Medical Mcps

Created By
pascalwhoop7 months ago
Overview

What is Medical Mcps?

Medical Mcps is a server that integrates multiple biological and medical databases, providing a unified API for research purposes.

How to use Medical Mcps?

To use Medical Mcps, connect to the production server using the unified endpoint, or configure it in an MCP client like Cursor. You can access over 100 tools across various biological and medical APIs.

Key features of Medical Mcps?

  • Unified access to 100+ tools from 14 biological and medical APIs.
  • Support for various data types including pathways, genes, proteins, diseases, drugs, and literature.
  • Local development options using Docker or Python.

Use cases of Medical Mcps?

  1. Conducting research on genetic variants and their associations with diseases.
  2. Accessing drug information and clinical trial data for biomedical research.
  3. Integrating multiple biological databases for comprehensive data analysis.

FAQ from Medical Mcps?

  • What APIs are integrated into Medical Mcps?

Medical Mcps integrates APIs like Reactome, KEGG, UniProt, OMIM, and many more.

  • Is there a local development option?

Yes, you can run a local instance using Docker or Python.

  • How do I access the production server?

You can access the production server via the unified endpoint: https://medical-mcps-production.up.railway.app/tools/unified/mcp.

Server Config

{
  "mcpServers": {
    "medical-mcps-api": {
      "type": "http",
      "url": "https://medical-mcps-production.up.railway.app/tools/unified/mcp"
    }
  }
}
Project Info
Created At
7 months ago
Updated At
6 months ago
Author Name
pascalwhoop
Star
-
Language
-
License
-

Recommend Servers

View All
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.

8 hours ago