Skip to main content
Glama
anthesiallc

MedData MCP Server

by anthesiallc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MedData MCP Server

No user-submitted related servers found.

    Related Servers

    • Pharma-MCP-Server

      rootsbymenda
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables drug safety, interactions, adverse events, and regulatory data queries using free sources like DrugBank, WHO, FDA FAERS, and more. Provides tools for checking drugs, interactions, adverse events, and searching across pharmaceutical databases.
      MIT

    • DailyMed MCP Server

      RowanErasmus
      A
      license
      B
      quality
      D
      maintenance
      Provides access to the official FDA DailyMed database for comprehensive drug information, including drug labels, NDC codes, RxNorm mappings, pharmacologic classifications, and FDA application numbers through natural language queries.
      28
      3
      MIT

    • rxnorm

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to query standardized drug concepts from the National Library of Medicine's RxNorm, including name-based search, drug property retrieval, and related concept exploration via the RxNav REST API.
      6 npm
      MIT

    • openfda-mcp-server

      ek-nath
      A
      license
      A
      quality
      D
      maintenance
      Enables LLMs to search FDA drug labels and adverse event data via the OpenFDA API, supporting natural language queries for drug safety information.
      2
      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.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: check_interactions for interactions, get_drug and get_drug_by_ndc for drug profiles by different identifiers, get_supplement for supplement profiles, search tools for lookup, and get_usage for billing. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., search_drugs, get_drug_by_ndc, check_interactions). The naming style is uniform and predictable.

    Tool Count5/5

    With 7 tools, the server is well-scoped for its purpose of drug and supplement information retrieval and interaction checking. Each tool earns its place without overcomplicating the surface.

    Completeness4/5

    The tool set covers search and retrieval for both drugs and supplements, plus interaction checking. A minor gap is the lack of a direct way to check interactions involving a single drug or supplement against a broader set, but the core workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources