Skip to main content
Glama
eliotk

NPI Registry MCP Server

by eliotk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to NPI Registry MCP Server

No user-submitted related servers found.

    Related Servers

    • NPI Registry MCP Server

      fastmcp-me
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for searching the National Provider Identifier (NPI) registry. It provides tools to search and retrieve information about healthcare providers and organizations in the United States.
      MIT

    • npi-verify

      gm4prezi
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for looking up and searching US healthcare providers in the CMS NPPES NPI Registry.
      MIT

    • NPPES MCP Server

      rradhakr-git
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for searching healthcare providers in the US National Provider Identifier (NPI) Registry, enabling natural language queries for provider data in MCP-compatible AI assistants.
      Apache 2.0

    • mcp-registry

      daedalus
      A
      license
      A
      quality
      C
      maintenance
      An MCP server designed for interacting with the Model Context Protocol Registry API to discover and retrieve information about available MCP servers. It provides tools to search, list, and view detailed configurations and version history for servers within the registry.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 1 tool

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources