NPI Who

io.github.npiwho由 GitHub 账号 npiwho 发布v1.0.0更新于 Oct 26, 2026

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

已验证Streamable HTTP可网页运行位置与生活数据与分析

概览

AI 生成的概览

远程 MCP 服务器,可按 NPI、姓名、电话或位置查询美国医疗提供者,并附带公开的支付、Medicare、排除名单与机构记录。

可以做什么
  • 按 NPI 查询单个提供者,返回注册记录、Open Payments 支付总额、Medicare 计费、OIG 排除状态、临床医生记录与机构登记
  • 按姓名搜索个人提供者或机构,可限定州
  • 按美国电话号码查找登记该号码的提供者
  • 按 NPI 或邮编加专科查找同专科的邻近提供者
  • 按州或城市列出 Medicare 认证的家庭健康机构、临终关怀机构、医院、养老院或 HRSA 健康中心
  • 查看答案所依据的公开数据文件及其快照日期
适用场景
当助手需要依据联邦公开记录回答关于美国医生、临床医生或医疗机构的问题时适用,例如支付总额、Medicare 计费、排除状态或本地机构名单,并可为每条结果引用公开页面。
运行要求
使用 npiwho.com/mcp 的远程 Streamable HTTP 端点,无需密钥或账号。需要支持 HTTP 传输的 MCP 客户端,或在 Claude.ai、ChatGPT 中添加自定义连接器。需能访问该服务网络;每个客户端地址每天约 1,000 次工具调用。
安装前请注意
结果仅为公开记录数据,不构成执照、资质或质量审查。要求隐藏联系方式的提供者不会返回,因此查不到电话或地址并不代表不存在。查询为只读,但每条结果都指向可识别该提供者的公开页面,查询内容会透露你正在调查谁。

安装

在 SourceWeft 中

  1. 打开 控制台中的 NPI Who,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.npiwho%2Fnpiwho/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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].

来源:README.md,提交 049a141

工具

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.

输入参数npi必填

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.

输入参数limitquery必填state

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.

输入参数phone必填

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.

输入参数npiziplimittaxonomy

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.

输入参数citykind必填limitstate必填

data_sources

Data sources and dates

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

无需输入参数。

版本历史

1
  1. v1.0.0最新Oct 25, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分