Remote MCP · Endpoint

Aura DNA MCP server

No. Aura DNA answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://auradna.app/api/agents/mcp

The last check completed an MCP handshake.

Registry name
io.github.ishtiaqrahman/aura-dna
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
6 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Seasonal palettes, color-matched essentials, and your connected Aura DNA color and style reports.
Listing
From the official MCP registry (active).
Recent checks of Aura DNA
CheckedResultHandshake
44 minutes agoHandshake completed100 ms
3 days agoHandshake completed100 ms
12 days agoHandshake completed1.13 s
13 days agoHandshake completed2.38 s
14 days agoHandshake completed147 ms
15 days agoHandshake completed1.59 s
16 days agoHandshake completed1.31 s
17 days agoHandshake completed1.40 s
18 days agoHandshake completed145 ms
19 days agoFailed - the server returned an HTTP error—
22 days agoFailed - the server returned an HTTP error—
25 days agoHandshake completed1.59 s
27 days agoHandshake completed100 ms

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

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 Aura DNA and makes no claim about it beyond what these checks measured.