mcpbeat Sign in

Npi Providers MCP Server

answering

Npi Providers MCP Server is answering right now. Last checked 15 min ago. 139 installs a week from npm. It exposes 3 tools. Last commit 26 Oct 2026.

Search NPPES providers and resolve NUCC specialty codes via MCP over STDIO or Streamable HTTP.

Installs per day peak 215 · avg 36 · -71% w/w
a month agotoday
Uptime history 91 days of history · worst day 93%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
572 ms
Response time
average over 24h
139
Installs / week
npm and PyPI

What changed 23

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 August 2026. No other catalogue keeps this.

26 Oct 3 tools changed the parameters they ask for npi_get_provider, npi_lookup_taxonomy, npi_search_providers
26 Oct 2 tool descriptions were rewritten npi_get_provider, npi_lookup_taxonomy
26 Oct a tool changed version
9 Oct a tool changed version
25 Sep a tool changed the parameters it asks for2 times that day npi_search_providers
25 Sep 2 tool descriptions were rewritten npi_lookup_taxonomy, npi_search_providers
25 Sep a tool changed version
24 Sep 2 tool descriptions were rewritten npi_get_provider, npi_search_providers
24 Sep a tool changed the parameters it asks for npi_get_provider
24 Sep a tool changed version
and 8 more, back to 25 August 2026

Nothing serious here today

Today is the operative word: we check Npi Providers MCP Server every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add npi-providers-mcp-server --transport http https://npi-providers.caseyjhand.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://npi-providers.caseyjhand.com/mcp
~/.codex/config.toml
[mcp_servers.npi-providers-mcp-server]
url = "https://npi-providers.caseyjhand.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "npi-providers-mcp-server": {
      "url": "https://npi-providers.caseyjhand.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "npi-providers-mcp-server": {
      "type": "http",
      "url": "https://npi-providers.caseyjhand.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

npi
npi_get_provider
Fetch NPPES records from up to 100 raw NPI entries per call. Deduplicate in input order, validate check digits, and look up the first 10 distinct valid NPIs; remaining valid NPIs are listed in unprocessed and are never looked up. Decodes an NPI from a claim, prescription, or another health data source into the provider's professional-practice profile: every taxonomy with its primary flag, license number and state; practice addresses with phone and fax (only LOCATION rows are kept for individual providers, so their mailing address is withheld; organizations also carry their mailing address); credential, sex, sole-proprietor flag; enumeration and last-updated dates; active/deactivated status; secondary identifiers (Medicaid, etc.); and FHIR/Direct endpoints. Each NPI must be 10 digits with a valid check digit (its last digit); every NPI failing the check digit lands in invalid and is never looked up. Reports partial success: valid 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.
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 active taxonomy entries, excluding codes NUCC marks inactive; mode `get` returns the full entry for an exact code, including NUCC's Notes; mode `browse` walks the hierarchy (grouping → classification → specialization), optionally filtered by grouping and NUCC section. Individual includes Group codes; section does not determine NPI entity type, which comes from NPPES enumeration_type. Every entry carries its status, and an inactive code names its replacement when NUCC gives one; `get` and `browse` still return inactive codes. A resolved entry's specialization, or its classification when specialization is absent, maps directly to npi_search_providers.taxonomy_description.
npi_search_providers
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. When city/state/postal_code are given, only practice addresses are searched, never mailing addresses: a provider is returned only when its primary practice location or one of its other practice locations matches all of them. A provider kept on another practice location names it in matchedLocation. Name searches also match former and other names, sorted by current name; such a row names the matching name in matchedOtherName. The registry never reports a true match total, and one search reaches only its first 1200 matches: a full page names the next in nextPage, and the terminal window (skip 1000, limit 200) returns continuationPostalCodes, postal_code prefixes that continue the search.

Endpoints

URLTransportStateLatencyChecked
https://npi-providers.caseyjhand.com/mcp streamable-http answering 620 ms 15 min ago

Alternatives to Npi Providers MCP Server

same job, measured the same way
StyleKit
by anxforever

MCP server for StyleKit styles, tokens, recipes, lint and repair over stdio or HTTP.

126 installs/wk 5 tools answering
Claudebox
by psyb0t

Self-hosted MCP server exposing Claude Code as an agentic AI tool over streamable HTTP.

local only
Statistik Austria MCP
by dv155

Search and query Statistik Austria open data (OGD) with codes resolved to readable labels.

304 installs/wk local only
Github
by davidweb3-ctrl

GitHub MCP Server - List PRs, issues, repo info, and search code

38 installs/wk local only
ContextStream MCP Server
by contextstreamio

ContextStream MCP server for code context, memory, search, and AI tools.

6 868 installs/wk local only
qart.uk QR studio
by qart

qart.uk MCP server: resolve scanned codes, browse the free pool, and buy QR artwork.

8 tools answering
Canada Postal Code Lookup MCP
by donniertf-hub

Resolve Canadian postal codes to city, province and coordinates.

3 tools answering
Agentsbestfriend
by therealfloatdev

MCP that provides fast, token-efficient tools for navigating, searching, and understanding codebases

66 installs/wk local only

Npi Providers MCP Server — questions

Answers built from our own checks of this server.

What can Npi Providers MCP Server do?
It exposes 3 tools, read directly from the server on our last check. Among them: npi_get_provider, npi_lookup_taxonomy, npi_search_providers. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Npi Providers MCP Server working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 572 ms. The bar chart above shows every period we have measured.
How do I connect Npi Providers MCP Server?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Npi Providers MCP Server need an API key?
No. Npi Providers MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Npi Providers MCP Server?
It answers our handshake in 572 ms on average, which is faster than 19% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Npi Providers MCP Server?
The npm package @cyanheads/npi-providers-mcp-server was installed 139 times in the last week. Week over week that is -71%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Npi Providers MCP Server open source?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript, 1 stars on GitHub and 7 open issues. The licence covers the code in the repository, not the hosted service at npi-providers.caseyjhand.com, which runs on its operator's own terms.