io.usefulapi/nppes-npi-registry
REMOTE · NPPES-NPI-REGISTRY.USEFULAPI.IO · SCANNED OCT 4
Look up US healthcare providers and organisations by NPI.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1245 tokens (~311/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/nppes-npi-registry MCP server?
io.usefulapi/nppes-npi-registry is a hosted endpoint at https://nppes-npi-registry.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · nppes-npi-registry.usefulapi.io
claude mcp add --transport http io-usefulapi-nppes-npi-registry 'https://nppes-npi-registry.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-nppes-npi-registry": {
"url": "https://nppes-npi-registry.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-nppes-npi-registry": {
"type": "http",
"url": "https://nppes-npi-registry.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-nppes-npi-registry] url = "https://nppes-npi-registry.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-nppes-npi-registry": {
"type": "remote",
"url": "https://nppes-npi-registry.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-nppes-npi-registry --url 'https://nppes-npi-registry.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-nppes-npi-registry:
url: "https://nppes-npi-registry.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-nppes-npi-registry": {
"Transport": "http",
"Url": "https://nppes-npi-registry.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-nppes-npi-registry -t streamable-http -u 'https://nppes-npi-registry.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-nppes-npi-registry": {
"type": "http",
"url": "https://nppes-npi-registry.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +7
- Authorization: partial → pass ▲ security
- 3 Oct 26 −6
- Authorization: pass → partial ▼ security
- Stability: unverified → 0.03 ▲ functional
- 2 Oct 26 +41
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- 30 Sept 26 +10
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 29 Sept 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://nppes-npi-registry.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nppes-npi-registry.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://nppes-npi-registry.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://nppes-npi-registry.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://nppes-npi-registry.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://nppes-npi-registry.usefulapi.io/mcp |
| Authorisation server | https://nppes-npi-registry.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nppes-npi-registry.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://nppes-npi-registry.usefulapi.io/mcp | HTTPS enforced | 301 | https://nppes-npi-registry.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
nppes_lookup_npi Look up a provider by NPI number ~91
Look up a single healthcare provider by their exact 10-digit National Provider Identifier (NPI). Returns the full registry record: basic info, addresses, taxonomies/specialties, identifiers and other names. NPPES Read API v2.1.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | The 10-digit NPI number to look up, e.g. '1467550004' (required). |
No output schema declared.
No examples provided.
nppes_search Search the NPI registry (all criteria) ~442
Full-power search of the NPPES NPI Registry across ANY combination of criteria — individual name, organization name, NPI number, taxonomy/specialty, and location. Use nppes_search_individuals / nppes_search_organizations for the common cases; use this when you need mixed or advanced criteria. The API requires at least one meaningful search parameter. NPPES Read API v2.1.
| Name | Type | Req | Description |
|---|---|---|---|
| address_purpose | string | – | Which address the city/state/postal_code filters apply to (LOCATION = practice address). |
| city | string | – | City of the provider's address. |
| country_code | string | – | Two-letter country code (default 'US'). Use 'US' for domestic addresses. |
| enumeration_type | string | – | Restrict to 'NPI-1' (individuals) or 'NPI-2' (organizations). Omit to search both. |
| first_name | string | – | Individual provider first name (trailing '*' wildcard allowed). |
| last_name | string | – | Individual provider last name (trailing '*' wildcard allowed). |
| limit | integer | – | Max number of records to return (1–200, default 10). |
| name_purpose | string | – | For name matching: 'PROVIDER' (default) or 'AO' (authorized official). |
| number | string | – | Exact 10-digit NPI number. |
| organization_name | string | – | Organization name (trailing '*' wildcard allowed). |
| postal_code | string | – | Postal (ZIP) code; a trailing '*' wildcard is allowed for prefix search, e.g. '941*'. |
| skip | integer | – | Number of records to skip, for pagination (0–1000; combined with limit, up to 1200 records reachable). |
| state | string | – | Two-letter U.S. state/territory abbreviation, e.g. 'CA', 'NY', 'PR'. |
| taxonomy_description | string | – | Provider taxonomy / specialty text, e.g. 'cardiology', 'Pediatrics', 'Social Worker'. Partial matches supported; a trailing '*' wildcard is allowed (min 2 chars before it). |
No output schema declared.
No examples provided.
nppes_search_individuals Search individual providers ~387
Search for INDIVIDUAL healthcare providers (NPI-1: doctors, nurses, therapists, etc.) by name, specialty (taxonomy) and/or location. Provide at least one meaningful criterion beyond a location. Name fields support a trailing '*' wildcard (min 2 chars before it). NPPES Read API v2.1.
| Name | Type | Req | Description |
|---|---|---|---|
| address_purpose | string | – | Which address the city/state/postal_code filters apply to (LOCATION = practice address). |
| city | string | – | City of the provider's address. |
| country_code | string | – | Two-letter country code (default 'US'). Use 'US' for domestic addresses. |
| first_name | string | – | Provider first name. A trailing '*' wildcard is allowed, e.g. 'Jo*'. |
| last_name | string | – | Provider last name. A trailing '*' wildcard is allowed, e.g. 'Smi*'. |
| limit | integer | – | Max number of records to return (1–200, default 10). |
| name_purpose | string | – | Which name to match: 'PROVIDER' (default) matches the provider's own name; 'AO' matches an authorized official. |
| postal_code | string | – | Postal (ZIP) code; a trailing '*' wildcard is allowed for prefix search, e.g. '941*'. |
| skip | integer | – | Number of records to skip, for pagination (0–1000; combined with limit, up to 1200 records reachable). |
| state | string | – | Two-letter U.S. state/territory abbreviation, e.g. 'CA', 'NY', 'PR'. |
| taxonomy_description | string | – | Provider taxonomy / specialty text, e.g. 'cardiology', 'Pediatrics', 'Social Worker'. Partial matches supported; a trailing '*' wildcard is allowed (min 2 chars before it). |
No output schema declared.
No examples provided.
nppes_search_organizations Search organization providers ~325
Search for ORGANIZATION healthcare providers (NPI-2: hospitals, clinics, group practices, pharmacies, labs, etc.) by organization name, specialty (taxonomy) and/or location. The organization_name field supports a trailing '*' wildcard (min 2 chars before it). NPPES Read API v2.1.
| Name | Type | Req | Description |
|---|---|---|---|
| address_purpose | string | – | Which address the city/state/postal_code filters apply to (LOCATION = practice address). |
| city | string | – | City of the provider's address. |
| country_code | string | – | Two-letter country code (default 'US'). Use 'US' for domestic addresses. |
| limit | integer | – | Max number of records to return (1–200, default 10). |
| organization_name | string | – | Organization (legal business) name. A trailing '*' wildcard is allowed, e.g. 'Kaiser*'. |
| postal_code | string | – | Postal (ZIP) code; a trailing '*' wildcard is allowed for prefix search, e.g. '941*'. |
| skip | integer | – | Number of records to skip, for pagination (0–1000; combined with limit, up to 1200 records reachable). |
| state | string | – | Two-letter U.S. state/territory abbreviation, e.g. 'CA', 'NY', 'PR'. |
| taxonomy_description | string | – | Provider taxonomy / specialty text, e.g. 'cardiology', 'Pediatrics', 'Social Worker'. Partial matches supported; a trailing '*' wildcard is allowed (min 2 chars before it). |
No output schema declared.
No examples provided.
What is the io.usefulapi/nppes-npi-registry MCP server?
io.usefulapi/nppes-npi-registry is an MCP server listed in the public MCP registry as io.usefulapi/nppes-npi-registry. Look up US healthcare providers and organisations by NPI. This page covers its hosted endpoint (https://nppes-npi-registry.usefulapi.io/mcp).
Is the io.usefulapi/nppes-npi-registry MCP server safe to use?
io.usefulapi/nppes-npi-registry scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/nppes-npi-registry MCP server expose?
io.usefulapi/nppes-npi-registry exposes 4 tools: nppes_lookup_npi, nppes_search_individuals, nppes_search_organizations, nppes_search. Their descriptions and schemas cost roughly 1,245 tokens of context every time the server is loaded.
Does the io.usefulapi/nppes-npi-registry MCP server require authentication?
Yes. io.usefulapi/nppes-npi-registry asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/nppes-npi-registry MCP server still maintained?
io.usefulapi/nppes-npi-registry is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.