Skip to main content
Glama
Sign In
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
      24 PyPI
      3
      MIT

    • clinicaltrialsgov-mcp-server

      Gracev54693
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to search the ClinicalTrials.gov registry, retrieve full study records and posted results, explore API field names and values, and match patient demographics and conditions to eligible recruiting trials. Runs over STDIO or Streamable HTTP with rate-limit handling, geographic proximity search, and read-only public access requiring no authentication.
      1,881 npm
      Apache 2.0

    • 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
      761 PyPI
      668
      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.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool targets a fairly distinct operation: count, search, single record, results, field values, field definitions, and patient-eligibility matching. The only real overlap is clinicaltrials_get_field_values vs clinicaltrials_get_field_definitions (and to a lesser degree search_studies vs get_study_record), but the descriptions draw clear lines between them.

    Naming Consistency5/5

    All tools share the clinicaltrials_ prefix and a predictable verb_noun snake_case pattern (get_study_count, search_studies, get_study_record, get_field_values, get_study_results, find_eligible). The one verb deviation (find_eligible vs get_*) is semantically meaningful and still readable.

    Tool Count5/5

    Seven tools is a well-scoped surface for a ClinicalTrials.gov wrapper, covering discovery, retrieval, results, and eligibility without redundancy. Each tool earns its place in a typical workflow.

    Completeness4/5

    The set covers counting, searching, field discovery, full records, results data, and patient matching, which is strong lifecycle coverage for the domain. Minor gaps remain, e.g. no batch record fetch for multiple NCT IDs (only results supports up to 20) and no dedicated sponsor/intervention entity lookup.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources