Skip to content
SecurityAuto-generatedScore: 28

National Health Authority MCP Server

The National Health Authority API for PM-JAY e-card management represents a critical digital public infrastructure endpoint, enabling programmatic access to the Ayushman Bharat Pradhan Mantri Jan Arogya Yojana (PM-JAY) health benefit scheme.

Quick Start Summary

The National Health Authority MCP server is a Model Context Protocol bridge that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the National Health Authority API through natural language. It exposes 1 API endpoints as callable tools, such as Pradhan Mantri Jan Arogya Yojana. No authentication is required — setup takes approximately 30 seconds. The server uses STDIO transport and can be installed by running npx -y @mcp/apisetu-gov-in-pmjay. This integration is sourced from the auto National Health Authority OpenAPI specification (v3.0.0) and has a quality score of 28/99 (fair documentation coverage).

1Endpointstools mapped
NoneAuthopen access
28/99Qualityfair
~30 secSetupno auth

Server Details

Category
Security
Authentication
None
Endpoints
1 operations
Transport
STDIO
Spec Version
v3.0.0
Install Command
npx -y @mcp/apisetu-gov-in-pmjay

Environment Variables

NATIONAL_HEALTH_AUTHORITY_API_KEY

Example: your_national_health_authority_api_key

Top Endpoints

POST
/pmjay/certificate

Pradhan Mantri Jan Arogya Yojana

Own this API?

Verify ownership of this listing to control the description, configuration details, and documentation links. Choose between free manual verification or instant premium placement.

Option 1: Free Verification

Slow manual review. Requires creating a GitHub issue with verified documentation or domain verification.

  • • Verified badge on page
  • • Standard search sorting
  • • 2-3 business days review
Start Free Claim →
Instant & Boosted

Option 2: Featured Upgrade($9/mo)

Instant verification plus premium styling, featured badges, and directory placement boost.

  • • ★ Featured star & amber highlight border
  • • Top of directory search placement
  • • Instant activation via claim token

📖 Detailed MCP Integration Guide

A technical breakdown of capabilities, agent workflows, and security/configuration best practices.

Capabilities & Use Cases
The National Health Authority API for PM-JAY e-card management represents a critical digital public infrastructure endpoint, enabling programmatic access to the Ayushman Bharat Pradhan Mantri Jan Arogya Yojana (PM-JAY) health benefit scheme. Provided by the National Health Authority (NHA) of India, this API's core capability is to facilitate the issuance and retrieval of PM-JAY e-cards, which serve as digital proof of eligibility for cashless and paperless treatment at empaneled hospitals. The specific POST /pmjay/certificate endpoint is designed for authorized entities—such as hospital administrators, third-party aggregators, and government portals—to trigger the generation and delivery of a beneficiary's e-card to their integrated DigiLocker account. This moves beyond a simple consumer-facing document view, enabling enterprise use cases like automated beneficiary onboarding for hospital networks, real-time eligibility verification during hospital admission workflows, and the secure, auditable distribution of health insurance credentials across partner ecosystems.
🤖AI Agent Value
Exposing this API as a tool via the Model Context Protocol (MCP) unlocks powerful, context-aware automation for AI coding assistants and intelligent agents. Within an MCP server configuration, the tool would translate natural language instructions into precise API calls, allowing the AI to operate as a direct bridge between human intent and national health system transactions. Its value lies in its specificity and its connection to a live, government-managed beneficiary database. An AI agent becomes a capable co-developer for health-tech applications, able to instantly test and integrate e-card issuance flows, simulate beneficiary onboarding journeys, or debug integration issues by dynamically generating test certificates in a sandbox environment. This drastically reduces context-switching and manual API testing, accelerating development cycles for solutions that rely on verified PM-JAY status.
💬Example Workflows
Practical workflows enabled by this MCP tool are numerous. A developer could instruct the AI to "Query the NHA API to issue a test PM-JAY e-card for beneficiary ID 123 and send it to my test DigiLocker instance to validate our app's document-fetching logic." The AI would structure the POST request, handle the payload, and report the outcome. Another dynamic task would be: "Generate a batch of mock PM-JAY certificates for 10 different beneficiary IDs to populate our QA database and stress-test our eligibility dashboard." Furthermore, the tool could be used for integration verification: "Using the MCP server, attempt to issue a certificate for a known active beneficiary and confirm the JSON response matches our expected schema, flagging any discrepancies." These examples demonstrate how the AI moves beyond code completion to perform system-aware validation and data provisioning tasks.
🛡️Security & Auth
Given the current "None" authentication method, which is highly unusual and suggests the endpoint might be in a restricted or sandbox state for specific partners, developers must exercise extreme caution. For any production or public-facing integration, implementing robust authentication is non-negotiable. The foremost security best practice is to treat the API as requiring high-privilege access and immediately engage with the NHA's technical partnership channels to obtain proper API keys or OAuth 2.0 credentials. The principle of least privilege must be applied rigorously; any service account used should have permissions scoped exclusively to the certificate issuance endpoint, with no broader system access. Developers configuring the MCP server should store any obtained credentials in a secure secrets manager, never in code or configuration files. All API calls should be logged and monitored for anomalies, and the use of IP allowlisting, if supported by the NHA, should be enforced to restrict access to trusted application servers. This proactive security stance is critical when interacting with an API that handles sensitive national health beneficiary data.

