Ensembl (PyPI) MCP Server

ensembl-mcp PyPI v0.3.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP for the ensembl beta

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 32

Each tool and what it can reach — statically extracted from the published source.

  • batch_get_variants_by_rsidno sensitive capability
  • batch_resolve_coordinatesno sensitive capability
  • batch_resolve_rsidsno sensitive capability
  • bulk_find_genesno sensitive capability
  • find_genes_by_symbolno sensitive capability
  • find_genomesno sensitive capability
  • get_gene_by_idno sensitive capability
  • get_gene_phenotypesno sensitive capability
  • get_genomeno sensitive capability
  • get_homologiesno sensitive capability
Show 22 more tools ↓
  • get_product_by_idno sensitive capability
  • get_protein_sequenceno sensitive capability
  • get_regionno sensitive capability
  • get_releasesno sensitive capability
  • get_sequenceno sensitive capability
  • get_sequence_metadatano sensitive capability
  • get_sequence_to_fileno sensitive capability
  • get_transcriptno sensitive capability
  • get_variantno sensitive capability
  • get_variant_by_rsidno sensitive capability
  • get_variant_clinical_summaryno sensitive capability
  • get_variant_to_fileno sensitive capability
  • get_variants_in_regionno sensitive capability
  • get_variation_versionno sensitive capability
  • get_versionno sensitive capability
  • graphql_queryno sensitive capability
  • graphql_query_to_fileno sensitive capability
  • list_variant_populationsno sensitive capability
  • overlap_regionno sensitive capability
  • resolve_rsidno sensitive capability
  • transcript_searchno sensitive capability
  • variant_recoderno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.3.0 latest A 98/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ensembl-mcp/badge.svg)](https://mcptrustchecker.com/registry/ensembl-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/ensembl-mcp"><img src="https://mcptrustchecker.com/registry/ensembl-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ensembl-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan ensembl-mcp --online --registry pypi

Use the free API → How scoring works

Other implementations of Ensembl 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Learning & Documentation