Healthcare Provider MCP (NPI) avatar

Healthcare Provider MCP (NPI)

Pricing

from $0.01 / 1,000 results

Go to Apify Store
Healthcare Provider MCP (NPI)

Healthcare Provider MCP (NPI)

MCP server that lets AI agents search and look up US healthcare providers from the public NPI Registry. Tools: search_providers, get_provider.

Pricing

from $0.01 / 1,000 results

Rating

0.0

(0)

Developer

Technical Dost Solutions

Technical Dost Solutions

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

4 days ago

Last modified

Share

An MCP server that lets AI agents (Claude, ChatGPT, Cursor, and any MCP client) search and look up US healthcare providers from the official public NPI Registry — doctors, nurses, pharmacies, clinics, hospitals.

Built on the same precision-first engine as the NPI Registry scraper: every search result is verified to actually match your query (the NPI API silently returns noise for broad common names; this server filters it out).

Two ways to use it

1. As an MCP server (for AI agents)

When run in Standby mode, the Actor exposes an MCP endpoint at /mcp (Streamable HTTP, JSON-RPC 2.0). Point any MCP client at the Actor's Standby URL + /mcp, or call it through Apify's MCP integration using actorName:toolName.

Tools:

ToolArgumentsReturns
search_providerslastName, firstName, organizationName, taxonomy, city, state, providerType (any/individual/organization), limit (1–200)Array of verified providers
get_providernpi (10-digit)A single provider record

Example tools/call:

{ "jsonrpc": "2.0", "id": 1, "method": "tools/call",
"params": { "name": "search_providers",
"arguments": { "taxonomy": "Cardiology", "city": "Austin", "state": "TX", "limit": 10 } } }

2. As a normal Actor (batch / testing)

Run it with input and it executes one tool, storing results in the dataset:

{ "tool": "search_providers", "lastName": "Smith", "state": "TX", "taxonomy": "Family Medicine", "limit": 20 }
{ "tool": "get_provider", "npi": "1760914097" }

Output fields

npi, enumerationType, providerName, credential, organizationName, primaryTaxonomy, primaryTaxonomyCode, addressLine1, city, state, postalCode, phone, npiUrl.

Pricing

Pay per event — priced per tool call (e.g. per search_providers / get_provider action). Per-action pricing is ideal for agent workloads.

Reliability

  • Verified matches only (post-filtering defeats the NPI API's broad-query noise).
  • Exponential backoff on rate limits / server errors.
  • Stateless MCP server — no sessions to leak, no proxies, no credentials.

Data usage & compliance

All data comes from the public NPI Registry operated by CMS, published in the public domain. This server performs only lookups against the official public API. Use the data in accordance with applicable laws; do not use it for spam or harassment.