DeepDNA local
PYPI · DEEPDNA-MCP
Reads a raw DNA file on your computer and reports the variants DeepDNA curates, with sources.
Available components
Last scanned (18 hours ago)
Scores higher than 86% of PyPI servers
Category Health and Science
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 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to alfonsoguv/deepdna-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 637 tokens (~318/item across 2 items; 2 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 Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety50
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "do not tell the user", at byte 463 of that field. See how to fix → Fail
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.1 → 0.1.2 functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed pypi/deepdna-mcp@0.1.2
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 | alfonsoguv/deepdna-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/alfonsoguv/deepdna-mcp/.github/workflows/publish.yml@refs/tags/v0.1.2 |
| Rekor log index | 3564496566 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:ca8e5f9c69caac85bc7af1e8218ecc1d45f2f554bf124bfe0418cdfd4027c760 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
lookup_drug_gene Look up drug-gene guidance ~139
Cited pharmacogenomic guidance for a gene, optionally for one drug, from DeepDNA's public API: the guideline (CPIC or DPWG where one exists, otherwise a drug label or the primary literature), a summary and sources. Sends only the gene and drug names. The phenotype groups it lists are the guideline's own: do not place the user in one from read_dna_file counts. Educational information, not a dose or a prescription.
| Name | Type | Req | Description |
|---|---|---|---|
| drug | – | – | Generic drug name, e.g. "clopidogrel" |
| gene | string | yes | Gene symbol, e.g. "CYP2C19" |
Structured output declared, but exposes no named fields.
No examples provided.
read_dna_file Read a raw DNA file on this computer ~297
Read the user's raw DNA file (23andMe, AncestryDNA, MyHeritage or FamilyTreeDNA; .txt, .csv or .zip) on this computer and report, for each curated variant, one of four states: read, no_call, not_in_file, or unexpected_letters (the file's letters fit neither the record nor its complement). For positions the record marks as countable it gives how many copies of the variant allele the file shows, with the record's text and sources. Pass `genes` for what the user asked about (for example ["CYP2C19"] before discussing clopidogrel). APOE, BRCA1 and HFE are disease-risk genes: they are read only when named in `genes`, so do not offer or report them unless the user asks for them by name. A count at one position is not a metabolizer status, diplotype, diagnosis or dose: say so, and refer anything that could matter for health to a clinician and a validated test.
| Name | Type | Req | Description |
|---|---|---|---|
| genes | – | – | Gene symbols the user asked about, e.g. ["CYP2C19"] |
| path | string | yes | Full path to the raw DNA file on this computer, e.g. /Users/name/Downloads/genome.txt |
| sex | – | – | Only if the user gives it: some chromosome X positions (G6PD) need it |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the DeepDNA local MCP server?
DeepDNA local runs locally as a PyPI package, launched with uvx deepdna-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 · deepdna-mcp
claude mcp add ai-deepdna-local -- uvx deepdna-mcp
What is the DeepDNA local MCP server?
DeepDNA local is an MCP server listed in the public MCP registry as ai.deepdna/local. Reads a raw DNA file on your computer and reports the variants DeepDNA curates, with sources. This page covers its PyPI package (deepdna-mcp).
Is the DeepDNA local MCP server safe to use?
DeepDNA local scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 DeepDNA local MCP server expose?
DeepDNA local exposes 2 tools: read_dna_file, lookup_drug_gene. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.
Is the DeepDNA local MCP server still maintained?
DeepDNA local is still listed as active in the MCP registry. We last reached this channel on 4 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 DeepDNA local MCP server under?
DeepDNA local declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.