Npi, name, organization_name, city, state, postal_code and specialty mean you can arrive with any fragment of the question, including the NPI number you are trying to confirm rather than find. Wildcard support after 2 characters is what makes that practical, since the field a caller is least sure of is usually the spelling of a name. limit caps how much comes back, so a broad prefix search is deliberately a wide result set rather than a truncated one. It reads a public registry and asks for no credential, which makes it cheap to wire in for verification work where the alternative is a browser tab and manual transcription.
A single-call lookup over the United States National Provider Identifier registry, covering both individual healthcare providers and organizations.
- One search that accepts the question from whichever end you have it: search_npi_registry takes npi, first_name, last_name, organization_name, city, state, postal_code and specialty, capped by limit.
- Fuzzy matching on text fields: a trailing '*' after at least 2 characters matches on a prefix, as in 'smith*' or 'hosp*', so a partial surname or organization name is a usable query.
Nothing — no account, no key.
One command — uvx npi-registry-mcp-server