Remote MCP · Endpoint

DeepDNA MCP server

No. DeepDNA answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://deepdna.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.deepdna/knowledge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
165 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pharmacogenomics for AI agents: cited drug–gene, gene and rsID lookups plus a medication screen.
Listing
From the official MCP registry (active).
Recent checks of DeepDNA
CheckedResultHandshake
20 minutes agoHandshake completed165 ms
9 days agoHandshake completed428 ms
9 days agoHandshake completed493 ms
11 days agoHandshake completed728 ms
12 days agoHandshake completed602 ms
13 days agoHandshake completed787 ms
14 days agoHandshake completed485 ms
15 days agoHandshake completed922 ms
16 days agoHandshake completed498 ms
19 days agoHandshake completed464 ms
21 days agoHandshake completed129 ms
24 days agoHandshake completed190 ms
26 days agoHandshake completed208 ms
28 days agoHandshake completed160 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 27.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with DeepDNA and makes no claim about it beyond what these checks measured.