Mutation Clinical Trial Matching MCP

Created By
pickleton89a year ago
MCP server to query clinicaltrial.gov to identify mutation specific trials
Overview

What is Mutation Clinical Trial Matching MCP?

Mutation Clinical Trial Matching MCP is a Model Context Protocol (MCP) server designed to query clinicaltrials.gov for identifying clinical trials specific to genetic mutations.

How to use Mutation Clinical Trial Matching MCP?

To use the MCP, install the required dependencies, configure Claude Desktop, and ask questions about specific genetic mutations to retrieve relevant clinical trials.

Key features of Mutation Clinical Trial Matching MCP?

  • Integration with Claude Desktop for natural language queries.
  • Summarization of clinical trial data based on genetic mutations.
  • Robust error handling and logging for API interactions.

Use cases of Mutation Clinical Trial Matching MCP?

  1. Finding clinical trials for specific genetic mutations like EGFR L858R.
  2. Retrieving detailed information about trials based on mutation types.
  3. Assisting researchers and patients in understanding available treatment options.

FAQ from Mutation Clinical Trial Matching MCP?

  • Can I use this tool for any genetic mutation?

Yes, the tool is designed to query trials based on various genetic mutations.

  • Is there a cost to use the MCP server?

No, the MCP server is free to use as part of the open-source project.

  • What should I do if I encounter issues?

Check the logs for errors and ensure that the server is running correctly.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pickleton89
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Hellogrowthcrm

2 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago
Payai X402 Tools

11 hours ago