NPPES NPI Registry MCP by usefulapi
io.usefulapi/nppes-npi-registryusefulapi.iostreamable-httpv1.40.4Scanned
Look up US healthcare providers and organisations by NPI.
4 tools: 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the NPPES NPI Registry MCP by usefulapi can do
The NPPES NPI Registry MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
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.
4 tools
Only reads 4Show 4 read-only tools
nppes_lookup_npiLook up a single healthcare provider by their exact 10-digit National Provider Identifier (NPI).No findings
Why it is in this group
- The name "nppes_lookup_npi" says "lookup": a word for reading.
Description, as the server wrote it Look up a single healthcare provider by their exact 10-digit National Provider Identifier (NPI). Returns the full registry record: basic info, addresses, taxonomies/specialties, identifiers and other names. NPPES Read API v2.1.
Annotations the server declares
- title: Look up a provider by NPI number
- readOnlyHint: true
nppes_searchFull-power search of the NPPES NPI Registry across ANY combination of criteria — individual name, organization name, NPI number, taxonomy/specialty, and location.No findings
Why it is in this group
- The name "nppes_search" says "search": a word for reading.
Description, as the server wrote it Full-power search of the NPPES NPI Registry across ANY combination of criteria — individual name, organization name, NPI number, taxonomy/specialty, and location. Use nppes_search_individuals / nppes_search_organizations for the common cases; use this when you need mixed or advanced criteria. The API requires at least one meaningful search parameter. NPPES Read API v2.1.
Annotations the server declares
- title: Search the NPI registry (all criteria)
- readOnlyHint: true
nppes_search_individualsSearch for INDIVIDUAL healthcare providers (NPI-1: doctors, nurses, therapists, etc.) by name, specialty (taxonomy) and/or location.No findings
Why it is in this group
- The name "nppes_search_individuals" says "search": a word for reading.
Description, as the server wrote it Search for INDIVIDUAL healthcare providers (NPI-1: doctors, nurses, therapists, etc.) by name, specialty (taxonomy) and/or location. Provide at least one meaningful criterion beyond a location. Name fields support a trailing '*' wildcard (min 2 chars before it). NPPES Read API v2.1.
Annotations the server declares
- title: Search individual providers
- readOnlyHint: true
nppes_search_organizationsSearch for ORGANIZATION healthcare providers (NPI-2: hospitals, clinics, group practices, pharmacies, labs, etc.) by organization name, specialty (taxonomy) and/or location.No findings
Why it is in this group
- The name "nppes_search_organizations" says "search": a word for reading.
Description, as the server wrote it Search for ORGANIZATION healthcare providers (NPI-2: hospitals, clinics, group practices, pharmacies, labs, etc.) by organization name, specialty (taxonomy) and/or location. The organization_name field supports a trailing '*' wildcard (min 2 chars before it). NPPES Read API v2.1.
Annotations the server declares
- title: Search organization providers
- readOnlyHint: 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 untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://nppes-npi-registry.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://nppes-npi-registry.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 5 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://nppes-npi-registry.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://nppes-npi-registry.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http nppes-npi-registry https://nppes-npi-registry.usefulapi.io/mcpclaude mcp add --transport http nppes-npi-registry https://nppes-npi-registry.usefulapi.io/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__nppes-npi-registry__nppes_lookup_npi",
"mcp__nppes-npi-registry__nppes_search_individuals",
"mcp__nppes-npi-registry__nppes_search_organizations",
"mcp__nppes-npi-registry__nppes_search"
],
"ask": [],
"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 nppes-npi-registry. Review it before you use it.
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.usefulapi/nppes-npi-registry/verify?hash=0c24fe5b81bb48529f31b2c87b49ca3647617a28f18c5c68c6211ddcd932201e" | jq -e '.changed == false'Pinned hash 0c24fe5b81bb, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/nppes-npi-registry/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/nppes-npi-registry)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
NPPES NPI Registry MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the NPPES NPI Registry MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the NPPES NPI Registry MCP by usefulapi delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the NPPES NPI Registry MCP by usefulapi 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 NPPES NPI Registry MCP by usefulapi have?
- 4 tools: 4 read. nppes_lookup_npi, nppes_search_individuals, nppes_search_organizations and nppes_search.
Does the NPPES NPI Registry MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the NPPES NPI Registry MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the NPPES NPI Registry MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.