Skip to main content
Glama
cyanheads

clinicaltrialsgov-mcp-server

by cyanheads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to clinicaltrialsgov-mcp-server

No user-submitted related servers found.

    Related Servers

    • Clinical Trials MCP Agent

      tonih23
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to search and analyze clinical trial data from ClinicalTrials.gov using both structured SQL queries for filtering trials by status, phase, and conditions, and semantic vector search for exploring detailed protocol information like exclusion criteria.
      -

    • clinicaltrials-mcp

      agents100x
      A
      license
      A
      quality
      F
      maintenance
      Enables conversational access to 400,000+ clinical trials on ClinicalTrials.gov, allowing users to search, compare, and retrieve trial details using plain English through MCP-compatible clients like Cursor and Claude Desktop.
      5
      3
      MIT

    • BioMCP

      genomoncology
      A
      license
      A
      quality
      A
      maintenance
      Provides LLMs with structured access to critical biomedical databases including PubTator3 (PubMed/PMC), ClinicalTrials.gov, and MyVariant.info through the Model Context Protocol.
      35
      812 PyPI
      646
      MIT

    • ClinicalTrials MCP Server

      JackKuo666
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search and access clinical trial data from ClinicalTrials.gov, including searching trials by keywords, retrieving detailed trial metadata by NCT ID, and managing trial data in CSV format for research and analysis.
      16
      -
    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.3/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct role: general search, full record retrieval, results data, patient eligibility matching, field discovery, value discovery, and counting. The only mild overlap is between clinicaltrials_search_studies and clinicaltrials_find_eligible, but the latter is clearly specialized for patient-to-trial matching with site-level filtering and re-ranking.

    Naming Consistency5/5

    All tool names follow the consistent clinicaltrials_<verb>_<noun> pattern using snake_case. Verbs like search, get, find, and count are predictable and align well with each tool's purpose.

    Tool Count5/5

    Seven tools is well-scoped for a ClinicalTrials.gov client. Each tool covers a distinct functional area without unnecessary duplication or bloat.

    Completeness5/5

    The surface covers the full read-only lifecycle: discover fields and values, search studies, fetch full records, retrieve results, count studies, and match patients to trials. There are no obvious missing operations for the domain.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources