Skip to main content
Glama
Aki894

mcp-ClinicalTrial

by Aki894
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to mcp-ClinicalTrial

No user-submitted related servers found.

    Related Servers

    • aria-mcp-server

      pkotecha-eng
      A
      license
      A
      quality
      C
      maintenance
      Clinical research MCP server providing real-time access to PubMed (35M+ papers) and ClinicalTrials.gov (400K+ trials). Built for trial coordinators and life sciences teams. No API key required.
      3
      3
      MIT

    • 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
      -

    • OpenFDA MCP Server

      colbyw5
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that enables AI assistants to query U.S. FDA public datasets, including drug adverse events, labeling, recalls, approvals, shortages, NDC directory, and medical device regulatory information.
      10
      MIT

    • DrugWise

      VidyasreeJayaprasad
      F
      license
      B
      quality
      B
      maintenance
      An MCP server that provides AI-assisted clinical decision support for medication safety, integrating trusted biomedical sources to detect drug interactions and suggest therapeutic alternatives.
      5
      1
      -
    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

    B3.3/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some potential overlap between 'analyze_safety_profile' and 'compare_adverse_events' as both involve adverse events analysis. The descriptions help differentiate them, with one focusing on overall safety profiling and the other on group comparisons, but an agent might initially confuse their scopes.

    Naming Consistency3/5

    The naming conventions are mixed, with tools using verb_noun patterns like 'search_clinical_trials' and 'get_study_details', but others like 'ae_pipeline_rag' and 'analyze_safety_profile' deviate with acronyms or noun-heavy structures. This inconsistency reduces predictability, though the names remain generally readable.

    Tool Count5/5

    With 5 tools, the count is well-scoped for a clinical trial server, covering search, retrieval, and analysis functions. Each tool appears to earn its place without redundancy, providing a focused set for typical agent workflows in this domain.

    Completeness4/5

    The tool set covers core operations like search, retrieval, and analysis of clinical trial data, with good lifecycle coverage from finding trials to detailed analysis. A minor gap exists in update or management functions, but this is reasonable for a read/analysis-focused server, and agents can work around it effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources