# NPI Who (remote · npiwho.com)

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

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `npiwho.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/npiwho-npiwho/npiwho.md), [page](https://verifymcp.io/servers/npiwho-npiwho/npiwho)

## Channel facts

- Endpoint: `https://npiwho.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 709 tokens (~118/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 62% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the NPI Who MCP server?

NPI Who is a hosted endpoint at https://npiwho.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "npiwho-npiwho": {
      "url": "https://npiwho.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "npiwho-npiwho": {
      "type": "http",
      "url": "https://npiwho.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.npiwho-npiwho]
url = "https://npiwho.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "npiwho-npiwho": {
      "type": "remote",
      "url": "https://npiwho.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add npiwho-npiwho --url 'https://npiwho.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  npiwho-npiwho:
    url: "https://npiwho.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "npiwho-npiwho": {
      "Transport": "http",
      "Url": "https://npiwho.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add npiwho-npiwho -t streamable-http -u 'https://npiwho.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 67, +4)

- [security improvement] HSTS header: fail → pass
- [security] Tool “data_sources” rewrote its description, which is the text the model reads
- [security] Tool “list_facilities” rewrote its description, which is the text the model reads
- [security] Tool “lookup_phone” rewrote its description, which is the text the model reads
- [security] Tool “lookup_provider” rewrote its description, which is the text the model reads
- [security] Tool “nearby_providers” rewrote its description, which is the text the model reads
- [security] Tool “search_providers” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail

### 2026-10-26 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 63)

First indexed and scored.

## MCP tools (6)

### `lookup_provider` (~111 tokens)

Look up a provider by NPI

Use when the question names an NPI, or after search_providers has found the right person. 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.

Input parameters:

- `npi` (string, required): The 10-digit National Provider Identifier

### `search_providers` (~112 tokens)

Search providers by name

Use when the question names a person or practice but no NPI. 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.

Input parameters:

- `limit` (integer)
- `query` (string, required): A person's name ('maria gonzalez', 'gonzalez'), or an organization name
- `state` (string): Two-letter state code, e.g. TX

### `lookup_phone` (~71 tokens)

Who is at this phone number

Use when the question is who a phone number belongs to. 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.

Input parameters:

- `phone` (string, required): A US phone number in any format

### `nearby_providers` (~129 tokens)

Nearest providers of the same specialty

Use when the question is who else does this nearby, or for alternatives to a provider. 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.

Input parameters:

- `limit` (integer)
- `npi` (string): Start from this provider's specialty and ZIP
- `taxonomy` (string): NUCC taxonomy code, e.g. 207Q00000X for family medicine; required with zip
- `zip` (string): Or a 5-digit ZIP code, with taxonomy

### `list_facilities` (~117 tokens)

Facilities in a state

Use when the question is about facilities of a kind in a state or city rather than one named provider. 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.

Input parameters:

- `city` (string)
- `kind` (string, required)
- `limit` (integer)
- `state` (string, required): Two-letter state code

### `data_sources` (~46 tokens)

Data sources and dates

Use when asked how current or how reliable the data is, or what it does not include. Which public files this data comes from, their snapshot dates, and what they do not cover.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/npiwho-npiwho/npiwho#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 67
- 2026-10-27: 67
- 2026-10-26: 63
- 2026-10-25: 63

## Common questions

### What is the NPI Who MCP server?

NPI Who is an MCP server listed in the public MCP registry as io.github.npiwho/npiwho. US health care providers by NPI, name or phone, with payments, Medicare, OIG and facility data. This page covers its hosted endpoint (https://npiwho.com/mcp).

### Is the NPI Who MCP server safe to use?

NPI Who scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the NPI Who MCP server expose?

NPI Who exposes 6 tools: lookup_provider, search_providers, lookup_phone, nearby_providers, list_facilities, data_sources. Their descriptions and schemas cost roughly 586 tokens of context every time the server is loaded.

### Does the NPI Who MCP server require authentication?

No. We connected to NPI Who without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the NPI Who MCP server still maintained?

NPI Who is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://npiwho.com/mcp
- Repository: https://github.com/npiwho/mcp
- Website: https://npiwho.com/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/npiwho-npiwho/npiwho.xml
- Changelog JSON feed: https://verifymcp.io/servers/npiwho-npiwho/npiwho.json
- HTML version of this page: https://verifymcp.io/servers/npiwho-npiwho/npiwho