io.github.cyanheads/npi-providers-mcp-server
REMOTE · NPI-PROVIDERS.CASEYJHAND.COM · 2 COMPONENTS · SCANNED AUG 3
Look up US healthcare providers in the NPPES NPI registry and resolve NUCC specialty codes.
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 →
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 Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1324 tokens (~441/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 Management27
- Stability observed for 8 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · npi-providers.caseyjhand.com
claude mcp add --transport http cyanheads-npi-providers-mcp-server 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": {
"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.
- 3 Aug 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.
- 1 Aug 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.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 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
- 26 Jul 26 62
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 3 Aug 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 | 7 Jul 2026 | 5 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 5aad900eb2055a0b0ea55912ec19680c |
| 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 |
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 |
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.
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 |
|---|---|---|---|
| errored | array | yes | 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 | yes | Fully decoded records for NPIs that resolved. |
| notFound | array | yes | 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 | yes | Number of provider records that resolved from the requested NPIs. |
No examples provided.
npi_lookup_taxonomy Npi Lookup Taxonomy ~365
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 codes and their canonical descriptions; 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). Grounding a plain-language specialty here before calling npi_search_providers ensures the correct taxonomy code is sent rather than returning nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | — | For mode "get": the exact NUCC taxonomy code (e.g. "207RC0000X"). |
| grouping | string | — | For mode "browse": filter to a top-level grouping by case-insensitive substring (e.g. "physicians"). |
| limit | integer | — | Maximum entries to return for resolve/browse (1–50). Ignored for get. |
| mode | string | yes | resolve: plain term → codes. get: exact code → entry. browse: walk the hierarchy. |
| query | string | — | For mode "resolve": the plain-language specialty term to resolve (e.g. "pediatric cardiologist"). |
| section | string | — | For mode "browse": filter by NPI section — Individual (NPI-1) or Non-Individual (NPI-2). |
| skip | integer | — | Entries to skip before the page, for paging past a truncated resolve/browse result (0–1000). Keep the same query/filters and limit, raise skip by limit each call. Ignored for get. |
| Name | Type | Req | Description |
|---|---|---|---|
| cap | number | — | The limit that was applied. |
| matches | array | yes | 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 ~605
Search the NPPES NPI registry for individual practitioners and healthcare organizations by name, organization name, location, provider type, and specialty. The specialty filter accepts plain-language terms (e.g. "cardiologist", "pediatric cardiologist") and resolves them through the bundled NUCC taxonomy to the registry's exact taxonomy descriptions before searching; the resolved taxonomy is echoed back so you can see what was actually searched. Pass location as the dedicated city/state/postal_code inputs, not inside specialty. Returns a compact row per provider — NPI, name, primary specialty, city/state/ZIP, type, and active/deactivated status — suitable for disambiguation; call npi_get_provider with an NPI for the full record. At least one search criterion is required, and the registry rejects state-only searches (pair state with another filter). The registry does not treat location as a hard filter for specialty searches, so location-constrained results are post-filtered server-side to the requested city/state/postal_code. The registry never reports a true match total and only the first 1200 matches are reachable, so broad queries are capped — narrow with more filters.
| 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 | — | Convenience shortcut: a single person's name, split into first/last heuristically. For precise control use first_name/last_name. |
| 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 — pair it with another criterion. Blank values from form-based clients are 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 single taxonomy_description sent to the registry (from specialty resolution or the raw escape hatch). |
| cap | number | — | The limit that was applied. |
| notice | string | — | Guidance — pagination ceiling, page-size-not-total caveat, or how to broaden an empty result. |
| providers | array | yes | Matching provider rows (up to limit). |
| resolvedTaxonomies | array | — | The taxonomy candidates the specialty term resolved to; the first was sent to the registry. Re-run with taxonomy_description to pick a different one. |
| shown | number | — | Number of providers returned. |
| truncated | boolean | — | True when the returned page hit the limit — more may match. |
No examples provided.