Tuper NPI Registry
REMOTE · MCP-NPI.TUPER.APP
Validate, look up and count US NPI providers from the public CMS registry; not affiliated with CMS.
Available components
Last scanned (1 hour ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 624 tokens (~156/item across 4 items; 4 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 25% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 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.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 67
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 5 Nov 2026 · Probed https://mcp-npi.tuper.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp-npi.tuper.app | CN=YR2,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | RSA 2048 | SHA256-RSA | 576c8b6addb118ad0dc2044ca5b993cd59a |
| SANs: mcp-npi.tuper.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-npi.tuper.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| tuper.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-npi.tuper.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp-npi.tuper.app/mcp | HTTPS enforced | 301 | https://mcp-npi.tuper.app/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
count_by_specialty Count providers by specialty and state ~102
How many providers does the NPI Registry list for a specialty, optionally in a state or ZIP prefix? Exact up to 1,200; beyond that it says "1200+" and points to the full-list route. Up to 5 specialties per call.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | – |
| postal_code | string | – | ZIP prefix with *, e.g. "100*" |
| specialties | array | yes | – |
| state | string | – | – |
No output schema declared.
No examples provided.
lookup_npi Look up NPI numbers ~65
Fetch 1-20 providers by NPI number from the live CMS NPI Registry: name, credential, status, primary specialty (taxonomy), practice address and phone. Check digits are validated first; invalid and unknown numbers are reported separately.
| Name | Type | Req | Description |
|---|---|---|---|
| npis | array | yes | – |
No output schema declared.
No examples provided.
search_providers Search providers ~217
Search the live NPI Registry by first/last name, organization name, specialty (taxonomy description as the registry writes it, e.g. "Family Medicine", "Dentist"), state (2 letters), city or ZIP. Needs at least one of name, organization, specialty, city or ZIP (a state alone is refused by CMS). Returns up to 50 rows and how many exist (capped at 1,200). Full lists beyond that: https://tuper.app/tools/npi-list-by-specialty/?src=mcp-npi
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| entity | string | – | – |
| first_name | string | – | – |
| last_name | string | – | – |
| limit | integer | – | – |
| organization_name | string | – | – |
| postal_code | string | – | 5 digits or a prefix with * |
| skip | integer | – | – |
| specialty | string | – | taxonomy description, e.g. "Pediatrics" |
| state | string | – | 2-letter US state code |
No output schema declared.
No examples provided.
validate_npi Validate NPI check digit ~65
Offline check of up to 50 NPI numbers: 10 digits and the Luhn check digit (prefix 80840). Does not call CMS, so it cannot say whether the number is issued; use lookup_npi for that.
| Name | Type | Req | Description |
|---|---|---|---|
| npis | array | yes | – |
No output schema declared.
No examples provided.
How do I install the Tuper NPI Registry MCP server?
Tuper NPI Registry is a hosted endpoint at https://mcp-npi.tuper.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp-npi.tuper.app
claude mcp add --transport http app-tuper-npi 'https://mcp-npi.tuper.app/mcp'
What is the Tuper NPI Registry MCP server?
Tuper NPI Registry is an MCP server listed in the public MCP registry as app.tuper/npi. Validate, look up and count US NPI providers from the public CMS registry; not affiliated with CMS. This page covers its hosted endpoint (https://mcp-npi.tuper.app/mcp).
Is the Tuper NPI Registry MCP server safe to use?
Tuper NPI Registry scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tuper NPI Registry MCP server expose?
Tuper NPI Registry exposes 4 tools: validate_npi, lookup_npi, search_providers, count_by_specialty. Their descriptions and schemas cost roughly 449 tokens of context every time the server is loaded.
Does the Tuper NPI Registry MCP server require authentication?
No. We connected to Tuper NPI Registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tuper NPI Registry MCP server still maintained?
Tuper NPI Registry is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.