Skip to main content
Glama
colbyw5

OpenFDA MCP Server

by colbyw5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to OpenFDA MCP Server

No user-submitted related servers found.

    Related Servers

    • OpenFDA MCP Server

      Augmented-Nature
      F
      license
      B
      quality
      D
      maintenance
      A comprehensive MCP server that provides access to U.S. FDA public datasets via the openFDA API, enabling querying of drug adverse events, labeling, recalls, approvals, shortages, NDC directory, and medical device regulatory data.
      10
      24
      -

    • medical-mcp

      samson-art
      A
      license
      Not graded
      quality
      C
      maintenance
      This MCP server provides authoritative medical data from FDA, WHO, PubMed, RxNorm, and Google Scholar, enabling drug information lookup, health statistics retrieval, medical literature searching, and clinical guidelines access directly in AI workflows.
      82 npm
      MIT

    • Medical MCP Server

      geo07mz
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides comprehensive medical information by querying authoritative APIs including FDA, WHO, PubMed, RxNorm, and Australia's PBS, enabling drug searches, health statistics, medical literature, drug nomenclature, and PBS subsidy queries.
      82 npm
      MIT

    • Healthcare MCP Server

      Cicatriiz
      A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server providing AI assistants with access to healthcare data tools, including FDA drug information, PubMed research, health topics, clinical trials, and medical terminology lookup.
      7
      24 npm
      127
      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/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct FDA dataset (e.g., NDC, adverse events, labels, recalls, approvals, shortages, 510(k), classifications) with no overlap in purpose. Descriptions clearly differentiate the endpoints.

    Naming Consistency5/5

    All tools follow a consistent 'search_{domain}_{dataset}' pattern (e.g., search_drug_ndc, search_device_recalls), making it predictable and easy to navigate.

    Tool Count5/5

    With 10 tools, the server covers the major FDA drug and device datasets without being too sparse or overwhelming. It is well-scoped for the intended domain.

    Completeness5/5

    The tool set covers key FDA drug endpoints (NDC, adverse events, labels, recalls, approvals, shortages) and device endpoints (510(k), classifications, adverse events, recalls). Few major gaps exist for the core OpenFDA query use cases.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources