2 checks that ran failed — supply chain and version behavior — so this release can’t be trusted as-is.
- Publisher
- io.github.smaniches
- Install
- pypi:alphafold-sovereign-mcp, pypi:alphafold-sovereign-mcp, pypi:alphafold-sovereign-mcp, pypi:alphafold-sovereign-mcp, pypi:alphafold-sovereign-mcp, pypi:alphafold-sovereign-mcp, pypi:alphafold-sovereign-mcp, pypi:alphafold-sovereign-mcp, pypi:alphafold-sovereign-mcp, pypi:alphafold-sovereign-mcp, pypi:alphafold-sovereign-mcp, pypi:alphafold-sovereign-mcp
- Versions
- 12
- Inspected
- 5 of 6 checks · 75%
- Scored
- 2026-09-04 · rubric 1.0.0
What we checked
Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.
Injection surface
unscannable25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.
Supply chain
fail25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
Python build script executes at build time: network call in build script
Credential hygiene
pass15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
Reads secrets from the environment (e.g. src/alphafold_sovereign/clients/_base.py) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.
Permission scope
pass15% of gradeDeclared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.
Network egress present (src/alphafold_sovereign/clients/_base.py: outbound HTTP/socket call) — expected for most servers and not a finding on its own. No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.
Version behavior
fail10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
vs prior 1.4.7 (patch bump): new capability primitive(s) in source: http-client, subprocess; new hardcoded outbound host/BCC destination(s): alphafold.ebi.ac.uk, anywhere.test, api.disgenet.com, api.example.com, api.example.test, api.github.com, api.monarchinitiative.org, api.platform.opentargets.org, demo.test, eutils.ncbi.nlm.nih.gov, evil.example, example.com, example.invalid, example.org, files.example.org, github.com, gnomad.broadinstitute.org, ontology.jax.org, platform.opentargets.org, purl.obolibrary.org, pypi.org, rest.ensembl.org, smaniches.github.io, token.actions.githubusercontent.com, topologica.ai, www.disgenet.com, www.ebi.ac.uk, www.ncbi.nlm.nih.gov, www.wwpdb.org, x, x.test.
Transport config
warn10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
manifest/source references tracking behavior — disclosure
Version history
Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.
| Version | Published | Grade | Score | Inspected | Change |
|---|---|---|---|---|---|
| v1.4.9 · current | 2026-09-03 | C | 60 | 5/6 · 75% | B→C in v1.4.9 |
| v1.4.7 | 2026-08-20 | B | 85 | 5/6 · 75% | ±0 |
| v1.4.6 | 2026-08-20 | B | 75 | 4/6 · 65% | ±0 |
| v1.4.5 | 2026-08-10 | B | 75 | 3/6 · 55% | ±0 |
| v1.4.3 | 2026-07-29 | B | 95 | 5/6 · 75% | C→B in v1.4.3 |
| v1.3.0 | 2026-06-23 | C | 70 | 4/6 · 65% | ±0 |
| v1.2.0 | 2026-06-09 | C | 70 | 4/6 · 65% | — |