Remote MCP · Endpoint

Hashgrid DNA MCP server

Yes, as of 52 minutes ago: the request timed out.

DownLast checked 52 minutes ago

Server URL

https://dna.hashgrid.ai/mcp

The last check failed: the request timed out.

Registry name
ai.hashgrid/dna
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
15 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
A search engine that learns from your grades. Store text, records, images or embeddings.
Listing
From the official MCP registry (active).
Recent checks of Hashgrid DNA
CheckedResultHandshake
52 minutes agoFailed - the request timed out—
3 days agoFailed - the server returned an HTTP error—
12 days agoHandshake completed284 ms
13 days agoHandshake completed278 ms
14 days agoHandshake completed287 ms
15 days agoHandshake completed279 ms
17 days agoHandshake completed279 ms
18 days agoHandshake completed295 ms
18 days agoHandshake completed412 ms
20 days agoHandshake completed287 ms
22 days agoHandshake completed284 ms
25 days agoHandshake completed492 ms
27 days agoHandshake completed287 ms
29 days agoHandshake completed279 ms

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

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