NPI Who
REMOTE · NPIWHO.COM
US health care providers by NPI, name or phone, with payments, Medicare, OIG and facility data.
Available components
Last scanned (11 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 709 tokens (~118/item across 6 items; 6 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +4
- HSTS header: fail → pass ▲ security
- Tool “data_sources” rewrote its description, which is the text the model reads security
- Tool “list_facilities” rewrote its description, which is the text the model reads security
- Tool “lookup_phone” rewrote its description, which is the text the model reads security
- Tool “lookup_provider” rewrote its description, which is the text the model reads security
- Tool “nearby_providers” rewrote its description, which is the text the model reads security
- Tool “search_providers” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 63
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 5 Nov 2026 · Probed https://npiwho.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=npiwho.com | CN=YE2,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6356e6bde0d435e256db98bbb16c96cea39 |
| SANs: *.npiwho.com, npiwho.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of npiwho.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| npiwho.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://npiwho.com/mcp | Verified | 200 | |
| http (plaintext) | http://npiwho.com/mcp | HTTPS enforced | 301 | https://npiwho.com/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 →
data_sources Data sources and dates ~46
Use when asked how current or how reliable the data is, or what it does not include. Which public files this data comes from, their snapshot dates, and what they do not cover.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_facilities Facilities in a state ~117
Use when the question is about facilities of a kind in a state or city rather than one named provider. Medicare-certified home health agencies, hospices, hospitals, nursing homes, or HRSA health centers (FQHCs) in a state, optionally one city. Up to 50 rows with page urls; the full list and a CSV are at the state page url.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| kind | string | yes | – |
| limit | integer | – | – |
| state | string | yes | Two-letter state code |
No output schema declared.
No examples provided.
lookup_phone Who is at this phone number ~71
Use when the question is who a phone number belongs to. Providers whose registry practice phone, or a phone they published on a claimed page, is this number. Any US format. Providers who asked for their phone to be withheld are not returned.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | A US phone number in any format |
No output schema declared.
No examples provided.
lookup_provider Look up a provider by NPI ~111
Use when the question names an NPI, or after search_providers has found the right person. One provider by NPI: the registry record, and what the public files have on them (Open Payments total, Medicare billing, OIG exclusion, Medicare clinician record, facility enrollments, claimed-page details) with the page section where each is. The result's url is the page to cite and to send readers to for the detail.
| Name | Type | Req | Description |
|---|---|---|---|
| npi | string | yes | The 10-digit National Provider Identifier |
No output schema declared.
No examples provided.
nearby_providers Nearest providers of the same specialty ~129
Use when the question is who else does this nearby, or for alternatives to a provider. The providers with the same specialty nearest a given provider (by NPI) or a ZIP code and specialty, by distance between ZIP code centres. Up to 12.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| npi | string | – | Start from this provider's specialty and ZIP |
| taxonomy | string | – | NUCC taxonomy code, e.g. 207Q00000X for family medicine; required with zip |
| zip | string | – | Or a 5-digit ZIP code, with taxonomy |
No output schema declared.
No examples provided.
search_providers Search providers by name ~112
Use when the question names a person or practice but no NPI. Find individual providers or organizations by name, optionally within a state. Returns up to 20 matches, best first, each with its page url. Use lookup_provider on a result for the full record.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | A person's name ('maria gonzalez', 'gonzalez'), or an organization name |
| state | string | – | Two-letter state code, e.g. TX |
No output schema declared.
No examples provided.
How do I install the NPI Who MCP server?
NPI Who is a hosted endpoint at https://npiwho.com/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 · npiwho.com
claude mcp add --transport http npiwho-npiwho 'https://npiwho.com/mcp'
What is the NPI Who MCP server?
NPI Who is an MCP server listed in the public MCP registry as io.github.npiwho/npiwho. US health care providers by NPI, name or phone, with payments, Medicare, OIG and facility data. This page covers its hosted endpoint (https://npiwho.com/mcp).
Is the NPI Who MCP server safe to use?
NPI Who scores 71 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 NPI Who MCP server expose?
NPI Who exposes 6 tools: lookup_provider, search_providers, lookup_phone, nearby_providers, list_facilities, data_sources. Their descriptions and schemas cost roughly 586 tokens of context every time the server is loaded.
Does the NPI Who MCP server require authentication?
No. We connected to NPI Who without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NPI Who MCP server still maintained?
NPI Who is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.