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.

DeepDNA

REMOTE · DEEPDNA.AI

Pharmacogenomics for AI agents: cited drug–gene, gene and rsID lookups plus a medication screen.

Available components

0 this week 85 Trust /100

Last scanned (17 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 616 tokens (~123/item across 5 items; 5 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 Management83
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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 (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83.

  • 10 Nov 26 −3
    • Stability: pass → fail ▼ security
  • 9 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: pass → fail ▼ functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: pass → 0.97 functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://deepdna.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=deepdna.ai CN=WE1,O=Google Trust Services,C=US 5 Nov 2026 3 Feb 2027 ECDSA 256 ECDSA-SHA256 99811891e9e788330e2956af6a82a299
SANs: deepdna.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of deepdna.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
deepdna.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://deepdna.ai/mcp Verified 200
http (plaintext) http://deepdna.ai/mcp HTTPS enforced 301 https://deepdna.ai/mcp
MCP tools · 5 exposed · ~375 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
check_medications ~89

Given 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 genotype.

NameTypeReqDescription
medicationsarrayyesGeneric names, e.g. ["clopidogrel", "simvastatin"].

No output schema declared.

No examples provided.

list_genes ~29

List the genes in the DeepDNA knowledge base, with a one-line summary and category for each.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_drug_gene ~106

Pharmacogenomic 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 drug curated for that gene.

NameTypeReqDescription
drugstring–Generic drug name, e.g. clopidogrel. Optional.
genestringyesPharmacogene symbol, e.g. CYP2C19.

No output schema declared.

No examples provided.

lookup_gene ~70

Everything 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.

NameTypeReqDescription
symbolstringyesHGNC gene symbol, e.g. CYP2C19. Case-insensitive.

No output schema declared.

No examples provided.

lookup_variant ~81

One 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. A single variant is not a phenotype or metabolizer status.

NameTypeReqDescription
rsidstringyesdbSNP identifier, e.g. rs4244285.

No output schema declared.

No examples provided.

Install

How do I install the DeepDNA MCP server?

DeepDNA is a hosted endpoint at https://deepdna.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · deepdna.ai

# add to Claude Code
claude mcp add --transport http ai-deepdna-knowledge 'https://deepdna.ai/mcp'
Common questions

What is the DeepDNA MCP server?

DeepDNA is an MCP server listed in the public MCP registry as ai.deepdna/knowledge. Pharmacogenomics for AI agents: cited drug–gene, gene and rsID lookups plus a medication screen. This page covers its hosted endpoint (https://deepdna.ai/mcp).

Is the DeepDNA MCP server safe to use?

DeepDNA scores 85 out of 100 on VerifyMCP. 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 MCP server expose?

DeepDNA exposes 5 tools: list_genes, lookup_gene, lookup_variant, lookup_drug_gene, check_medications. Their descriptions and schemas cost roughly 375 tokens of context every time the server is loaded.

Does the DeepDNA MCP server require authentication?

No. We connected to DeepDNA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DeepDNA MCP server still maintained?

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

What did VerifyMCP test on the DeepDNA MCP server?

VerifyMCP ran 13 checks on DeepDNA, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.