io.github.cyanheads/npi-providers-mcp-server
REMOTE · NPI-PROVIDERS.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 21
Search NPPES providers and resolve NUCC specialty codes via MCP over STDIO or Streamable HTTP.
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 Security66
- 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 3 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1074 tokens (~358/item across 3 items; 3 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 Management83
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.cyanheads/npi-providers-mcp-server server?
io.github.cyanheads/npi-providers-mcp-server is a hosted endpoint at https://npi-providers.caseyjhand.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 · npi-providers.caseyjhand.com
claude mcp add --transport http cyanheads-npi-providers-mcp-server 'https://npi-providers.caseyjhand.com/mcp'
{
"mcpServers": {
"cyanheads-npi-providers-mcp-server": {
"url": "https://npi-providers.caseyjhand.com/mcp"
}
}
} {
"servers": {
"cyanheads-npi-providers-mcp-server": {
"type": "http",
"url": "https://npi-providers.caseyjhand.com/mcp"
}
}
} [mcp_servers.cyanheads-npi-providers-mcp-server] url = "https://npi-providers.caseyjhand.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cyanheads-npi-providers-mcp-server": {
"type": "remote",
"url": "https://npi-providers.caseyjhand.com/mcp",
"enabled": true
}
}
} openclaw mcp add cyanheads-npi-providers-mcp-server --url 'https://npi-providers.caseyjhand.com/mcp' --transport streamable-http
mcp_servers:
cyanheads-npi-providers-mcp-server:
url: "https://npi-providers.caseyjhand.com/mcp" {
"McpServers": {
"cyanheads-npi-providers-mcp-server": {
"Transport": "http",
"Url": "https://npi-providers.caseyjhand.com/mcp"
}
}
} assistant mcp add cyanheads-npi-providers-mcp-server -t streamable-http -u 'https://npi-providers.caseyjhand.com/mcp'
{
"mcpServers": {
"cyanheads-npi-providers-mcp-server": {
"type": "http",
"url": "https://npi-providers.caseyjhand.com/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.
- 20 Sept 26 0
- Server version: 0.1.8 → 0.1.9 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 −3
- Stability: 0.97 → fail ▼ security
- Stability: 0.97 → pass security
- Tool “npi_search_providers” rewrote its description, which is the text the model reads security
- Tool “npi_lookup_taxonomy” rewrote its description, which is the text the model reads security
- “npi_lookup_taxonomy” dropped the required parameter “mode” ▼ functional
- Schema quality: 441 → 358 ▲ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.1.7 → 0.1.8 functional
- “npi_search_providers” reworded the description of “state” cosmetic
- “npi_search_providers” reworded the description of “name_search” cosmetic
- “npi_lookup_taxonomy” dropped the optional parameter “section” cosmetic
- “npi_lookup_taxonomy” dropped the optional parameter “skip” cosmetic
- “npi_lookup_taxonomy” dropped the optional parameter “query” cosmetic
- “npi_lookup_taxonomy” dropped the optional parameter “limit” cosmetic
- “npi_lookup_taxonomy” dropped the optional parameter “grouping” cosmetic
- “npi_lookup_taxonomy” dropped the optional parameter “code” cosmetic
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 10 Aug 26 0
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.50 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 8 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.40 → unverified ▼ security
- HSTS header: pass → fail ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 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
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 Sept 2026 · Probed https://npi-providers.caseyjhand.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=caseyjhand.com | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a6985204ed51ae050e7738aa6be668e9 |
| SANs: caseyjhand.com, *.caseyjhand.com | ||||||
| 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 secure
Validation of npi-providers.caseyjhand.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| caseyjhand.com. | present | 2371 | 13 | Verified |
| npi-providers.caseyjhand.com. | Verified address RRset verified with the apex keys |
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=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://npi-providers.caseyjhand.com/mcp | Verified | 200 | |
| http (plaintext) | http://npi-providers.caseyjhand.com/mcp | HTTPS enforced | 301 | https://npi-providers.caseyjhand.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 →
npi_get_provider Npi Get Provider ~219
Fetch the complete NPPES record for one or more NPI numbers (up to 10 per call). Decodes an NPI from a claim, prescription, or another health data source into a fully populated provider profile: every taxonomy with its primary flag, license number and state; all practice and mailing addresses; credential, sex, sole-proprietor flag; enumeration and last-updated dates; active/deactivated status; secondary identifiers (Medicaid, etc.); and FHIR/Direct endpoints. The 10-digit NPI format is validated before any API call. Reports partial success: well-formed NPIs with no registry record (deactivated or never enumerated) land in notFound, while NPIs whose lookup hit an upstream error (registry unavailable, timeout) land in errored — kept distinct from confirmed misses — rather than failing the whole call.
| Name | Type | Req | Description |
|---|---|---|---|
| npis | – | yes | A single 10-digit NPI, or an array of up to 10. Each is validated as exactly 10 digits before any API call. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Present when the call failed. Absent on success. |
| errored | array | – | NPIs whose lookups failed with an upstream/transport error (service unavailable, timeout) — distinct from a confirmed miss in notFound. These are unresolved, not absent; retry them. |
| found | array | – | Fully decoded records for NPIs that resolved. |
| notFound | array | – | NPIs that were well-formed but returned no record (deactivated or never enumerated). A confirmed absence, not a failure. |
| notice | string | – | Guidance when some or all NPIs returned nothing. |
| totalCount | number | – | Number of provider records that resolved from the requested NPIs. |
No examples provided.
npi_lookup_taxonomy Npi Lookup Taxonomy ~142
Resolve and browse the NUCC Healthcare Provider Taxonomy — the specialty code set NPPES uses — fully offline (bundled). Mode `resolve` turns a plain-language specialty (e.g. "cardiologist", "heart doctor") into matching taxonomy entries; mode `get` returns the full entry for an exact code; mode `browse` walks the hierarchy (grouping → classification → specialization), optionally filtered by grouping and by NPI section (Individual/NPI-1 vs Non-Individual/NPI-2). A resolved entry's specialization, or its classification when specialization is absent, maps directly to npi_search_providers.taxonomy_description.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| cap | number | – | The limit that was applied. |
| error | object | – | Present when the call failed. Absent on success. |
| matches | array | – | Matching taxonomy entries. For mode "get" this is the single requested entry; for "resolve"/"browse" it is the ranked/sorted matches up to limit. |
| notice | string | – | Guidance — how to page a truncated result with skip, or how to broaden when nothing matched. |
| shown | number | – | Number of entries returned. |
| truncated | boolean | – | True when the list was capped at `limit` (more entries may match). |
No examples provided.
npi_search_providers Npi Search Providers ~578
Search the NPPES NPI registry for individual practitioners and healthcare organizations by name, organization name, location, provider type, and specialty. Plain-language specialty terms (e.g. "cardiologist", "pediatric cardiologist") resolve through the bundled NUCC taxonomy; the top match's specialization or classification becomes taxonomy_description, and all resolved candidates are returned in metadata. Location belongs in the dedicated city/state/postal_code inputs, not inside specialty. Each provider row includes the NPI, name, primary specialty, city/state/ZIP, type, and active/deactivated status; the NPI is the input for npi_get_provider when the full record is needed. At least one search criterion is required, and the registry rejects state-only searches. For specialty searches, returned providers are limited to the requested city/state/postal_code even when the registry includes providers outside that location. The registry never reports a true match total and only the first 1200 matches are reachable, so broad queries are capped.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Practice-location city. |
| first_name | string | – | Individual first name. Trailing wildcard "*" allowed with at least 2 leading characters. |
| last_name | string | – | Individual last name. Trailing wildcard "*" allowed with at least 2 leading characters. |
| limit | integer | – | Maximum providers to return (1–200; the registry caps at 200). |
| name_search | string | – | One person's name. The first token becomes first_name and the last token becomes last_name; use first_name/last_name when middle names or multi-part surnames matter. |
| organization_name | string | – | Organization name (implies provider_type organization). Trailing wildcard "*" allowed with at least 2 leading characters. |
| postal_code | string | – | Practice-location postal/ZIP code (5 or 9 digits). |
| provider_type | string | – | Restrict to individuals (NPI-1) or organizations (NPI-2). Omit to search both. |
| skip | integer | – | Results to skip for pagination (0–1000). Only the first 1200 matches are reachable; skip beyond 1000 silently returns the same window — narrow the query instead of paging further. |
| specialty | string | – | Plain-language specialty (e.g. "pediatric cardiologist"), resolved through the bundled NUCC taxonomy to exact descriptions before searching. The matched taxonomy is echoed in the result. Mutually exc… |
| state | – | – | 2-letter state code (e.g. "WA"). The registry rejects state-only searches, so another criterion is required. A blank value is treated as omitted. |
| taxonomy_description | string | – | Exact NUCC taxonomy description for direct passthrough — use when the taxonomy description is already known. Mutually exclusive with specialty. |
| Name | Type | Req | Description |
|---|---|---|---|
| appliedTaxonomyDescription | string | – | The exact NUCC specialization or classification used as the specialty filter. |
| cap | number | – | The limit that was applied. |
| error | object | – | Present when the call failed. Absent on success. |
| notice | string | – | Guidance — pagination ceiling, page-size-not-total caveat, or how to broaden an empty result. |
| providers | array | – | Matching provider rows (up to limit). |
| resolvedTaxonomies | array | – | Taxonomy candidates ranked for the specialty term. The first candidate supplies appliedTaxonomyDescription; a different candidate can be selected through taxonomy_description. |
| shown | number | – | Number of providers returned. |
| truncated | boolean | – | True when the NPPES page contained at least cap providers before location constraints were applied; more may match even when shown is below cap. |
No examples provided.
What is the io.github.cyanheads/npi-providers-mcp-server server?
io.github.cyanheads/npi-providers-mcp-server is listed in the public MCP registry as io.github.cyanheads/npi-providers-mcp-server. Search NPPES providers and resolve NUCC specialty codes via MCP over STDIO or Streamable HTTP. This page covers its hosted endpoint (https://npi-providers.caseyjhand.com/mcp).
Is the io.github.cyanheads/npi-providers-mcp-server server safe to use?
io.github.cyanheads/npi-providers-mcp-server scores 77 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.github.cyanheads/npi-providers-mcp-server server expose?
io.github.cyanheads/npi-providers-mcp-server exposes 3 tools: npi_search_providers, npi_get_provider, npi_lookup_taxonomy. Their descriptions and schemas cost roughly 939 tokens of context every time the server is loaded.
Does the io.github.cyanheads/npi-providers-mcp-server server require authentication?
No. We connected to io.github.cyanheads/npi-providers-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cyanheads/npi-providers-mcp-server server still maintained?
io.github.cyanheads/npi-providers-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.