Genefoundry

io.github.berntpoppPublished by GitHub account berntpoppv0.13.17Updated Nov 22, 2026

MCP gateway federating 30 biomedical MCP servers behind one endpoint: gnomAD, ClinVar, HPO, VEP.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Remote MCP gateway that federates 22 biomedical data servers (gnomAD, ClinVar, HPO, VEP and more) behind one endpoint with search-based tool discovery.

What you can do
  • Search the federated catalog of about 285 tools across 22 biomedical backends by intent
  • Invoke any hit by its namespaced name, such as gnomad_search_genes or spliceai_predict_splicing
  • Reach each backend's pinned front-door tool directly, without relying on search ranking
  • Query variant, gene, phenotype, protein, expression, pharmacogenomics and literature sources through one connection
When to use it
Useful when an assistant needs to look up genetics and biomedical reference data — variant frequency and clinical significance, gene-disease curation, phenotype ontologies, protein function, splicing prediction — without wiring up each source separately.
Requirements
A remote Streamable-HTTP endpoint at genefoundry.org; no local install needed. OAuth authentication is required. Running your own copy needs Python 3.14+ and uv, plus GF_* backend URL and auth-mode settings.
Before you install
Explicitly research use only, not clinical decision support, and not for diagnosis, treatment, triage or patient management. The caller's token is not forwarded upstream, but queries still go to third-party biomedical data sources. Tool definitions are fingerprinted against a reviewed baseline to detect drift.

Installation

In SourceWeft

  1. Open Genefoundry in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.berntpopp%2Fgenefoundry/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "genefoundry": {
      "type": "http",
      "url": "https://genefoundry.org/mcp"
    }
  }
}

README

genefoundry-router

[Python 3.14+] [CI] [Security] [License: MIT]

A thin FastMCP 3.x aggregator that federates the GeneFoundry *-link MCP fleet behind a single Streamable-HTTP endpoint. A host adds one server — genefoundry — and gets every biomedical backend with collision-free <namespace>_<tool> naming and search-based discovery.

[!IMPORTANT] Research use only. Not clinical decision support. Do not use for diagnosis, treatment, triage, or patient management.

Why

An MCP host that mounted all 21 backends directly would face a wall of several hundred tools — more than a model can reason over, and a guarantee of name collisions. The router collapses that into one endpoint and replaces the flat catalog with a search surface, so a model finds the right tool by intent instead of by scrolling.

It is a client to each backend and a server to hosts: it namespaces and shapes the surface, but never rewrites a backend's data. The caller's token is never forwarded upstream.

Quick start

The fleet is hosted — no install required:

bash
claude mcp add --transport http genefoundry https://genefoundry.org/mcp

Health check: genefoundry.org/health.

To run your own against the live fleet (Python 3.14+, uv):

bash
uv sync --group devcp .env.example .env                    # set GF_*_URL backend URLs and GF_AUTH_MODEuv run genefoundry-router run --host 127.0.0.1 --port 8000curl -s localhost:8000/health | python -m json.tool

An offline fake fleet (make dev-fleet + make run-dev, or one-shot make test-e2e) runs the real router against impersonated backends over real Streamable-HTTP — no Docker, no network.

Tools

The router does not surface the federated catalog flat. A model sees three things:

ToolPurpose
search_toolsRelevance search over the entire federated catalog
call_toolInvoke a hit by its <namespace>_<tool> name
pinned entry pointsEach backend's front-door tool, always visible — declared per-backend as entrypoints: in servers.yaml
text
search_tools(query="splicing prediction")   # → spliceai_predict_splicing (+ schema)call_tool(name="spliceai_predict_splicing", arguments={...})

Pinning makes each domain's canonical tool reachable deterministically rather than by relevance luck. See How discovery works — including the two traps that bite MCP clients.

Federated backends

30 backends, 345 tools, each surfaced namespaced — e.g. gnomad_search_genes.