Similar APIs

Other APIs in the Security category.

Spotify Web API

The Spotify Web API is a comprehensive RESTful service provided by Spotify AB that empowers developers to programmatically access Spotify's vast catalog of over 100 million songs and 5 million podcast titles. Its core capabilities encompass music discovery, library management, audio content retrieval, and playback control across authenticated user devices. Beyond basic metadata queries for albums, artists, and tracks, the API provides specialized endpoints for deep audio analysis (e.g., tempo, key, loudness) and audio features (e.g., danceability, energy, valence), which are invaluable for applications in music recommendation, DJ software, and academic research into music theory and psychology. Typical use cases span consumer applications like building custom playlist generators, social sharing features, or music learning tools, as well as enterprise applications for music intelligence platforms, content discovery engines, and personalized marketing analysis. The API serves as the foundational gateway for any third-party integration that seeks to leverage Spotify's ecosystem, from simple "Now Playing" widgets to complex data processing pipelines.

1Password Connect

The 1Password Connect API is a robust RESTful interface provided by 1Password, a leading enterprise password management and secrets orchestration platform. This API serves as the programmatic backbone for 1Password Connect, a self-hosted server that acts as a secure bridge between an organization's internal infrastructure and its 1Password vaults. Its core capability is to enable secure, automated access to secrets, credentials, documents, and other sensitive items stored within 1Password, without exposing master passwords or sensitive data to applications directly. Typical use cases are extensive within modern DevOps and IT environments, including dynamically injecting database credentials into cloud application deployments, rotating secrets on a scheduled basis, automatically retrieving API keys for CI/CD pipelines, and centralizing secret management for microservices architectures. By providing a self-hosted component, the API allows organizations to maintain full control over their data flow and integrate 1Password's zero-knowledge security model directly into their internal tooling and automation scripts.

Events API

The 1Password Events API is a specialized service provided by the password and credential management platform 1Password, designed for enterprise security teams, IT administrators, and security analysts. Its core capability is to provide a secure, queryable stream of audit events related to secret access and authentication activity within a 1Password organization or team. By aggregating data from the specified endpoints—`/api/v1/itemusages` for secret access logs and `/api/v1/signinattempts` for user authentication logs—it enables comprehensive monitoring, threat detection, and compliance reporting. Unlike a general-purpose API for managing vaults or secrets, this API is strictly read-focused, serving as the primary telemetry pipeline for security information and event management (SIEM) systems, custom alerting tools, and internal audit platforms. Typical use cases include correlating unusual secret access patterns with potential insider threats, verifying compliance with data access policies, generating audit trails for regulatory frameworks like SOC 2 or GDPR, and building real-time dashboards to visualize credential usage across an organization.

Authentiq API

The Authentiq API provides a robust foundation for implementing strong, passwordless authentication and identity verification systems. Developed by Authentiq, a specialist in modern digital identity solutions, this API enables the secure management of cryptographic keys and the orchestration of login and scope-based authorization flows. Its core capabilities are centered around the lifecycle management of public-private key pairs, which serve as the user's credentials. The endpoints allow for the creation of a new key pair (POST /key), retrieval of a public key by its ID (GET /key/{PK}), and associated management operations (POST, PUT, DELETE on the key resource). Beyond basic key management, the API facilitates the authentication process itself through the POST /login endpoint, which verifies a signature from the user's private key. The /scope endpoints introduce a layer of fine-grained, permission-based access control, allowing developers to define, query, and manage specific authorization scopes tied to a job or session. This makes the API ideal for enterprise applications requiring secure internal tool access, consumer-facing mobile or web apps seeking seamless login experiences without credential fatigue, and IoT ecosystems where device authentication is paramount.

Related MCP Server Integrations

Spotify Web API MCP Setup

The Spotify Web API is a comprehensive RESTful service provided by Spotify AB that empowers developers to programmatically access Spotify's vast catalog of over 100 million songs and 5 million podcast titles. Its core capabilities encompass music discovery, library management, audio content retrieval, and playback control across authenticated user devices. Beyond basic metadata queries for albums, artists, and tracks, the API provides specialized endpoints for deep audio analysis (e.g., tempo, key, loudness) and audio features (e.g., danceability, energy, valence), which are invaluable for applications in music recommendation, DJ software, and academic research into music theory and psychology. Typical use cases span consumer applications like building custom playlist generators, social sharing features, or music learning tools, as well as enterprise applications for music intelligence platforms, content discovery engines, and personalized marketing analysis. The API serves as the foundational gateway for any third-party integration that seeks to leverage Spotify's ecosystem, from simple "Now Playing" widgets to complex data processing pipelines.

SecurityConfigure →

1Password Connect MCP Setup

The 1Password Connect API is a robust RESTful interface provided by 1Password, a leading enterprise password management and secrets orchestration platform. This API serves as the programmatic backbone for 1Password Connect, a self-hosted server that acts as a secure bridge between an organization's internal infrastructure and its 1Password vaults. Its core capability is to enable secure, automated access to secrets, credentials, documents, and other sensitive items stored within 1Password, without exposing master passwords or sensitive data to applications directly. Typical use cases are extensive within modern DevOps and IT environments, including dynamically injecting database credentials into cloud application deployments, rotating secrets on a scheduled basis, automatically retrieving API keys for CI/CD pipelines, and centralizing secret management for microservices architectures. By providing a self-hosted component, the API allows organizations to maintain full control over their data flow and integrate 1Password's zero-knowledge security model directly into their internal tooling and automation scripts.

SecurityConfigure →

Events API MCP Setup

The 1Password Events API is a specialized service provided by the password and credential management platform 1Password, designed for enterprise security teams, IT administrators, and security analysts. Its core capability is to provide a secure, queryable stream of audit events related to secret access and authentication activity within a 1Password organization or team. By aggregating data from the specified endpoints—`/api/v1/itemusages` for secret access logs and `/api/v1/signinattempts` for user authentication logs—it enables comprehensive monitoring, threat detection, and compliance reporting. Unlike a general-purpose API for managing vaults or secrets, this API is strictly read-focused, serving as the primary telemetry pipeline for security information and event management (SIEM) systems, custom alerting tools, and internal audit platforms. Typical use cases include correlating unusual secret access patterns with potential insider threats, verifying compliance with data access policies, generating audit trails for regulatory frameworks like SOC 2 or GDPR, and building real-time dashboards to visualize credential usage across an organization.

SecurityConfigure →

Authentiq API MCP Setup

The Authentiq API provides a robust foundation for implementing strong, passwordless authentication and identity verification systems. Developed by Authentiq, a specialist in modern digital identity solutions, this API enables the secure management of cryptographic keys and the orchestration of login and scope-based authorization flows. Its core capabilities are centered around the lifecycle management of public-private key pairs, which serve as the user's credentials. The endpoints allow for the creation of a new key pair (POST /key), retrieval of a public key by its ID (GET /key/{PK}), and associated management operations (POST, PUT, DELETE on the key resource). Beyond basic key management, the API facilitates the authentication process itself through the POST /login endpoint, which verifies a signature from the user's private key. The /scope endpoints introduce a layer of fine-grained, permission-based access control, allowing developers to define, query, and manage specific authorization scopes tied to a job or session. This makes the API ideal for enterprise applications requiring secure internal tool access, consumer-facing mobile or web apps seeking seamless login experiences without credential fatigue, and IoT ecosystems where device authentication is paramount.

SecurityConfigure →

IP geolocation API MCP Setup

The IP Geolocation API, developed by AbstractAPI, is a robust and scalable RESTful service designed to provide developers with precise geographic, network, and contextual data associated with any given IPv4 or IPv6 address. Its core capability lies in translating a digital identifier—a public IP address—into a rich dataset that includes region, country, city, latitude, longitude, timezone, and ISP details. Beyond this fundamental geolocation, the API extends its value by offering supplementary metadata such as the local currency code, national flag, primary language, and security flags indicating whether an IP is from a corporate network or associated with a known threat actor. Typical enterprise use cases span from real-time user authentication and fraud prevention, where a login attempt from an unexpected location can trigger a security alert, to localized content delivery, ensuring users see region-appropriate pricing, language, and offers. For consumers and developers, it powers features like website analytics dashboards, personalized news feeds, and dynamic form auto-population.

SecurityConfigure →