Tuper NPI Registry

Is Tuper NPI Registry MCP server safe?

• None of the hidden-instruction wordings we know were found in its tool descriptions.
• Its error messages showed no secrets or internal details.
• All 4 of its tools are labeled read-only.
• Overall it scored 83/100 on 2 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What it can do

4 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Ready for the newest MCP version

  1 warning

  • !Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
  note
• !
  Every tool is described

  4 warnings

  • !validate_npi: Inputs with no description: npis
  • !lookup_npi: Inputs with no description: npis
  • !search_providers: Inputs with no description: first_name, last_name, organization_name, city, entity, limit, skip
  • !count_by_specialty: Inputs with no description: specialties, state, entity
  note
• !
  Bad inputs give a clean error

  4 warnings

  • !validate_npi: Accepted missing required input "npis" without complaining
  • !validate_npi: Accepted wrong type for "npis" without complaining
  • !lookup_npi: Accepted wrong type for "npis" without complaining
  • !search_providers: Accepted wrong type for "first_name" without complaining
  • and 3 more
  note
• ✓
  ConnectsConnected in 1.1 s
  pass
• ✓
  Lists its toolsFound 4 tools
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
  pass
• ✓
  Tools work with good inputs

  All good

  • ✓validate_npi: Worked (144 ms)
  • ✓lookup_npi: Worked (144 ms)
  • ✓search_providers: Answered with an error, probably because of our sample input: Error: Give at least one of name, organization_name, specialty, city or postal_code (CMS refuses a state alone).
  • ✓count_by_specialty: Answered with an error, probably because of our sample input: Error: taxonomy_description: No taxonomy codes found with entered description
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 1.1 s
  • ✓Listing tools took 145 ms
  • ✓Average tool answer: 226 ms
  • ✓count_by_specialty: Slowest tool: count_by_specialty (473 ms)
  pass
• ✓
  No secrets leakedChecked 5 error messages: no secrets or internal details
  pass
• ✓
  Follows MCP best practices (not scored yet)Tool names, safety labels and tool list size follow the MCP guide
  pass
• –
  Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)
  not tested

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 2 Nov 202683

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use Tuper NPI Registry, signed in with GitHub, one per person. Reviews never change the score.