Healthcare Provider NPI Enricher MCP Server
Related Servers
Alternatives to Healthcare Provider NPI Enricher MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSearch and validate US healthcare providers in the public CMS NPI Registry: lookup by NPI, search by name, specialty and location, taxonomy codes and NPI checksum validation.MIT
- AlicenseNot gradedqualityBmaintenanceLook up US healthcare providers in the NPPES NPI registry and resolve NUCC specialty codes via MCP.303 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables LLM clients to search and retrieve U.S. healthcare provider records from the NPPES NPI Registry, including provider lookup, specialty search, checksum validation, and referral-eligibility assessment, all without an API key.MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying healthcare provider information from the CMS NPI Registry using a 10-digit National Provider Identifier (NPI).82 npmMIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables interaction with the CMS NPPES NPI Registry to search, lookup, and validate National Provider Identifier records. It features offline-capable search using a local SQLite database that automatically updates with the latest provider data.-
- FlicenseNot gradedqualityDmaintenanceProvides tools to look up healthcare providers and organizations by NPI number and to search the CMS NPPES NPI Registry by name, location, taxonomy, and other criteria.-
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between competing tools. Its purpose (NPI provider lookup/enrichment) is stated clearly and unambiguously.
The single name enrich_healthcare_providers_npi follows a clear snake_case verb_noun convention that is descriptive and readable. With only one tool there is no pattern to verify consistency against, which keeps it just short of a perfect score.
A single tool is thin, but the server's scope is deliberately narrow (one enrichment lookup against the NPI Registry), so it is defensible. Still, agents needing batch processing or different lookup modes have no alternative entry point.
The tool accepts the main lookup keys (NPI, individual name, organization name, taxonomy + state) and returns a rich provider record, covering the core enrichment workflow. Minor gaps exist around explicit bulk/batch handling, pagination limits, and output shaping options.