About Precision Medicine MCP
Precision Medicine MCP is an MCP server published by lynnlangit in the Developer Tools category: precision Medicine MCP Platform: A set of bioinformatics servers + tools - production multiomics/genomics + spatial transcriptomics. Examples for ovarian cancer, breast cancer and preventative cardiovascular conditions.
The repository has 24 stars and 13 forks, with the last commit a month ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
git clone https://github.com/lynnlangit/precision-medicine-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Precision Medicine MCP
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 2 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- ✓Tests presentA test suite exists in the repository.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
1 check has not been run yet.
Releases
README
Precision Medicine MCP Platform

Dedicated to PatientOne -- a dear friend who passed from High-Grade Serous Ovarian Carcinoma in 2025.
This platform automates multi-modal data processing for clinical decision support — all results require clinician review before any clinical action.
The Problem
A patient can spend months moving between referrals, imaging, repeat evaluations, and denials without reaching a decision. Much of that motion starts at the workup — the test that would have settled the question was never ordered, or the finding that would have opened a door was never generated.
Standard oncology panels (BRCA1/2, HRD, tumor genomic) surface no immunotherapy or investigational hypotheses. Standard lipid panels and population genetic screens miss the tests most likely to change preventive management. Integrating genomics, spatial transcriptomics, imaging, and clinical data by hand is clinically impractical — the platform automates it.
What This Changes for the Patient
This platform does not triage patients or route referrals. It makes the analysis behind a decision complete on the first pass, instead of spread across a sequence of visits.
| Where the loop starts | What the platform does | Evidence |
|---|---|---|
| The decisive test was never ordered | Reports what was not tested, and why it would change management | PAT003 — Lp(a), APOE, CAC flagged after a "normal" panel (detail) |
| A threshold closed the door | Re-checks eligibility against current labeling, not just the panel's cutoff | PAT002 — HRD 35 fell below the myChoice 42 cutoff; OlympiA labeling reopens it (detail) |
| No hypothesis was ever generated | Synthesizes genomic, spatial, immune, and perturbation data into investigational paths | PAT001 + PAT002 — 6 hypotheses standard workup did not reach (detail) |
| The decision can't survive review | Every result carries XAI metadata behind a clinician APPROVE/REVISE/REJECT gate, with an audit trail | Proof layers → |
| Every modality is another handoff | One orchestrated session replaces a multi-day relay across specialists | An estimated 40 hours → an estimated 2–5 hours (modeled) |
Fewer tests is also a result. A CAC score of 0 would support deferring statin therapy for PAT003. The same analysis that adds a test can remove one — the goal is the decision, not the volume of workup.
Scope of the claim. These are three synthetic patients analyzed end-to-end, not clinical outcomes. Time and cost figures are modeled and pending clinical validation. The platform's contribution is to the quality and completeness of the decision, not to the referral pathway around it.
The Results
The platform surfaces clinically actionable findings that standard workup cannot reach — 6 investigational hypotheses across 2 cancer types plus 3 preventive health evidence gaps, validated across three independent use cases:
| Use Case | Patient | Key Finding Missed by Standard Workup |
|---|---|---|
| HGSOC (Stage IV) | PAT001 | 3 investigational paths: neoantigen vaccine (RMPEAAPPV IC50 7.8 nM), NNMT/CAF inhibition, convergent checkpoint blockade |
| ER+ Breast Cancer | PAT002 | 3 investigational hypotheses: inavolisib over alpelisib (PIK3CA H1047R, 2024 FDA approval), MYC-driven triple therapy, YSAPLSSSL neoepitope vaccine + CAF depletion + anti-PD-1 — zero disease-specific code changes |
| Preventive Cardiovascular | PAT003 | Intermediate CVD risk (Reynolds 14.3%) with 3 high-priority gaps missed by standard lipid panel AND population genetic screen: Lp(a), APOE genotype, CAC score |
The same 19-server architecture runs all three, with no disease-specific code changes. All tools are accessible via natural language, every AI result requires clinician APPROVE/REVISE/REJECT, and 11 servers return per-tool XAI metadata (confidence levels, evidence grades, counterfactuals). Current counts: Server Registry.
Try It
# Clone and explore
git clone https://github.com/lynnlangit/precision-medicine-mcp.git
cd precision-medicine-mcp
# Run tests for any server (DRY_RUN mode, no external deps needed)
cd servers/mcp-multiomics && uv run pytest -v
# Or use Claude Code to explore interactively
claude
Most servers default to DRY_RUN mode (mock responses, no API keys needed) for quick validation. Set *_DRY_RUN=false to use synthetic patient data for end-to-end testing. mcp-deidentify is the exception — it runs live by default, because a de-identification tool that silently returns fabricated data is a safety failure rather than a safe default.
Learn More
| Audience | Start Here |
|---|---|
| Getting Started | Installation Guide |
| Funders | Executive Summary |
| Hospitals | Hospital Guide |
| Developers | Architecture |
| Researchers | Researcher Guide |
| Educators | Educator Guide |
| All docs | Documentation Index |
Video: 5-minute demo | Paper: Why MCP for Healthcare | External connectors: Setup guide
+--------------------------------------+
| CLIENT LAYER |
| Claude Desktop / Hospital EHR |
| Adapter / Research Notebook |
+----------------+-----------------+
|
MCP (FastMCP >= 2.13)
|
+---------------------------------------------------------------+
| |
| PRE-PROCESSING (Stage 0) |
| deidentify |
| |
| DATA ACQUISITION ANALYSIS & INFERENCE REPORTING |
| |
| mockepic spatialtools patient- |
| epic multiomics report |
| geodownload perturbation |
| mocktcga quantum-fidelity |
| genomic-results opentargets |
| fgbio neoantigen |
| cibersortx |
| openimagedata |
| deepcell |
| cell-classify |
| cardiometabolic |
+---------------------------------------------------------------+
Full detail: Architecture · Server Registry
| Metric | Value | Source server |
|---|---|---|
| HRD score | 54 | mcp-genomic-results |
| TMB (POLE-corrected) | 47.3 mut/Mb | mcp-genomic-results |
| Top neoantigen IC50 (RMPEAAPPV) | 7.8 nM | mcp-neoantigen |
| Spatial spot count | 900 | mcp-spatialtools |
| Moran's I (global) | -0.0033 | mcp-spatialtools |
| Deconvolution: tumor | 56 cells | mcp-cibersortx |
| Deconvolution: endothelial | 44 cells | mcp-cibersortx |
| Deconvolution: macrophages | 43 cells | mcp-cibersortx |
| Deconvolution: fibroblasts | 41 cells | mcp-cibersortx |
| Deconvolution: CD8+ T cells | 30 cells | mcp-cibersortx |
Canonical values for all three patients: Patient Outcomes (source of truth: tests/fixtures/pat00X_canonical.py)
Apache 2.0 | Python 3.11+ | FastMCP >= 2.13 | uv for package management
README fetched from the repository 2 days ago. The original is authoritative.