npi-providers-mcp-server
io.github.cyanheads/npi-providers-mcp-servercyanheadsstreamable-httpv0.5.1Scanned
Search NPPES providers and resolve NUCC specialty codes via MCP over STDIO or Streamable HTTP.
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the npi-providers-mcp-server can do
The npi-providers-mcp-server is published by the GitHub account cyanheads. It has 3 tools. It can create or change data (1 tool: npi_lookup_taxonomy), but cannot delete data. 2 tools only read.
3 tools bring in text other people can write (npi_search_providers, npi_get_provider and npi_lookup_taxonomy).
The fixed checks matched 3 findings (long-description, credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 0.5.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 1Claude Code: ask
npi_lookup_taxonomyResolve and browse the NUCC Healthcare Provider Taxonomy — the specialty code set NPPES uses — fully offline (bundled).Reads text others write1 finding
Why it is in this group
- The name "npi_lookup_taxonomy" says "lookup": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Findings
- Warn
The server marks "npi_lookup_taxonomy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "npi_lookup_taxonomy" says "lookup": a word for reading.
Description, as the server wrote it 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, classification, and NUCC section; its first page lists the groupings the filters reach with entry counts, plus that grouping's classifications when they reach exactly one. 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. An active entry's code goes straight into npi_search_providers taxonomy_description, which searches with that code's text.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
npi_get_providerFetch NPPES records from up to 100 raw NPI entries per call.Reads text others write1 finding
Why it is in this group
- The name "npi_get_provider" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...ions also carry their mailing address); credential, sex, sole-proprietor flag; enumeration..."
Description, as the server wrote it 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 (a description the registry leaves blank comes from the bundled NUCC code set, marked descriptionSource "nucc"); 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
npi_search_providersSearch the NPPES NPI registry for individual practitioners and healthcare organizations by name, organization name, location, provider type, and specialty.Reads text others write1 finding
Why it is in this group
- The name "npi_search_providers" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,032 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...) returns continuationPostalCodes, postal_code prefixes that continue the search."
Description, as the server wrote it 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 search text becomes taxonomy_description, and all resolved candidates are returned in metadata. taxonomy_description also takes a NUCC code, such as one npi_get_provider returns, and searches with that code's text. 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. With name_role "authorized_official", first_name, last_name, and name_search match each organization's authorized official instead of the provider, the search covers organizations only, and each row names the official in authorizedOfficial. 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. A specialty filter matches any of a provider's taxonomies, as a case-insensitive prefix of the taxonomy's classification or specialization; a row matched through a taxonomy other than its primary names it in matchedTaxonomy. 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:33 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://npi-providers.caseyjhand.com/mcp: tools/list returned 3 tools to an anonymous client, including npi_lookup_taxonomy (write)
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 0 to 1
Findings
Matches of fixed checks, with the text they matched.
The server marks "npi_lookup_taxonomy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "npi_lookup_taxonomy" says "lookup": a word for reading.
The description is 2,032 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...) returns continuationPostalCodes, postal_code prefixes that continue the search."
- Infonpi_get_provider
The description mentions "credential".
What this check looks forMatched text
description: "...ions also carry their mailing address); credential, sex, sole-proprietor flag; enumeration..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:npi_get_providerOnly readsdescription
- Changed:npi_lookup_taxonomyChanges thingsdescriptioninputSchema
- Changed:npi_search_providersOnly readsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
- Tools that change things, listed without credentials: 0 to 1
Tools3 changed.~3 changedView diff
- Changed:npi_get_providerOnly readsdescriptioninputSchema
- Changed:npi_lookup_taxonomyChanges thingsdescriptioninputSchema
- Changed:npi_search_providersOnly readsinputSchema
Install
Pinned to version 0.5.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http npi-providers https://npi-providers.caseyjhand.com/mcpclaude mcp add --transport http npi-providers https://npi-providers.caseyjhand.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__npi-providers__npi_search_providers",
"mcp__npi-providers__npi_get_provider"
],
"ask": [
"mcp__npi-providers__npi_lookup_taxonomy"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as npi-providers. Review it before you use it.
Capability tags behind 3 rules
- mcp__npi-providers__npi_search_providers untrusted-input
- mcp__npi-providers__npi_get_provider untrusted-input
- mcp__npi-providers__npi_lookup_taxonomy untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/npi-providers-mcp-server/verify?hash=2c1079319743b85172ac75828d19870f379458290240d0a7f82970d30a8d3427" | jq -e '.changed == false'Pinned hash 2c1079319743, from Nov 19, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cyanheads/npi-providers-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cyanheads/npi-providers-mcp-server)Source: MCP Registry · repository. Synced Nov 19, 2026, 16:18 UTC.
npi-providers-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the npi-providers-mcp-server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the npi-providers-mcp-server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the npi-providers-mcp-server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the npi-providers-mcp-server have?
- 3 tools: 1 write, 2 read. npi_lookup_taxonomy, npi_search_providers and npi_get_provider.
Does the npi-providers-mcp-server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the npi-providers-mcp-server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the npi-providers-mcp-server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.