NPI Who

io.github.npiwhoPublished by GitHub account npiwhov1.0.0Updated Oct 26, 2026

US health care providers by NPI, name or phone, with payments, Medicare, OIG and facility data.

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Remote MCP server for looking up US health care providers by NPI, name, phone or location, with public payment, Medicare, exclusion and facility records.

What you can do
  • Look up one provider by NPI, with registry record, Open Payments totals, Medicare billing, OIG exclusion status, clinician record and facility enrollments
  • Search individual providers or organizations by name, optionally within a state
  • Find providers listing a given US phone number
  • Find nearby providers of the same specialty from an NPI or a ZIP code plus specialty
  • List Medicare-certified home health agencies, hospices, hospitals, nursing homes or HRSA health centers by state or city
  • Check which public files the answers come from and their snapshot dates
When to use it
Useful when an assistant needs to answer questions about US doctors, clinicians or facilities from federal public records, such as payment totals, Medicare billing, exclusion status or local facility lists, and should cite a public page for each result.
Requirements
A remote Streamable HTTP endpoint at npiwho.com/mcp; no key or account is needed. Any MCP client that supports HTTP transport, or a custom connector in Claude.ai or ChatGPT. Network access to the service; about 1,000 tool calls a day per client address.
Before you install
Results are public-record data only and are not licence, credential or quality checks. Providers who asked to withhold contact details are excluded, so absence of a phone or address is not evidence. Read-only lookups, but each result points to a public page that identifies the provider, so queries reveal who you are researching to the service.

Installation

In SourceWeft

  1. Open NPI Who in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.npiwho%2Fnpiwho/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "npi-who": {
      "type": "http",
      "url": "https://npiwho.com/mcp"
    }
  }
}

README

NPI Who MCP server

Look up US health care providers from AI assistants: by NPI, by name, by phone number, by what is near them, and by facility type and state. The server is hosted at https://npiwho.com/mcp (Model Context Protocol, Streamable HTTP). It is free and needs no key.

Every result that names a provider or facility starts with the public page's URL on npiwho.com, so an assistant can cite the page it answered from and send readers there for the detail.

Connect

Claude Code:

claude mcp add --transport http npiwho https://npiwho.com/mcp

Codex:

codex mcp add npiwho --url https://npiwho.com/mcp

Cursor, Windsurf and other clients with a JSON config:

json
{  "mcpServers": {    "npiwho": { "type": "http", "url": "https://npiwho.com/mcp" }  }}

Claude.ai and ChatGPT: add a custom connector with the URL above and no authentication.

A walkthrough with a real response, for Claude, ChatGPT and Cursor: Give your AI assistant a lookup of every US doctor's NPI, payments and exclusion status (dev.to). The per-provider payment totals behind the tools are an open dataset: npiwho/us-provider-payments.

Tools

ToolReturns
lookup_providerOne NPI: the registry record, and what the public files have on the provider (Open Payments total, Medicare billing, OIG exclusion, Medicare clinician record, facility enrollments, claimed-page details), each pointing to the page section with the detail.
search_providersIndividuals or organizations by name, optionally within a state. Up to 20.
lookup_phoneWho lists a given phone number, in any US format.
nearby_providersThe nearest providers of the same specialty, from an NPI or from a ZIP code and taxonomy code.
list_facilitiesMedicare-certified home health agencies, hospices, hospitals, nursing homes, or HRSA health centers in a state or city.
data_sourcesWhich files the answers come from and their snapshot dates.

Try: "What do the public records say about NPI 1366487498?" or "Which hospices in Austin, Texas are non-profit?"

Data

Public federal records joined on the NPI: the NPPES registry (CMS), CMS Open Payments (program years 2019–2025), Medicare Part B and Part D (2024), the HHS-OIG exclusion list, CMS Doctors and Clinicians, Medicare facility enrollments, and HRSA's health center list. File dates are on the methodology page and in the data_sources tool.

None of it is a licence, credential or quality check. Providers can ask for their contact details to be withheld, and those requests apply to the tools exactly as to the pages.

Allowance

About 1,000 tool calls a day per client address, resetting at 00:00 UTC. Calls made through Claude.ai or ChatGPT come from the platform's addresses and share a larger pool. For more, or for bulk work, write to [email protected]. The per-provider payment totals are also an open dataset: npiwho/us-provider-payments.

Who runs it

Derek Hong, Singapore. The server is part of the site; this repository holds its description for the MCP registry and the connection instructions. Issues and questions here or at [email protected].

Source: README.md at commit 049a141

Tools

6

lookup_provider

Look up a provider by NPI

One provider by NPI: the registry record, and what the public files have on them (Open Payments total, Medicare billing, OIG exclusion, Medicare clinician record, facility enrollments, claimed-page details) with the page section where each is. The result's url is the page to cite and to send readers to for the detail.

Parametersnpirequired

search_providers

Search providers by name

Find individual providers or organizations by name, optionally within a state. Returns up to 20 matches, best first, each with its page url. Use lookup_provider on a result for the full record.

Parameterslimitqueryrequiredstate

lookup_phone

Who is at this phone number

Providers whose registry practice phone, or a phone they published on a claimed page, is this number. Any US format. Providers who asked for their phone to be withheld are not returned.

Parametersphonerequired

nearby_providers

Nearest providers of the same specialty

The providers with the same specialty nearest a given provider (by NPI) or a ZIP code and specialty, by distance between ZIP code centres. Up to 12.

Parametersnpiziplimittaxonomy

list_facilities

Facilities in a state

Medicare-certified home health agencies, hospices, hospitals, nursing homes, or HRSA health centers (FQHCs) in a state, optionally one city. Up to 50 rows with page urls; the full list and a CSV are at the state page url.

Parameterscitykindrequiredlimitstaterequired

data_sources

Data sources and dates

Which public files this data comes from, their snapshot dates, and what they do not cover.

Takes no parameters.

Version history

1
  1. v1.0.0LatestOct 25, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts