Skip to main content
mcpSource-backed
BioMCP logo

BioMCP

Biomedical MCP server and CLI for searching genes, variants, articles, clinical trials, drugs, diseases, pathways, proteins, adverse events, pharmacogenomics, GWAS, phenotypes, and local study datasets.

by GenomOncology · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/genomoncology/biomcp/blob/main/README.md, https://github.com/genomoncology/biomcp, https://biomcp.org
Brand
BioMCP
Brand domain
biomcp.org
Brand asset source
brandfetch
Safety notes
BioMCP is an evidence retrieval and analysis tool, not medical advice, diagnosis, treatment guidance, or a substitute for professional review., Biomedical sources can be incomplete, stale, conflicting, preliminary, or restricted by licensing and terms of use., Trial status, eligibility criteria, drug labels, safety reports, variant interpretations, and disease associations can change after retrieval., The MCP server can return dense biomedical evidence that should be checked against primary sources before downstream decisions., Local study analytics can process downloaded study datasets and generate charts, so use only approved, de-identified, and policy-compliant data.
Privacy notes
Biomedical queries can reveal research interests, genes, variants, diseases, drugs, phenotypes, trial searches, or cohort metadata to upstream APIs., Optional API keys and tokens may be sent to third-party data providers such as NCBI, Semantic Scholar, OpenFDA, NCI, OncoKB, AlphaGenome, or DisGeNET., Local study files, generated charts, caches, prompts, and model transcripts can contain sensitive cohort or patient-derived context., Avoid patient-identifiable data unless the environment, approvals, and data-use agreements explicitly allow it., The project documentation says BioMCP does not add telemetry, analytics, or remote log upload, but upstream biomedical APIs can still receive request metadata.
Author
GenomOncology
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

15 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

4 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/4 ready
Account & credentials1Network & hosting2Review & approval115 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 5 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access.

4 areas
  • SafetyGeneralBioMCP is an evidence retrieval and analysis tool, not medical advice, diagnosis, treatment guidance, or a substitute for professional review.
  • SafetyGeneralBiomedical sources can be incomplete, stale, conflicting, preliminary, or restricted by licensing and terms of use.
  • SafetyGeneralTrial status, eligibility criteria, drug labels, safety reports, variant interpretations, and disease associations can change after retrieval.
  • SafetyGeneralThe MCP server can return dense biomedical evidence that should be checked against primary sources before downstream decisions.
  • SafetyNetwork accessLocal study analytics can process downloaded study datasets and generate charts, so use only approved, de-identified, and policy-compliant data.
  • PrivacyGeneralBiomedical queries can reveal research interests, genes, variants, diseases, drugs, phenotypes, trial searches, or cohort metadata to upstream APIs.
  • PrivacyCredentials & tokensOptional API keys and tokens may be sent to third-party data providers such as NCBI, Semantic Scholar, OpenFDA, NCI, OncoKB, AlphaGenome, or DisGeNET.
  • PrivacyLocal filesLocal study files, generated charts, caches, prompts, and model transcripts can contain sensitive cohort or patient-derived context.
  • PrivacyGeneralAvoid patient-identifiable data unless the environment, approvals, and data-use agreements explicitly allow it.
  • PrivacyNetwork accessThe project documentation says BioMCP does not add telemetry, analytics, or remote log upload, but upstream biomedical APIs can still receive request metadata.

Safety notes

  • BioMCP is an evidence retrieval and analysis tool, not medical advice, diagnosis, treatment guidance, or a substitute for professional review.
  • Biomedical sources can be incomplete, stale, conflicting, preliminary, or restricted by licensing and terms of use.
  • Trial status, eligibility criteria, drug labels, safety reports, variant interpretations, and disease associations can change after retrieval.
  • The MCP server can return dense biomedical evidence that should be checked against primary sources before downstream decisions.
  • Local study analytics can process downloaded study datasets and generate charts, so use only approved, de-identified, and policy-compliant data.

Privacy notes

  • Biomedical queries can reveal research interests, genes, variants, diseases, drugs, phenotypes, trial searches, or cohort metadata to upstream APIs.
  • Optional API keys and tokens may be sent to third-party data providers such as NCBI, Semantic Scholar, OpenFDA, NCI, OncoKB, AlphaGenome, or DisGeNET.
  • Local study files, generated charts, caches, prompts, and model transcripts can contain sensitive cohort or patient-derived context.
  • Avoid patient-identifiable data unless the environment, approvals, and data-use agreements explicitly allow it.
  • The project documentation says BioMCP does not add telemetry, analytics, or remote log upload, but upstream biomedical APIs can still receive request metadata.

Prerequisites

  • Python 3.10 or newer and uv, pip, or another supported Python tool installer.
  • Network access to the biomedical APIs needed for the selected searches.
  • Optional API keys for NCBI, Semantic Scholar, OpenFDA, NCI, OncoKB, AlphaGenome, or DisGeNET when those integrations are required.
  • Review by a qualified domain expert before using biomedical findings in clinical, diagnostic, treatment, or regulatory decisions.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
15 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "biomcp": {
      "command": "biomcp",
      "args": ["serve"]
    }
  }
}

About this resource

Content

BioMCP is a biomedical Model Context Protocol server and command-line tool for evidence retrieval, entity lookup, and local study analysis. It lets Claude use the biomcp command grammar through MCP to search articles, genes, variants, clinical trials, diagnostics, drugs, diseases, pathways, proteins, adverse events, pharmacogenomics, GWAS records, phenotypes, and approved local study datasets.

The project focuses on read-only biomedical discovery. It aggregates public and optional authenticated data sources such as PubMed, PubTator3, Europe PMC, ClinicalTrials.gov, NCI CTS, MyGene.info, MyVariant.info, ClinVar, MyChem.info, OpenFDA, Reactome, UniProt, CIViC, OncoKB, g:Profiler, and Semantic Scholar.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, PyPI metadata, Python package metadata, Rust package metadata, MCP manifest, and license file for current install commands, supported entities, tool behavior, optional credentials, and licensing.

Features

  • Python package biomcp-cli with a Rust-backed biomcp binary.
  • Stdio MCP server launched with biomcp serve.
  • Read-only biomedical command grammar exposed through a biomcp MCP tool.
  • Literature search across PubTator3 and Europe PMC, with article detail, citation, reference, recommendation, and entity workflows.
  • Gene, variant, disease, drug, diagnostic, pathway, protein, adverse-event, pharmacogenomics, GWAS, and phenotype lookup workflows.
  • Clinical trial search through ClinicalTrials.gov API v2 and NCI CTS sources.
  • Local study analytics for approved downloaded datasets, including cohort, survival, comparison, co-occurrence, and chart workflows.
  • Optional API keys for higher-rate or gated integrations.
  • MIT license.

Installation

Install the package, then configure the MCP server:

uv tool install biomcp-cli
{
  "mcpServers": {
    "biomcp": {
      "command": "biomcp",
      "args": ["serve"]
    }
  }
}

After restarting the MCP client, ask Claude to search or summarize an approved biomedical question and cite the returned source records.

Use Cases

  • Search biomedical literature for a gene, variant, disease, drug, or phenotype.
  • Compare article evidence with clinical trial records for a research question.
  • Retrieve structured detail pages for genes, variants, drugs, diseases, or trials.
  • Explore known gene, variant, disease, pathway, and drug relationships.
  • Summarize public clinical trial status and eligibility criteria for review.
  • Run approved local study analytics on de-identified datasets.
  • Generate evidence-backed biomedical research notes with source links.

Safety and Privacy

BioMCP should be treated as a research aid. Its outputs are not medical advice and should not be used directly for diagnosis, treatment, eligibility determinations, regulatory submissions, or safety decisions without qualified human review and source verification.

Biomedical searches can expose sensitive research direction, disease interests, drug names, variants, trial queries, and cohort context to third-party APIs. Local study workflows can also handle sensitive derived data and generated charts. Use only approved datasets, protect optional API keys, and avoid PHI or patient-identifiable records unless your environment and approvals explicitly permit that use.

Duplicate Check

Existing content includes paper-search and PubMed-oriented MCP entries, plus life-sciences agent content. This entry is distinct because it covers genomoncology/biomcp, a unified biomedical MCP server and CLI spanning literature, genes, variants, trials, diagnostics, drugs, diseases, pathways, proteins, adverse events, pharmacogenomics, GWAS, phenotypes, and local study analytics. No matching BioMCP source URL or dedicated BioMCP entry was found in content/mcp.

Source citations

Add this badge to your README

Show that BioMCP is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/biomcp.svg)](https://heyclau.de/entry/mcp/biomcp)

How it compares

BioMCP side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Biomedical MCP server and CLI for searching genes, variants, articles, clinical trials, drugs, diseases, pathways, proteins, adverse events, pharmacogenomics, GWAS, phenotypes, and local study datasets.

Open dossier

Python MCP server and CLI for searching, deduplicating, downloading, and reading academic papers across open and public sources such as arXiv, PubMed, bioRxiv, Semantic Scholar, OpenAlex, CORE, Europe PMC, Zenodo, HAL, and more.

Open dossier

AgentQL MCP server for extracting structured JSON from public webpages using a URL and natural-language extraction prompt.

Open dossier

MCP server for searching, downloading, reading, and analyzing arXiv papers through Claude and other MCP clients.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandBioMCP logoBioMCPAgentQL logoAgentQL
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorGenomOncologyopenagsAgentQLJoseph Blazick
Added2026-06-062026-06-052026-06-062026-06-05
Platforms
Harness
Source repo
Safety notesBioMCP is an evidence retrieval and analysis tool, not medical advice, diagnosis, treatment guidance, or a substitute for professional review. Biomedical sources can be incomplete, stale, conflicting, preliminary, or restricted by licensing and terms of use. Trial status, eligibility criteria, drug labels, safety reports, variant interpretations, and disease associations can change after retrieval. The MCP server can return dense biomedical evidence that should be checked against primary sources before downstream decisions. Local study analytics can process downloaded study datasets and generate charts, so use only approved, de-identified, and policy-compliant data.Prefer open-access and publisher-permitted sources. The README describes Sci-Hub as optional, unstable, jurisdiction-dependent, and user-responsibility-only. Download and read tools can retrieve PDFs and extract text; confirm copyright, license, institutional, and project-policy requirements before downloading or sharing papers. Optional source credentials, proxy URLs, and API keys can change access levels and rate limits; store them as secrets rather than in prompts or committed configs. Google Scholar, SSRN, CORE, OpenAIRE, BASE, and other sources may rate-limit, block, or return incomplete results depending on network conditions and provider policies. Paid or restricted connectors should stay disabled unless the user has valid credentials and rights to use those services.AgentQL MCP exposes one tool, `extract-web-data`, that sends a target URL and natural-language extraction prompt to the AgentQL API. The tool is intended for public webpages; do not use it to bypass access controls, scrape private pages, evade paywalls, or extract data where automated collection is prohibited. Web extraction can still trigger target-site rate limits, legal restrictions, robots guidance, or terms-of-service concerns. The source implementation uses AgentQL's query-data endpoint with fast mode, no screenshot capture, no scroll-to-bottom behavior, and no local browser cookies. Treat extracted output as untrusted web data that may include errors, stale content, ads, tracking text, or prompt-injection attempts.arXiv MCP Server retrieves paper content from external, user-generated sources. Upstream explicitly warns that paper text is untrusted input and can contain prompt-injection attempts. Downloaded papers are stored locally for later reading and semantic search. Citation graph and alert workflows can expand research context beyond the original paper query. Treat model summaries of papers as data, not instructions, especially in multi-tool sessions with filesystem, shell, browser, database, or messaging tools enabled.
Privacy notesBiomedical queries can reveal research interests, genes, variants, diseases, drugs, phenotypes, trial searches, or cohort metadata to upstream APIs. Optional API keys and tokens may be sent to third-party data providers such as NCBI, Semantic Scholar, OpenFDA, NCI, OncoKB, AlphaGenome, or DisGeNET. Local study files, generated charts, caches, prompts, and model transcripts can contain sensitive cohort or patient-derived context. Avoid patient-identifiable data unless the environment, approvals, and data-use agreements explicitly allow it. The project documentation says BioMCP does not add telemetry, analytics, or remote log upload, but upstream biomedical APIs can still receive request metadata.Queries may reveal research topics, grant interests, product plans, biomedical topics, legal theories, security research, or competitive intelligence. Downloaded PDFs, extracted text, search results, DOI lists, API keys, proxy URLs, emails, and source-specific logs can contain sensitive research or credential data. MCP transcripts and model-provider logs may retain paper queries, abstracts, titles, authors, downloaded text, and notes outside library or institutional systems. Do not paste private API keys, proxy credentials, unpublished manuscripts, review assignments, patient-adjacent research details, or embargoed paper content into prompts.Target URLs, extraction prompts, API key-authenticated requests, and extracted structured data are sent to AgentQL's API. Extracted data can include personal data, copyrighted content, customer information, job postings, prices, social content, or other third-party material. AGENTQL_API_KEY should stay out of prompts, issues, logs, screenshots, and committed configuration files. Claude transcripts and downstream reports may retain extracted data, so avoid collecting information that is not approved for the model session.Search queries, paper IDs, downloaded paper text, local storage choices, semantic search terms, citation graph requests, alert topics, prompts, and tool outputs may be visible to the MCP client and model provider. Research queries and downloaded papers can reveal confidential research direction, product plans, academic review topics, legal strategy, or competitive analysis. Review locally stored papers and generated summaries before syncing, sharing, or committing them.
Prerequisites
  • Python 3.10 or newer and uv, pip, or another supported Python tool installer.
  • Network access to the biomedical APIs needed for the selected searches.
  • Optional API keys for NCBI, Semantic Scholar, OpenFDA, NCI, OncoKB, AlphaGenome, or DisGeNET when those integrations are required.
  • Review by a qualified domain expert before using biomedical findings in clinical, diagnostic, treatment, or regulatory decisions.
  • Python 3.10 or newer, with uv recommended for the documented no-install and persistent-install paths.
  • Network access to public academic sources and repositories.
  • Optional API keys or emails configured only for sources the user is authorized to access.
  • A policy decision on whether download, read, optional Sci-Hub fallback, paid-platform skeleton connectors, and proxy-based Google Scholar discovery are allowed.
  • Node.js and npx available to the MCP client runtime.
  • AgentQL API key from the AgentQL developer portal.
  • Approved list of public webpages or domains Claude may query.
  • Review of target site terms, robots guidance, rate limits, and data-use rules before extraction.
  • Python 3.11 or newer available to the MCP client runtime.
  • uvx available for package execution.
  • Local storage available for downloaded papers.
  • Optional PDF extra if you need older papers that do not have HTML content.
Install
uv tool install biomcp-cli
uvx paper-search-mcp
npx -y agentql-mcp
uvx arxiv-mcp-server
Config
{
  "mcpServers": {
    "biomcp": {
      "command": "biomcp",
      "args": ["serve"],
      "env": {
        "NCBI_API_KEY": "",
        "S2_API_KEY": "",
        "OPENFDA_API_KEY": "",
        "NCI_API_KEY": "",
        "ONCOKB_TOKEN": "",
        "ALPHAGENOME_API_KEY": ""
      }
    }
  }
}
Manual-only setup:
uv tool install paper-search-mcp
uv tool run paper-search-mcp
{
  "mcpServers": {
    "agentql": {
      "command": "npx",
      "args": ["-y", "agentql-mcp"],
      "env": {
        "AGENTQL_API_KEY": "<your-agentql-api-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "arxiv": {
      "command": "uvx",
      "args": ["arxiv-mcp-server"]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.