Skip to main content
Glama
eliotk

NPI Registry MCP Server

by eliotk
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Server Quality Checklist

75%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    With only one tool, there is no ambiguity or overlap between tools. The single tool has a clear, distinct purpose of searching the NPI registry, so an agent cannot misselect between multiple tools.

    Naming Consistency5/5

    With only one tool, naming consistency is inherently perfect. The tool name 'search_npi_registry' follows a clear verb_noun pattern that would be consistent if more tools existed.

    Tool Count2/5

    A single tool for an NPI registry server feels too thin for the apparent scope. The registry likely supports more operations beyond search, such as retrieving specific records by ID or filtering by additional criteria, making the tool count insufficient for comprehensive coverage.

    Completeness2/5

    The tool surface is severely incomplete for an NPI registry domain. While search is well-implemented with various criteria, there are obvious gaps such as no tools for retrieving a specific provider by NPI number (get_npi), updating records, or managing provider data, which limits agent workflows.

  • Average 4.4/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • This repository includes a glama.json configuration file.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior4/5

    Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

    With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively adds context beyond basic functionality by detailing wildcard support rules (e.g., '*' after at least 2 characters), exact vs. fuzzy matching for parameters like NPI and state, and the default limit of 10 results. It doesn't cover aspects like rate limits or authentication needs, but provides substantial operational guidance.

    Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

    Conciseness4/5

    Is the description appropriately sized, front-loaded, and free of redundancy?

    The description is well-structured with clear sections (overview, wildcard support, args, examples, returns) and front-loaded key information. It's appropriately sized but could be slightly more concise by integrating some details more tightly. Every sentence adds value, though minor trimming might improve flow.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness4/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    For a search tool with 9 parameters, 0% schema coverage, no annotations, and no output schema, the description is highly complete. It covers purpose, usage, parameter details, examples, and return format. It lacks some advanced behavioral traits like error handling or pagination, but provides enough context for effective use given the complexity.

    Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

    Parameters5/5

    Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

    Given 0% schema description coverage and 9 parameters, the description compensates fully by explaining each parameter's purpose, wildcard support, and constraints (e.g., NPI is exact match, state abbreviations, limit range 1-200). Examples illustrate usage, adding significant value beyond the bare schema. This exceeds the baseline expectation for such low coverage.

    Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

    Purpose5/5

    Does the description clearly state what the tool does and how it differs from similar tools?

    The description clearly states the tool searches the NPI registry for healthcare providers and organizations in the US, specifying the resource (NPI registry) and action (search). It distinguishes the tool's purpose by listing specific search criteria like name, NPI number, location, and specialty, making it highly specific and informative even without sibling tools for comparison.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines4/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    The description provides clear context on when to use the tool by listing searchable criteria and examples, such as finding providers by name, location, or specialty. However, it lacks explicit guidance on when not to use it or alternatives, which prevents a perfect score. No sibling tools are mentioned, so no comparison is needed.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

npi-registry-mcp-server MCP server

Copy to your README.md:

Score Badge

npi-registry-mcp-server MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eliotk/npi-registry-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server