# io.github.cyanheads/npi-providers-mcp-server (remote · npi-providers.caseyjhand.com)

Look up US healthcare providers in the NPPES NPI registry and resolve NUCC specialty codes.

- Trust score: 68/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `npi-providers.caseyjhand.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-npi-providers-mcp-server/npi-providers.md), [page](https://verifymcp.io/servers/cyanheads-npi-providers-mcp-server/npi-providers)
- npm · `@cyanheads/npi-providers-mcp-server`: 35/100, [markdown](https://verifymcp.io/servers/cyanheads-npi-providers-mcp-server/cyanheads-npi-providers-mcp-server.md), [page](https://verifymcp.io/servers/cyanheads-npi-providers-mcp-server/cyanheads-npi-providers-mcp-server)

## Channel facts

- Endpoint: `https://npi-providers.caseyjhand.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.7`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http cyanheads-npi-providers-mcp-server https://npi-providers.caseyjhand.com/mcp
```

### Codex

```toml
[mcp_servers.cyanheads-npi-providers-mcp-server]
url = "https://npi-providers.caseyjhand.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-npi-providers-mcp-server": {
      "type": "remote",
      "url": "https://npi-providers.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyanheads-npi-providers-mcp-server --url https://npi-providers.caseyjhand.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cyanheads-npi-providers-mcp-server:
    url: "https://npi-providers.caseyjhand.com/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +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.

### 2026-08-01 (score 67, +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.

### 2026-07-31 (score 66, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +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.

### 2026-07-28 (score 63, +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.

### 2026-07-27 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (3)

### `npi_search_providers` (~605 tokens)

Npi Search Providers

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.

Input parameters:

- `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.

Output parameters:

- `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): 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.

### `npi_get_provider` (~219 tokens)

Npi Get Provider

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.

Input parameters:

- `npis` (required): A single 10-digit NPI, or an array of up to 10. Each is validated as exactly 10 digits before any API call.

Output parameters:

- `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.

### `npi_lookup_taxonomy` (~365 tokens)

Npi Lookup Taxonomy

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.

Input parameters:

- `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, required): 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.

Output parameters:

- `cap` (number): The limit that was applied.
- `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).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cyanheads-npi-providers-mcp-server/npi-providers#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 66
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 62

## Links

- Remote endpoint: https://npi-providers.caseyjhand.com/mcp
- Repository: https://github.com/cyanheads/npi-providers-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/cyanheads-npi-providers-mcp-server/npi-providers/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyanheads-npi-providers-mcp-server/npi-providers/changelog.json
- HTML version of this page: https://verifymcp.io/servers/cyanheads-npi-providers-mcp-server/npi-providers