Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AlphaFold Sovereign MCP

PYPI · ALPHAFOLD-SOVEREIGN-MCP

MCP server for AlphaFold and 8 other biomedical data sources with a local SQLite knowledge graph

−1 this week 90 Trust /100

Last scanned (14 hours ago)

Scores higher than 93% of PyPI servers

Category Health and Science

Recent critical change

GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to smaniches/alphafold-sovereign-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4667 tokens (~160/item across 29 items; 29 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability check failed: the tool surface changed between 1.4.10 and 1.5.10: 1 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 29 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: unverified → pass ▲ functional
  • 4 Nov 26 −16
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: pass → unverified ▼ functional
    • Package version: 1.5.9 → 1.5.10 functional
  • 31 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −17
    • Malware scan: pass → unverified ▼ security
    • Package version: 1.5.7 → 1.5.9 functional
  • 24 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 23 Oct 26 −16
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → fail ▼ security
    • Stability: pass → 0.97 functional
    • Package version: 1.5.4 → 1.5.7 functional
    • Package version: 1.5.4 → 1.5.5 functional
  • 22 Oct 26 +91
    • GHSA-6q48-6c7w-9gw2 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
    • Score status: failed → scored ▲ functional
  • 21 Oct 26 −91
    • GHSA-6q48-6c7w-9gw2 affects this package: none ▼ critical
    • Known CVEs: pass → fail ▼ critical
    • Score status: scored → failed ▼ critical
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/alphafold-sovereign-mcp@1.5.10

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo smaniches/alphafold-sovereign-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/smaniches/alphafold-sovereign-mcp/.github/workflows/release.yml@refs/tags/v1.5.10
Rekor log index 3683925024
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:0c3eeff06344a6a15bb956cbf947c05eb07be203d785373e12938a7fa9c81388

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 33 packages
Packages resolved 33
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 29 exposed · ~4,667 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_structural_confidence ~127

Analyze AlphaFold structural confidence using pLDDT and PAE. Returns a structural reliability summary (not a per-residue profile): - **pLDDT**: the model's mean confidence (AlphaFold DB ``globalMetricValue``) plus a coarse confidence tier - **PAE** (predicted aligned error): mean and max inter-residue uncertainty and PAE-derived domain boundaries - **Druggability pre-screen**: model confidence limitations; actual ordered fraction and ligand suitability are NOT assessed

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

assess_target_druggability ~168

Comprehensive druggability assessment for a protein target. Integrates four independent druggability signals into a HOT/WARM/COLD/NOT_DRUGGABLE classification: 1. **Drug precedent** — ChEMBL approved drugs + clinical compounds 2. **Tractability** — Open Targets tractability labels (small-molecule, antibody, PROTAC) 3. **Structural confidence** — AF2 pLDDT (model-local confidence, not binding evidence) 4. **Population constraint** — gnomAD LOEUF (gene-level LoF depletion, not toxicity evidence) This is an author-defined, uncalibrated research score, not a validated predictive model, clinical safety result, or independent biological fact.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

classify_variant_acmg ~90

Generate a draft ACMG/AMP variant classification framework. Reports computational observations that may inform an expert's later disease-specific ACMG/AMP review. This tool does NOT establish ACMG criteria or assign a pathogenicity class: generic consequence, model scores, and population frequencies are insufficient without clinical disease mechanism, inheritance, and criterion-specific validation.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

compare_disease_target_overlap ~88

Compare the protein target landscapes of two diseases. Identifies shared and unique targets between two diseases — a key analysis for drug repurposing, identifying shared mechanisms, and understanding comorbidity. Returns: - Shared targets (present in both disease target sets) - Unique to Disease A / Disease B - Jaccard similarity score of target sets

NameTypeReqDescription
paramsobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

compare_proteins_topologically ~184

Compare multiple proteins using a TDA-fingerprint distance. Computes a pairwise distance matrix between the TDA fingerprints of the provided proteins. Distance metric: L2 distance between length-normalised 64-dimensional fingerprint vectors (see ``_fingerprint_distance``). Distance = 0 means identical fingerprints; larger values mean more divergent fingerprints. This is **not** a Wasserstein distance between persistence diagrams. Applications: Possible uses (all of which require independent validation before any downstream use): - Drug-repurposing triage: proteins with low fingerprint distance may share gross topology. - Off-target screening: family members with near-zero distance. - Cross-species comparison of the same gene's structure. None of these are direct functional or sequence-similarity measures.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

compute_topology_fingerprint ~255

Compute a rotation-invariant topological fingerprint of a protein's fold. Fetches the AlphaFold model for ``uniprot_id`` and derives an exploratory 64-dimensional geometric/topological feature vector from Cα coordinates. With GUDHI installed, H0 and H1 are computed on the 15-Å Vietoris-Rips 2-skeleton. H2 is NOT computed. Without GUDHI only a 4-Å graph component count and geometric statistics are available. Betti numbers describe this chosen filtration, not protein domains, β-barrels, drug cavities, molecular function, or an experimental structure. Returns the fingerprint vector, the Betti numbers, the residue count, and which method ran. Full persistent homology needs the optional ``[tda]`` extra (``gudhi``); without it a coarse fallback runs that does NOT compute persistent homology, and the result flags this. Returns a no-structure result when AlphaFold DB has no model for the accession. This is a coarse, geometry-only summary — not a substitute for sequence alignment, RMSD, or functional-homology assessment.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

detect_intrinsically_disordered ~255

Flag low-confidence modeled regions as intrinsic-disorder candidates. Reads per-residue AlphaFold pLDDT from PDB C-alpha records and groups contiguous runs below 50. Low pLDDT may reflect intrinsic disorder, missing binding partners, alternate conformations, or model uncertainty; it is NOT independent evidence that a region is disordered. Returns model-local residue indices, observed PDB chain/residue identifiers, and positional descriptions of low-pLDDT runs. These labels describe model geometry, not validated linkers, tails, disorder or function. Legacy idr_fraction and disordered_residue_count remain deprecated numeric aliases of low-pLDDT measurements, NOT validated intrinsic-disorder assays. Prefer low_plddt_* fields for scientific interpretation. PDB numbering is not mapped to full-length UniProt via SIFTS here. This implementation is a reproducible screening heuristic, not a validated disorder predictor, biomolecular mechanism classifier, or clinical result. For background on intrinsic disorder, see Ruff & Pappu (2021), J Mol Biol. 433:167208; that paper does not validate these cutoffs or code.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

export_research_dataset ~128

Export the stored knowledge-graph data for downstream analysis. Returns all stored entities as JSON-serialisable dicts, suitable for: - Loading into pandas DataFrames for ML feature engineering - Importing into R or Julia for statistical analysis - Feeding into downstream bioinformatics pipelines Example (Python):: import pandas as pd result = await export_research_dataset(ExportInput(tables=["variants"])) df = pd.DataFrame(result["data"]["variants"]) high_tier = df[df["clinical_tier"] == "HIGH"]

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

find_drug_gene_network ~120

Traverse the local knowledge graph from a seed entity. Given a seed (UniProt ID, gene symbol, or MONDO disease ID), expands its immediate neighbourhood in the stored drug-gene-disease graph: a gene symbol resolves to its encoded proteins and reported variants, a UniProt accession resolves to its stored protein record, and a MONDO disease resolves to drugs with an indication for it. The store is populated by the storage API, or retained from historical database versions.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

find_drug_repurposing_candidates ~285

Rank existing clinical-stage drugs as repurposing candidates for a disease. Surfaces approved or trial-stage drugs whose target carries genetic/association evidence for the disease — i.e. drug-repurposing hypotheses. For the full approved-plus-pipeline drug picture of a disease (not only repurposing candidates), use ``map_disease_drug_landscape`` instead. How it works: take the top ``target_limit`` Open Targets evidence-scored targets for the disease; for each, fetch its ChEMBL drugs at or above ``min_phase``; drop duplicate molecules; rank by ``composite_repurposing_score = OT evidence score × (max ChEMBL phase / 4)``. Ranking uses clinical and association evidence only — no protein structure. Returns a JSON record whose ``candidates`` list holds up to 20 drugs (each with ChEMBL ID, name, max phase, target gene/UniProt, OT evidence score, composite score, and mechanism), plus the candidate count and the methodology string. Returns an empty ``candidates`` list with a ``message`` when the disease has no Open Targets associations. The composite score is a prioritisation aid, not an efficacy prediction — validate mechanistically before acting on it.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

find_evolutionary_structural_shifts ~81

Report ortholog sequence identity and exploratory structural distances. Distances between Cα-derived feature vectors are not calibrated evolutionary, functional, binding, or antibody cross-reactivity measures. The GUDHI and geometric-proxy methods are distinguished in each result. There is deliberately no cross-method conservation ranking.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

generate_variant_clinical_report ~237

Generate a multi-source variant interpretation report. Cross-references evidence from up to seven upstream databases for a single HGVS variant into one structured research report. It preserves source classifications and computational observations separately; it does not assign an independent clinical tier or establish ACMG criteria. 1. **Ensembl VEP** — functional consequence, SIFT/PolyPhen/CADD predictions 2. **ClinVar** — clinical pathogenicity classifications and review status 3. **gnomAD v4** — population allele frequencies (gnomAD v4, ~807k individuals) 4. **AlphaMissense** — deep-learning missense pathogenicity (Cheng et al. 2023) 5. **Open Targets** — disease-gene evidence scores 6. **DisGeNET** — curated gene-disease association scores 7. **ChEMBL** — approved drugs acting on the gene product The report includes unassessed ACMG-related computational signals, sequence consequences, and gene-level drug context. It does not compute variant-specific three-dimensional structural impact.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_common_disease_targets ~217

Profile the top drug targets for a curated set of common diseases in one call. Use this for a fast landscape scan across a whole disease area: given a ``category`` (e.g. 'oncology'), it looks up the curated MONDO diseases in that category and returns each one's top Open Targets evidence-scored targets, in parallel. To profile a single disease you already have a MONDO ID for, use ``get_disease_targets`` instead — this tool is its category-level, multi-disease counterpart and does not accept a raw MONDO ID. Queries Open Targets live. Returns a JSON string with the ``category``, the number of diseases profiled, and a ``profile`` object mapping each disease to its MONDO ID and top targets (per-disease errors are reported inline, not raised). Returns a JSON error object listing the valid values when the category — or a ``disease_name`` filter within it — is not recognised.

NameTypeReqDescription
paramsobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_disease_targets ~232

Return top protein targets for a disease with Open Targets evidence scores. Evidence score breakdown (0–1 per data type): - ``genetic_association``: GWAS + rare-variant signals - ``somatic_mutation``: Cancer somatic variant evidence - ``known_drug``: Approved or clinical-stage drugs - ``affected_pathway``: Pathway membership (Reactome, SIGNOR) - ``literature``: Text-mining evidence (Europe PMC) - ``animal_model``: Knockout / model organism phenotypes - ``rna_expression``: Differential expression evidence ``drug_count`` is the target's Open Targets drug-and-clinical-candidate record count (all stages) and ``tractable`` is true when any Open Targets tractability bucket is set; both are observed per row and are ``null`` only when the source omits them. Example: ``get_disease_targets(disease_id='MONDO:0007254', limit=15)`` returns top 15 targets for breast carcinoma.

NameTypeReqDescription
paramsobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_gene_phenotype_profile ~118

Return all HPO phenotypes associated with a gene, plus gnomAD constraint. Useful for understanding the clinical consequences of variants in a gene before requesting structural context. Returns: - HPO phenotypes linked to the gene (from HPO association database) - gnomAD LOEUF / pLI constraint scores - Interpretation of constraint (haploinsufficient / tolerant / moderate) Example: ``get_gene_phenotype_profile(gene_symbol='SCN1A')``

NameTypeReqDescription
paramsobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_knowledge_graph_stats ~45

Return statistics about the local knowledge graph. Shows entity counts, database size, and last activity — useful for understanding the current contents and coverage of the local store.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_protein_structure ~278

Retrieve a protein's AlphaFold model: metadata, download URLs, optional coordinates. The single entry point for getting the predicted structure itself. Returns the AlphaFold DB entry metadata — entry ID, model version and creation date, organism, gene, UniProt description, the amino-acid sequence and its length, and the model's mean pLDDT — plus stable download URLs for the PDB and mmCIF coordinate files, the PAE matrix, and the AlphaMissense substitutions CSV. The PAE image URL is only present in legacy API responses. Set ``include_coordinates`` to embed the full PDB coordinate text directly. Use the sibling structure tools for *interpretation* rather than retrieval, so their scopes don't overlap: ``analyze_structural_confidence`` for a pLDDT/PAE confidence read, ``score_binding_pocket_geometry`` for pockets, ``compute_topology_fingerprint`` for fold topology, and ``detect_intrinsically_disordered`` for disorder. This tool hands you the structure and its handles; it does not score or interpret the model. Returns ``structure_available: false`` with an explanatory note when AlphaFold DB has no model for the accession — an expected coverage gap, not a server fault.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_target_diseases ~86

Return all diseases associated with a protein target via Open Targets. Accepts a UniProt accession and returns the full disease landscape for that target — essential for target-validation and indication-expansion. Example: ``get_target_diseases(uniprot_id='P04637')`` returns all diseases associated with TP53 / p53.

NameTypeReqDescription
paramsobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

lookup_disease ~118

Retrieve a disease record from the MONDO unified disease ontology. Returns the canonical MONDO entry with: - Disease name, definition, synonyms - ICD-10 / ICD-11 codes (for clinical coding / EHR integration) - OMIM, Orphanet, MeSH, DOID cross-references - Immediate parent and child terms in the MONDO hierarchy Example: ``lookup_disease(mondo_id='MONDO:0005010')`` returns the record for coronary artery disease.

NameTypeReqDescription
paramsobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

lookup_phenotype ~93

Retrieve an HPO phenotype term with associated disease annotations. Returns: - Phenotype label, definition, synonyms - Diseases annotated with this phenotype (from HPO + OMIM + Orphanet) - Parent phenotype terms Example: ``lookup_phenotype(hpo_id='HP:0001250')`` returns the Seizure phenotype with ~400 associated diseases.

NameTypeReqDescription
paramsobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

map_disease_drug_landscape ~96

Map a bounded, source-attributed therapeutic landscape for a disease. Returns retrieved approved drugs, pipeline agents, top druggable targets, and an exploratory summary for a given MONDO disease. Combines Open Targets evidence with ChEMBL drug indications and MONDO disease hierarchy to produce a comprehensive landscape report used in business development, competitive intelligence, and R&D portfolio decisions.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

phenotype_to_structures ~133

Map a clinical phenotype to the protein structures of its disease targets. Pipeline: 1. Resolve HPO term → associated diseases 2. For each disease → top protein targets (Open Targets) 3. For each target → UniProt ID (for AlphaFold retrieval) Use the returned UniProt IDs with ``analyze_structural_confidence`` to retrieve AlphaFold structural confidence (pLDDT/PAE). Example: ``phenotype_to_structures(hpo_id='HP:0002621')`` maps Atherosclerosis → disease targets → UniProt IDs.

NameTypeReqDescription
paramsobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

query_protein_database ~201

Recall proteins already stored in the local knowledge graph. This is a local-recall query, not a live lookup: it returns only proteins that have previously been written through the knowledge-graph storage API (or retained from earlier versions of the database). No upstream API is called. To assess a protein that may not be stored yet, use ``assess_target_druggability`` (druggability tier) or ``analyze_structural_confidence`` (pLDDT), which query live sources. Filters are combined with AND; omit a filter to leave that dimension unconstrained. Returns a JSON record with the applied ``query``, a ``result_count``, and the matching ``proteins`` rows. The list is empty when nothing stored matches; an empty result means the local store has no matching row, not that the protein is absent from upstream biology.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

query_variant_database ~89

Search the local knowledge graph for stored variants. Returns variants matching the filter criteria. No upstream API calls are made — all data is served from the local SQLite knowledge graph, which is populated only through explicit writes to the knowledge-graph storage API. Historical SQLite files may retain illustrative rows from older versions; these should not be interpreted as independently verified biology.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

resolve_icd10_to_mondo ~110

Resolve an ICD-10 clinical code to MONDO disease ontology terms. Enables integration between clinical / EHR data (which uses ICD-10) and the research-grade MONDO ontology used by Open Targets, HPO, and this MCP. Example: ``resolve_icd10_to_mondo(icd10_code='I21.0')`` maps ST-elevation MI (ICD-10) to MONDO coronary disease terms.

NameTypeReqDescription
paramsobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

score_binding_pocket_geometry ~292

Identify and score putative binding pockets from AlphaFold geometry. Detects pockets with a geometry-only heuristic. Residues in the inner 60 percent of the structure by distance from the centroid are taken as the pocket-forming core, then grown greedily into clusters within an 8 Angstrom radius. A cluster is kept as a putative pocket when it has at least ``min_pocket_residues`` members and a mean pLDDT of at least 50. Each pocket reports a radius of gyration (compactness of the pocket residues), a centroid offset (distance of the pocket centroid from the structure centroid; larger means more peripheral), mean pLDDT, and an uncalibrated geometry score. Centroid offset does not measure solvent exposure, cavity validity, or ligand binding. The druggability index runs 0 to 100 and is the sum of four equally weighted 0 to 25 sub-scores: residue count, radius of gyration, mean pLDDT, and centroid offset. This is a fast, dependency-free pre-screen, not a substitute for a validated pocket detector such as fpocket or P2Rank. It needs no ML model, is fully reproducible from AlphaFold coordinates, and runs in air-gapped deployments.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

search_diseases ~84

Search for diseases by name or keyword using the MONDO ontology. Returns a ranked list of matching diseases with MONDO IDs and cross-references. Useful for resolving a clinical term to a canonical identifier before querying targets or phenotypes. Example: ``search_diseases(query='breast cancer', limit=5)``

NameTypeReqDescription
paramsobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

synthesize_protein_dossier ~83

Generate a complete protein intelligence dossier from 7 data sources. It assembles disease associations, drug precedent, population constraint, ClinVar variants, and cross-species orthologs for one protein into a single structured record. It composes upstream records and author-defined research heuristics, without issuing clinical conclusions.

NameTypeReqDescription
paramsobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

triage_variant_3d ~374

Retrieve source-reported variant evidence for research. Fuses the upstream signals this tool currently wires into a single prioritised report: 1. **Pathogenicity** — ClinVar interpretation + review status. The ``alphamissense_score`` / ``alphamissense_interpretation`` fields are always ``null`` / "Not available" here: AlphaMissense is not wired into this tool. For an AlphaMissense pathogenicity score use ``generate_variant_clinical_report``. 2. **Population genetics** — gnomAD LOEUF / pLI gene-constraint scores. Per-variant allele frequencies and the per-ancestry breakdown are not wired into this tool. 3. **Disease associations** — a placeholder note pointing at ``get_target_diseases()``; the Open Targets / MONDO traversal is a roadmap (Wave-3) item. 4. **Structural context** — a text note pointing at ``analyze_structural_confidence`` (resolve the gene to a UniProt accession first); the AlphaFold pLDDT / PAE join into this report is a roadmap (Wave-3) item. Returns the legacy ``pathogenicity_tier`` key as NOT_ASSESSED. Raw verified ClinVar classifications remain source-attributed in the pathogenicity section; they are not converted into a local risk tier. Gene-relative candidates remain explicitly unverified. AlphaMissense is not wired into this particular tool. The report is not a calibrated risk estimate. Example: ``triage_variant_3d(hgvs='BRCA1:c.181T>G')``

NameTypeReqDescription
paramsobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the AlphaFold Sovereign MCP server?

AlphaFold Sovereign MCP runs locally as a PyPI package, launched with uvx alphafold-sovereign-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · alphafold-sovereign-mcp

# add to Claude Code
claude mcp add smaniches-alphafold-sovereign-mcp -- uvx alphafold-sovereign-mcp
Common questions

What is the AlphaFold Sovereign MCP server?

AlphaFold Sovereign MCP is listed in the public MCP registry as io.github.smaniches/alphafold-sovereign-mcp. MCP server for AlphaFold and 8 other biomedical data sources with a local SQLite knowledge graph. This page covers its PyPI package (alphafold-sovereign-mcp).

Is the AlphaFold Sovereign MCP server safe to use?

AlphaFold Sovereign MCP scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AlphaFold Sovereign MCP server expose?

AlphaFold Sovereign MCP exposes 29 tools: lookup_disease, search_diseases, lookup_phenotype, get_gene_phenotype_profile, get_disease_targets, and 24 more. Their descriptions and schemas cost roughly 4,667 tokens of context every time the server is loaded.

Is the AlphaFold Sovereign MCP server still maintained?

AlphaFold Sovereign MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the AlphaFold Sovereign MCP server under?

AlphaFold Sovereign MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the AlphaFold Sovereign MCP server?

VerifyMCP ran 16 checks on AlphaFold Sovereign MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.