protogrid

Search / app.tuper/npi

Tuper NPI Registry

R0· no sign-in

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

v1.0.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality81new
Trust83of 100
Uptime, 30 days100%
Latency p50549 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "npi": {
      "type": "http",
      "url": "https://mcp-npi.tuper.app/mcp"
    }
  }
}
claude mcp add --transport http npi https://mcp-npi.tuper.app/mcp
[mcp_servers.npi]
url = "https://mcp-npi.tuper.app/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "npi": {
      "type": "remote",
      "url": "https://mcp-npi.tuper.app/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "npi": {
      "type": "http",
      "url": "https://mcp-npi.tuper.app/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=npi&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLW5waS50dXBlci5hcHAvbWNwIn0%3D"
}
{
  "servers": {
    "npi": {
      "type": "http",
      "url": "https://mcp-npi.tuper.app/mcp"
    }
  }
}
{
  "mcpServers": {
    "npi": {
      "httpUrl": "https://mcp-npi.tuper.app/mcp"
    }
  }
}
extensions:
  "npi":
    enabled: true
    name: "npi"
    type: streamable_http
    uri: "https://mcp-npi.tuper.app/mcp"
    timeout: 300

Quality 81 / 100new

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene86 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations4 of 4 tools declare readOnlyHint or destructiveHint
  • fail
    tools.directory_hintsno 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_costabout 652 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stabilityn/a · weight 15
  • n/a
    stability.changes, stability.rug_pulltool history recorded for 5 of the 7 days needed
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

4 tools, about 652 tokens to load them all · tool set b715c7eb864b · checked 2026-11-07 17:28 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 83 / 100

no-repository
provenance55
liveness100
freshness100
hygiene80

+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. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://mcp-npi.tuper.app/mcp streamable-httpnoneyes100%549 ms2025-11-252026-11-07

Tools (4)

count_by_specialtyread-onlyHow 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_npiread-onlyFetch 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_providersread-onlySearch 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_npiread-onlyOffline 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.

Schemas: list_tools.

Similar MCP servers

More from app.tuper

And 6 more from this publisher.

Official server.json
{
  "name": "app.tuper/npi",
  "title": "Tuper NPI Registry",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://mcp-npi.tuper.app/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "websiteUrl": "https://tuper.app/tools/npi-list-by-specialty/mcp/?src=mcp-registry",
  "description": "Validate, look up and count US NPI providers from the public CMS registry; not affiliated with CMS."
}