NPILayer
REMOTE · NPILAYER.COM
Look up U.S. healthcare providers by NPI, name, specialty and ZIP radius from CMS NPPES data.
Available components
Last scanned (1 day ago)
Scores higher than 52% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Health and Science
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 596 tokens (~198/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://npilayer.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=npilayer.com | CN=YE2,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5b65b0b0cecb8eb356b1cff6e129ebe47c2 |
| SANs: *.npilayer.com, npilayer.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of npilayer.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| npilayer.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://npilayer.com/mcp | Verified | 200 | |
| http (plaintext) | http://npilayer.com/mcp | HTTPS enforced | 301 | https://npilayer.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lookup_npi Look up an NPI ~89
Look up a single U.S. healthcare provider or organization by its 10-digit National Provider Identifier (NPI), from CMS NPPES data. An NPI record identifies a provider; it does not indicate licensure, credentialing, network participation, or current practice status.
| Name | Type | Req | Description |
|---|---|---|---|
| npi | string | yes | A 10-digit National Provider Identifier, e.g. "1932586781". |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object|null | yes | – |
| meta | object | yes | – |
No examples provided.
providers_near Find providers near a location ~225
Find U.S. healthcare providers within a radius of a ZIP code or coordinate, from CMS NPPES data. Provide either "zip", or both "lat" and "lng". Distance is measured from each provider's primary practice location to the ZIP centroid (not an exact street address), since NPILayer's geography is ZIP-based.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_type | string | – | Restrict to individual providers or organizations, e.g. to exclude group practices from "find a cardiologist" results. |
| lat | number | – | Latitude, used with "lng" instead of "zip". |
| limit | integer | – | – |
| lng | number | – | Longitude, used with "lat" instead of "zip". |
| page | integer | – | – |
| radius | number | – | Radius in miles. |
| specialty | string | – | A plain-language specialty, e.g. "cardiology". |
| taxonomy | string | – | An exact NUCC taxonomy code, e.g. "207RC0000X". |
| zip | string | – | A 5-digit ZIP code to search around. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| meta | object | yes | – |
No examples provided.
search_providers Search providers ~187
Search U.S. healthcare providers and organizations by name, location, or specialty, from CMS NPPES data. Provide at least one filter; an empty search returns an arbitrary page of providers rather than a meaningful result.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| entity_type | string | – | – |
| first_name | string | – | – |
| last_name | string | – | – |
| limit | integer | – | – |
| name | string | – | Matches first name, last name, or organization name. |
| organization | string | – | – |
| page | integer | – | – |
| specialty | string | – | A plain-language specialty, e.g. "cardiology". |
| state | string | – | Two-letter state code, e.g. "MI". |
| taxonomy | string | – | An exact NUCC taxonomy code, e.g. "207RC0000X". |
| zip | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| meta | object | yes | – |
No examples provided.
How do I install the NPILayer MCP server?
NPILayer is a hosted endpoint at https://npilayer.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.
remote · npilayer.com
claude mcp add --transport http com-npilayer-npilayer 'https://npilayer.com/mcp'
What is the NPILayer MCP server?
NPILayer is an MCP server listed in the public MCP registry as com.npilayer/npilayer. Look up U.S. healthcare providers by NPI, name, specialty and ZIP radius from CMS NPPES data. This page covers its hosted endpoint (https://npilayer.com/mcp).
Is the NPILayer MCP server safe to use?
NPILayer scores 66 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 NPILayer MCP server expose?
NPILayer exposes 3 tools: lookup_npi, search_providers, providers_near. Their descriptions and schemas cost roughly 501 tokens of context every time the server is loaded.
Does the NPILayer MCP server require authentication?
No. We connected to NPILayer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NPILayer MCP server still maintained?
NPILayer is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.