Skip to main content
Glama
openpharma-org

Medicaid MCP Server

Related Servers

Alternatives to Medicaid MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying US drug price benchmarks, including retail pharmacy NADAC acquisition costs and Medicare Part B ASP payment limits, with cross-reference by NDC and HCPCS codes, plus 340B covered entity and contract pharmacy lookups.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables querying Medicaid drug utilization, managed-care enrollment, and state enrollment data from CMS's public Medicaid Open Data API, with tools for trends, market analysis, and program mix without authentication.
      2 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching the CMS Open Payments dataset for physician, company, product, and research payments using structured filters, with annual dataset discovery through the official DKAN API.
      7 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides unified access to drug formulary data from US ACA marketplace health insurance plans, enabling drug search, coverage details, restriction info, and plan comparison across thousands of plans.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides access to U.S. HUD datasets covering fair market rents, income limits, USPS vacancy data, public housing, homelessness counts, and CHAS housing statistics.
      2 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no ambiguity or overlap between tools, as there are no other tools to compare it against. The tool's purpose is clearly defined as a unified interface for Medicaid data operations.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'medicaid_info' follows a clear and consistent pattern, though no pattern can be established across multiple tools.

    Tool Count2/5

    A single tool for a server named 'Medicaid MCP Server' suggests a very thin surface. While it unifies multiple data operations, the scope of Medicaid data (enrollment, drug pricing, quality measures) likely warrants more granular tools for better agent usability and flexibility.

    Completeness2/5

    The tool covers multiple aspects (enrollment, pricing, quality) in a unified way, but this approach may lead to gaps in specific operations like filtering, updating, or detailed queries. For a Medicaid data domain, a single tool is likely insufficient for comprehensive coverage, as agents might need more targeted actions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues