# Tuper NPI Registry

> Validate, look up and count US NPI providers from the public CMS registry; not affiliated with CMS.

- name: app.tuper/npi
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 81/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/app.tuper%2Fnpi
- tools: https://api.protogrid.dev/v1/servers/app.tuper%2Fnpi/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "npi": {
      "type": "http",
      "url": "https://mcp-npi.tuper.app/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-6d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 81/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 4 of 4 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: search_providers (destructiveHint, idempotentHint); count_by_specialty (destructiveHint, idempotentHint); validate_npi (destructiveHint, idempotentHint); …
- pass `tools.token_cost`: about 652 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 5 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 4, about 652 tokens to load them all
- tool set hash: b715c7eb864bdfabb5e8909861bb0f9a
- badge: [![protogrid quality](https://protogrid.dev/badge/app.tuper/npi.svg)](https://protogrid.dev/servers/app.tuper/npi)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp-npi.tuper.app/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (4)

- `count_by_specialty`: 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.
- `lookup_npi`: 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.
- `search_providers`: 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
- `validate_npi`: 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.