Npi Providers MCP Server
by npi-providers.caseyjhand.com in Search & web
Search NPPES providers and resolve NUCC specialty codes via MCP over STDIO or Streamable HTTP.
https://npi-providers.caseyjhand.com/mcp- Tools
- 3
- open to any client
- Uptime
- 100%
- last 30 days
- Response time
- 433 ms
- 517 ms slowest 5%
- Last check
- Passed
- 7 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"npi-providers-mcp-server": {
"type": "http",
"url": "https://npi-providers.caseyjhand.com/mcp"
}
}
}3 tools
- npi_search_providers
Search the NPPES NPI registry for individual practitioners and healthcare organizations by name, organization name, location, provider type, and specialty. Plain-language specialty terms (e.g. "cardiologist", "pediatric cardiologist") resolve through the bundled NUCC taxonomy…
- npi_get_provider
Fetch the NPPES record for one or more NPI numbers (up to 10 per call). Decodes an NPI from a claim, prescription, or another health data source into the provider's professional-practice profile: every taxonomy with its primary flag, license number and state; practice addresses…
- npi_lookup_taxonomy
Resolve and browse the NUCC Healthcare Provider Taxonomy — the specialty code set NPPES uses — fully offline (bundled). Mode `resolve` turns a plain-language specialty (e.g. "cardiologist", "heart doctor") into matching active taxonomy entries, excluding codes NUCC marks…
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 7 h ago | Passed | 200 | 492 ms |
| 17 h ago | Passed | 200 | 418 ms |
| 27 h ago | Passed | 200 | 456 ms |
| 37 h ago | Passed | 200 | 421 ms |
| 46 h ago | Passed | 200 | 440 ms |
Show 8 older checks
| 2 days ago | Passed | 200 | 417 ms |
| 3 days ago | Passed | 200 | 423 ms |
| 3 days ago | Passed | 200 | 443 ms |
| 3 days ago | Passed | 200 | 433 ms |
| 4 days ago | Passed | 200 | 517 ms |
| 4 days ago | Passed | 200 | 414 ms |
| 5 days ago | Passed | 200 | 382 ms |
| 5 days ago | Passed | 200 | 451 ms |