Skip to main content
Glama
BACH-AI-Tools

OpenFDA Drug Label MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to OpenFDA Drug Label MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • drug-label

      arhancanli
      A
      license
      A
      quality
      B
      maintenance
      Answers medication questions from official FDA labels with section citations, resolves drug names via RxNorm, and reports FDA recalls and shortages.
      4
      MIT

    • mcp-fda-devices

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying FDA medical device regulatory databases including 510(k) clearances, PMA approvals, recalls, and adverse events through natural language.
      550 npm
      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

    A3.6/5.0

    Scored across 5 tools

    Disambiguation3/5

    The three specific getters (adverse reactions, warnings, indications) are clearly distinct, but search_drug_labels and ae_pipeline_rag both fetch broad drug label data, creating some overlap. The descriptions help distinguish them (general search vs. advanced safety pipeline), but the boundary is not entirely sharp.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (search_drug_labels, get_drug_adverse_reactions, get_drug_warnings, get_drug_indications). The outlier is ae_pipeline_rag, which uses an acronym and lacks a verb, making it a minor deviation from the otherwise predictable naming convention.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of querying FDA drug labels. Each tool covers a meaningful aspect (general search, specific sections, and a comprehensive pipeline) without excessive redundancy or missing core functionality.

    Completeness4/5

    The tool set covers the primary drug safety sections (adverse reactions, warnings, indications) and provides a full search capability. Minor gaps exist (e.g., no explicit contraindications or dosage getter), but agents can retrieve these via search_drug_labels or ae_pipeline_rag, so the surface is not severely incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources