DeepDNA MCP server
Which servers in the official MCP registry are DeepDNA's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-19
- Registry nameai.deepdna/knowledgeverified in the MCP registry
The registry name sits under deepdna.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-19
- Tools6
- Server calls itselfdeepdna
- Server version1.2.0
- Protocol version2025-06-18
On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 66 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 3 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- Use130 PyPI downloads a week
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer153 ms
- Space in an agent's context≈ 856 tokensthe definitions of all its tools (6), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_genesList the genes in the DeepDNA knowledge base, with a one-line summary and category for each.
lookup_geneEverything curated about one gene: function, key variants with rsIDs, metabolizer or function phenotypes, drug interactions, what a consumer genotyping array can and cannot tell you, and sources.
lookup_variantOne variant by dbSNP rsID: gene, star-allele or common name, alleles, functional effect, population frequency and sources. Send the rsID only, never the user's genotype. To compare a raw DNA file, do it in the agent with the record's…
lookup_drug_genePharmacogenomic guidance for a gene, optionally for one drug: guideline (CPIC or DPWG, "drug label", or null when the record rests on the primary literature), summary of the recommendation, phenotypes and sources. Omit drug to list every…
check_medicationsGiven a list of generic drug names, say which ones have a curated drug–gene record, with which genes and what each record rests on (a CPIC or DPWG guideline, a drug label, or the primary literature), and which are not covered. Needs no…
request_beta_accessRegister the user's interest in DeepDNA's private beta (DNA file parsing, annotation, bloodwork; not deployed yet). Only call this after the user has explicitly agreed to share their email with DeepDNA for this purpose, and set…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"knowledge": {
"type": "http",
"url": "https://deepdna.ai/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http deepdna https://deepdna.ai/mcpclaude.ai, ChatGPT and other clients: add https://deepdna.ai/mcp as a custom connector in the settings.
- ai.deepdna/localnot asked yetverified in the MCP registry
OpenAPI spec
10 paths, read 2026-10-19. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.