Skip to main content
Glama
ek-nath

openfda-mcp-server

by ek-nath

Related Servers

Alternatives to openfda-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides LLM-optimized access to FDA data through the OpenFDA API and direct regulatory decision document retrieval, covering all 21 OpenFDA endpoints plus 510(k) summaries, De Novo decisions, and PMA approvals.
      4
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time access to medical data including drug interactions, ICD-10 codes, FDA adverse event reports, and clinical guidelines. It enables LLMs to query databases like openFDA, PubMed, and CMS for pharmaceutical and clinical information.
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target distinct OpenFDA endpoints: drug labels and adverse events. There is no overlap in their purposes, making it clear which to use.

    Naming Consistency4/5

    Both names follow a verb_noun pattern, but one uses 'search' and the other uses 'get', which is a minor inconsistency. Otherwise the pattern is clear and predictable.

    Tool Count3/5

    With only two tools, the server feels thin for the OpenFDA domain, which has many potential endpoints. However, the two tools cover two common use cases, so the count is borderline acceptable.

    Completeness2/5

    OpenFDA offers many data types (e.g., recalls, enforcement reports, labeling for drugs and devices). Only drug labels and adverse events are covered, leaving significant gaps that would force agents to look elsewhere.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues