Skip to content

Tuper NPI Registry

app.tuper/npituper.appstreamable-httpv1.0.0Scanned

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

4 tools: 4 only read.

Tools: 0 delete, 0 irreversible, 0 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

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 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 →

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
  • count_by_specialtyHow many providers does the NPI Registry list for a specialty, optionally in a state or ZIP prefix?Reads text others writeNo findings

    Why it is in this group

    • The name "count_by_specialty" says "count": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • lookup_npiFetch 1-20 providers by NPI number from the live CMS NPI Registry: name, credential, status, primary specialty (taxonomy), practice address and phone.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "lookup_npi" says "lookup": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "credential": it reads secrets.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...r from the live CMS NPI Registry: name, credential, status, primary specialty (taxonomy),..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • search_providersSearch the live NPI Registry by first/last name, organization name, specialty (taxonomy description as the registry writes it, e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "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.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • validate_npiOffline check of up to 50 NPI numbers: 10 digits and the Luhn check digit (prefix 80840).No findings

    Why it is in this group

    • The name "validate_npi" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

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 outbound.

Reads private data1
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.

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description mentions "credential".

    Matched text

    description: "...r from the live CMS NPI Registry: name, credential, status, primary specialty (taxonomy),..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http npi https://mcp-npi.tuper.app/mcp
claude mcp add --transport http npi https://mcp-npi.tuper.app/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__npi__validate_npi",
      "mcp__npi__lookup_npi",
      "mcp__npi__search_providers",
      "mcp__npi__count_by_specialty"
    ],
    "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 npi. Review it before you use it.

Capability tags behind 3 rules
  • mcp__npi__lookup_npi private-data, untrusted-input
  • mcp__npi__search_providers untrusted-input
  • mcp__npi__count_by_specialty 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://anlyon.dev/api/v1/servers/app.tuper/npi/verify?hash=a368d487e96ed852dcdfee48039a3818a582fdd8cecf44045b63fc6a4961d10f" | jq -e '.changed == false'

Pinned hash a368d487e96e, from Nov 2, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/app.tuper/npi/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for app.tuper/npi
[![anlyon.dev](https://anlyon.dev/badge/app.tuper/npi.svg)](https://anlyon.dev/servers/app.tuper/npi)

Source: MCP Registry. Synced Nov 2, 2026, 03:17 UTC.