Healthcare Provider NPI Enricher MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| enrich_healthcare_providers_npiA | Give NPIs, individual names, organization names, or a taxonomy with a state. Returns one row per provider from the official US NPI Registry with taxonomy, license, practice address and phone, and organization official. Invalid and unmatched lookups are free. Pay per event on Apify: 0.002 USD per provider row. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.