npi-registry
No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked
NPI Registry is a hosted MCP server that exposes tools for searching healthcare providers by name, organization, taxonomy, postal code, or state and retrieving a provider by 10-digit NPI. Developers can call it through a JSON-RPC HTTP endpoint or connect it to AI agents.
Inferred · not functionally tested
Overview
6 featuresPurpose: Finding and retrieving healthcare provider information by NPI or provider attributes.
Inferred · not functionally tested
Audience: developers building AI agents and healthcare data applications
Inferred · not functionally tested
Functions: data_extraction
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown
Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: gateway.pipeworx.io. These links do not verify the individual claims.
npi-registry sits in PulseGate's API design, testing & docs category. Inferred · not functionally tested: It focuses on finding and retrieving healthcare provider information by NPI or provider attributes. Inferred · not functionally tested: npi-registry is a B2B product aimed at developers building AI agents and healthcare data applications. Basis unknown · not verified: It runs on the web and API.
It is developed by Pipeworx. Inferred · not functionally tested: Key capabilities include provider search, NPI lookup, and field filtering. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Provider search
- NPI lookup
- Field filtering
- JSON-RPC endpoint
- MCP tools
- Live playground
Topics: Inferred · not functionally tested
Built with & integrations
- Cloudflare
- cf-ray header
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed10 Oct · 00:02 UTCNpi Registry seen via MCP Registry (official)Source: MCP Registry (official) · Open
Frequently asked questions about npi-registry
- What does npi-registry do?
- Inferred · not functionally tested: Npi-registry focuses on finding and retrieving healthcare provider information by NPI or provider attributes. It is catalogued under API design, testing & docs on PulseGate.
- Who should use npi-registry?
- Inferred · not functionally tested: npi-registry is a B2B product built for developers building AI agents and healthcare data applications.
- What platforms does npi-registry run on?
- Basis unknown · not verified: npi-registry runs on the web and API.
- Is npi-registry still active?
- Unverified. npi-registry has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
- What projects are similar to npi-registry?
- Similar projects tracked by PulseGate include nps, bioregistry, and Pipeworx.npsbioregistryPipeworx
- Who develops npi-registry?
- npi-registry is developed by Pipeworx.
- Does npi-registry have an API or integrations?
- Inferred · not functionally tested: Yes — npi-registry exposes an MCP server and a public API.
Similar projects
Closest matches by what these projects do