Skip to main content
Glama
Sairajiv-13

Clinical Trials MCP Server

by Sairajiv-13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Clinical Trials MCP Server

No user-submitted related servers found.

    Related Servers

    • Clinical Trials MCP Server

      BACH-AI-Tools
      A
      license
      B
      quality
      D
      maintenance
      Provides programmatic access to ClinicalTrials.gov API with 18 specialized tools for searching, analyzing, and retrieving detailed information about 400,000+ clinical trials worldwide, including filtering by condition, location, phase, sponsor, eligibility criteria, and outcomes.
      17
      10 npm
      4
      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,067 npm
      Apache 2.0

    • ClinicalTrials-MCP

      celia-zheng
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables searching clinical trials, retrieving trial details, matching patient profiles to recruiting trials, and extracting eligibility criteria from ClinicalTrials.gov.
      -
    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

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: discovery (search_trials), single-record retrieval (get_trial), structured eligibility verdict (eligibility_check), and site listings (recruiting_sites). The search-vs-get boundary is explicit (filters vs NCT number), so an agent can select unambiguously.

    Naming Consistency4/5

    search_trials and get_trial follow a clean verb_noun pattern, but eligibility_check and recruiting_sites are noun-heavy phrases rather than verb-led. All are snake_case and readable, with only a minor stylistic deviation.

    Tool Count4/5

    Four tools is a focused, cohesive set for a read-only clinical trials lookup server, with no redundant or filler tools. It is slightly thin—no location- or intervention-based filtering beyond the search tool's filters—but each tool earns its place.

    Completeness4/5

    The surface covers the natural read-only lifecycle: find studies, inspect a study, check structured eligibility, and locate recruiting sites. Since the registry is public and read-only, the absence of write operations is correct; only minor gaps (e.g. no multi-trial comparison) remain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources