# io.usefulapi/nppes-npi-registry (remote · nppes-npi-registry.usefulapi.io)

Look up US healthcare providers and organisations by NPI.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `nppes-npi-registry.usefulapi.io`: 75/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-nppes-npi-registry/nppes-npi-registry.md), [page](https://verifymcp.io/servers/io-usefulapi-nppes-npi-registry/nppes-npi-registry)

## Channel facts

- Endpoint: `https://nppes-npi-registry.usefulapi.io/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-10-04.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1245 tokens (~311/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.usefulapi/nppes-npi-registry MCP server?

io.usefulapi/nppes-npi-registry is a hosted endpoint at https://nppes-npi-registry.usefulapi.io/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 io-usefulapi-nppes-npi-registry 'https://nppes-npi-registry.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-nppes-npi-registry": {
      "url": "https://nppes-npi-registry.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-nppes-npi-registry": {
      "type": "http",
      "url": "https://nppes-npi-registry.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-nppes-npi-registry]
url = "https://nppes-npi-registry.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-nppes-npi-registry": {
      "type": "remote",
      "url": "https://nppes-npi-registry.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-nppes-npi-registry --url 'https://nppes-npi-registry.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-nppes-npi-registry:
    url: "https://nppes-npi-registry.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-nppes-npi-registry": {
      "Transport": "http",
      "Url": "https://nppes-npi-registry.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-nppes-npi-registry -t streamable-http -u 'https://nppes-npi-registry.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-nppes-npi-registry": {
      "type": "http",
      "url": "https://nppes-npi-registry.usefulapi.io/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-10-04 (score 75, +7)

- [security improvement] Authorization: partial → pass

### 2026-10-03 (score 68, −6)

- [security regression] Authorization: pass → partial
- [functional improvement] Stability: unverified → 0.03

### 2026-10-02 (score 74, +41)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-10-01 (score 33, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-09-30 (score 28, +10)

- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (4)

### `nppes_lookup_npi` (~91 tokens)

Look up a provider by NPI number

Look up a single healthcare provider by their exact 10-digit National Provider Identifier (NPI). Returns the full registry record: basic info, addresses, taxonomies/specialties, identifiers and other names. NPPES Read API v2.1.

Input parameters:

- `number` (string, required): The 10-digit NPI number to look up, e.g. '1467550004' (required).

### `nppes_search_individuals` (~387 tokens)

Search individual providers

Search for INDIVIDUAL healthcare providers (NPI-1: doctors, nurses, therapists, etc.) by name, specialty (taxonomy) and/or location. Provide at least one meaningful criterion beyond a location. Name fields support a trailing '*' wildcard (min 2 chars before it). NPPES Read API v2.1.

Input parameters:

- `address_purpose` (string): Which address the city/state/postal_code filters apply to (LOCATION = practice address).
- `city` (string): City of the provider's address.
- `country_code` (string): Two-letter country code (default 'US'). Use 'US' for domestic addresses.
- `first_name` (string): Provider first name. A trailing '*' wildcard is allowed, e.g. 'Jo*'.
- `last_name` (string): Provider last name. A trailing '*' wildcard is allowed, e.g. 'Smi*'.
- `limit` (integer): Max number of records to return (1–200, default 10).
- `name_purpose` (string): Which name to match: 'PROVIDER' (default) matches the provider's own name; 'AO' matches an authorized official.
- `postal_code` (string): Postal (ZIP) code; a trailing '*' wildcard is allowed for prefix search, e.g. '941*'.
- `skip` (integer): Number of records to skip, for pagination (0–1000; combined with limit, up to 1200 records reachable).
- `state` (string): Two-letter U.S. state/territory abbreviation, e.g. 'CA', 'NY', 'PR'.
- `taxonomy_description` (string): Provider taxonomy / specialty text, e.g. 'cardiology', 'Pediatrics', 'Social Worker'. Partial matches supported; a trailing '*' wildcard is allowed (min 2 chars before it).

### `nppes_search_organizations` (~325 tokens)

Search organization providers

Search for ORGANIZATION healthcare providers (NPI-2: hospitals, clinics, group practices, pharmacies, labs, etc.) by organization name, specialty (taxonomy) and/or location. The organization_name field supports a trailing '*' wildcard (min 2 chars before it). NPPES Read API v2.1.

Input parameters:

- `address_purpose` (string): Which address the city/state/postal_code filters apply to (LOCATION = practice address).
- `city` (string): City of the provider's address.
- `country_code` (string): Two-letter country code (default 'US'). Use 'US' for domestic addresses.
- `limit` (integer): Max number of records to return (1–200, default 10).
- `organization_name` (string): Organization (legal business) name. A trailing '*' wildcard is allowed, e.g. 'Kaiser*'.
- `postal_code` (string): Postal (ZIP) code; a trailing '*' wildcard is allowed for prefix search, e.g. '941*'.
- `skip` (integer): Number of records to skip, for pagination (0–1000; combined with limit, up to 1200 records reachable).
- `state` (string): Two-letter U.S. state/territory abbreviation, e.g. 'CA', 'NY', 'PR'.
- `taxonomy_description` (string): Provider taxonomy / specialty text, e.g. 'cardiology', 'Pediatrics', 'Social Worker'. Partial matches supported; a trailing '*' wildcard is allowed (min 2 chars before it).

### `nppes_search` (~442 tokens)

Search the NPI registry (all criteria)

Full-power search of the NPPES NPI Registry across ANY combination of criteria — individual name, organization name, NPI number, taxonomy/specialty, and location. Use nppes_search_individuals / nppes_search_organizations for the common cases; use this when you need mixed or advanced criteria. The API requires at least one meaningful search parameter. NPPES Read API v2.1.

Input parameters:

- `address_purpose` (string): Which address the city/state/postal_code filters apply to (LOCATION = practice address).
- `city` (string): City of the provider's address.
- `country_code` (string): Two-letter country code (default 'US'). Use 'US' for domestic addresses.
- `enumeration_type` (string): Restrict to 'NPI-1' (individuals) or 'NPI-2' (organizations). Omit to search both.
- `first_name` (string): Individual provider first name (trailing '*' wildcard allowed).
- `last_name` (string): Individual provider last name (trailing '*' wildcard allowed).
- `limit` (integer): Max number of records to return (1–200, default 10).
- `name_purpose` (string): For name matching: 'PROVIDER' (default) or 'AO' (authorized official).
- `number` (string): Exact 10-digit NPI number.
- `organization_name` (string): Organization name (trailing '*' wildcard allowed).
- `postal_code` (string): Postal (ZIP) code; a trailing '*' wildcard is allowed for prefix search, e.g. '941*'.
- `skip` (integer): Number of records to skip, for pagination (0–1000; combined with limit, up to 1200 records reachable).
- `state` (string): Two-letter U.S. state/territory abbreviation, e.g. 'CA', 'NY', 'PR'.
- `taxonomy_description` (string): Provider taxonomy / specialty text, e.g. 'cardiology', 'Pediatrics', 'Social Worker'. Partial matches supported; a trailing '*' wildcard is allowed (min 2 chars before it).

## Diagnostics

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

## Score history

- 2026-10-04: 75
- 2026-10-03: 68
- 2026-10-02: 74
- 2026-10-01: 33
- 2026-09-30: 28
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/nppes-npi-registry MCP server?

io.usefulapi/nppes-npi-registry is an MCP server listed in the public MCP registry as io.usefulapi/nppes-npi-registry. Look up US healthcare providers and organisations by NPI. This page covers its hosted endpoint (https://nppes-npi-registry.usefulapi.io/mcp).

### Is the io.usefulapi/nppes-npi-registry MCP server safe to use?

io.usefulapi/nppes-npi-registry scores 75 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 io.usefulapi/nppes-npi-registry MCP server expose?

io.usefulapi/nppes-npi-registry exposes 4 tools: nppes_lookup_npi, nppes_search_individuals, nppes_search_organizations, nppes_search. Their descriptions and schemas cost roughly 1,245 tokens of context every time the server is loaded.

### Does the io.usefulapi/nppes-npi-registry MCP server require authentication?

Yes. io.usefulapi/nppes-npi-registry asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.usefulapi/nppes-npi-registry MCP server still maintained?

io.usefulapi/nppes-npi-registry is still listed as active in the MCP registry. We last reached this channel on 4 October 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://nppes-npi-registry.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-nppes-npi-registry/nppes-npi-registry.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-nppes-npi-registry/nppes-npi-registry.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-nppes-npi-registry/nppes-npi-registry