NamespaceDomainData sourceToolsRepo
pubtatorLiterature & entity annotationPubTator335pubtator-link
gnomadVariant / gene / population frequencygnomAD22gnomad-link
hpoPhenotype ontology & associationsHuman Phenotype Ontology19hpo-link
orphanetRare disease ontology & associationsOrphadata19orphanet-link
clingenGene–disease curationClinGen17clingen-link
mavedbVariant-effect assay scoresMaveDB15mavedb-link
uniprotProtein functionUniProt15uniprot-link
clinpgxPharmacogenomics / gene-drug guidelinesClinPGx13clinpgx-link
genereviewsGene–disease literatureGeneReviews13genereviews-link
mgiMouse phenotype & modelsMGI13mgi-link
mondoDisease ontology / cross-referencesMondo13mondo-link
genccGene–disease curationGenCC12gencc-link
metadomeProtein tolerance landscapesMetaDome11metadome-link
civicSomatic variant clinical evidence & AMP/ASCO/CAP assertionsCIViC10civic-link
stringdbProtein–protein interaction networksSTRING10stringdb-link
cbioportalCancer genomics mutation prevalence & hotspotscBioPortal9cbioportal-link
gtexTissue expressionGTEx Portal9gtex-link
hgncGene nomenclatureHGNC9hgnc-link
panelappDiagnostic gene panels & curationPanelApp9panelapp-link
clinvarVariant clinical significanceClinVar8clinvar-link
pgscatalogPolygenic scores, traits, ancestry & performance metricsPGS Catalog8pgscatalog-link
ucscGenome Browser region tracks, reference sequence, BLAT & in-silico PCRUCSC Genome Browser8ucsc-link
autopvs1Variant ACMG PVS1AutoPVS17autopvs1-link
opentargetsTarget tractability, drug candidates & target-disease evidenceOpen Targets Platform7opentargets-link
spliceaiSplicing predictionSpliceAI Lookup7spliceailookup-link
vepVariant annotation / consequenceEnsembl VEP7vep-link
litvarVariant literatureLitVar26litvar-link
moalmanacRegulatory approvals for cancer biomarker-therapy pairsMolecular Oncology Almanac5moalmanac-link
strchiveTandem-repeat (STR) disease loci & repeat rangesSTRchive5strchive-link
mitomapMitochondrial DNA (mtDNA) variants & disease associationsMITOMAP4mitomap-link

Data & provenance

The router serves no data of its own; each backend owns its sources, licences and citation guidance, and the router mirrors their disclaimers.

What it does own is integrity of the tool surface. A backend can serve a clean tool at review time and later change its definition — the channel for a rug pull. The router fingerprints every normalized tool definition and diffs the live fleet against a reviewed, packaged baseline (genefoundry_router/data/fleet-baseline.json), enforced at startup and on a schedule. See Deployment → drift detection.

Documentation

Contributing

See AGENTS.md for engineering conventions. make ci-local is the definition-of-done gate: format, lint, line budget, README standard, mypy, and tests.

License

MIT © Bernt Popp. Each federated backend carries the licence and citation terms of its upstream data source; see that backend's repository.

Source: README.md at commit e59d0e8

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

23
  1. v0.13.17LatestNov 22, 2026
  2. v0.13.15Nov 21, 2026
  3. v0.13.14Nov 21, 2026
  4. v0.13.13Nov 20, 2026
  5. v0.13.12Nov 20, 2026
  6. v0.13.11Nov 19, 2026
  7. v0.13.7Nov 19, 2026
  8. v0.13.2Nov 19, 2026
  9. v0.12.3Nov 19, 2026
  10. v0.10.17Nov 13, 2026
  11. v0.10.13Nov 12, 2026
  12. v0.10.12Nov 11, 2026
  13. v0.10.10Oct 29, 2026
  14. v0.10.8Oct 21, 2026
  15. v0.10.7Oct 20, 2026
  16. v0.10.4Oct 18, 2026
  17. v0.10.1Oct 4, 2026
  18. v0.10.0Oct 4, 2026
  19. v0.9.4Oct 4, 2026
  20. v0.9.3Oct 3, 2026
  21. v0.9.2Sep 18, 2026
  22. v0.9.1Sep 18, 2026
  23. v0.9.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts