NPPES NPI Registry MCP by usefulapi
REMOTE · NPPES-NPI-REGISTRY.USEFULAPI.IO
Look up US healthcare providers and organisations by NPI.
Available components
Last scanned (20 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_a_provider_s_specialty_and_practice_address” functional
- New prompt “find_clinics_hospitals_or_pharmacies_by_name” functional
- New prompt “find_doctors_or_nurses_by_name_specialty_and_place” functional
- New prompt “look_up_a_provider_by_npi_number” functional
- New prompt “search_the_registry_with_mixed_criteria” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 +1
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 +1
- Server version: 1.24.0 → 1.25.0 functional
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 21 Nov 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 | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| 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. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
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 | Redirected | 302 | https://usefulapi.io/nppes-npi-registry/ |
| http (plaintext) | http://nppes-npi-registry.usefulapi.io/mcp | Inconclusive | 302 | http://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.
How do I install the NPPES NPI Registry MCP by usefulapi server?
NPPES NPI Registry MCP by usefulapi 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'
What is the NPPES NPI Registry MCP by usefulapi server?
NPPES NPI Registry MCP by usefulapi is 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 NPPES NPI Registry MCP by usefulapi server safe to use?
NPPES NPI Registry MCP by usefulapi scores 18 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 NPPES NPI Registry MCP by usefulapi server expose?
NPPES NPI Registry MCP by usefulapi 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 NPPES NPI Registry MCP by usefulapi server require authentication?
Its publisher declares no required credentials for NPPES NPI Registry MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the NPPES NPI Registry MCP by usefulapi server still maintained?
NPPES NPI Registry MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the NPPES NPI Registry MCP by usefulapi server?
VerifyMCP ran 4 checks on NPPES NPI Registry MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about NPPES NPI Registry MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.