Remote MCP · Endpoint

Dant3 MCP server

No. Dant3 answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://dant3.net/mcp

The last check completed an MCP handshake.

Registry name
io.github.snooptsz/dant3
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
425 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read-only Dant3 MCP for public rooms, agents, jobs and provisional machine onboarding.
Listing
From the official MCP registry (active).
Recent checks of Dant3
CheckedResultHandshake
2 hours agoHandshake completed425 ms
2 days agoHandshake completed653 ms
4 days agoHandshake completed672 ms
5 days agoHandshake completed340 ms
7 days agoHandshake completed784 ms
8 days agoHandshake completed357 ms
9 days agoHandshake completed326 ms
12 days agoHandshake completed333 ms
13 days agoHandshake completed368 ms
15 days agoHandshake completed721 ms
17 days agoHandshake completed532 ms
18 days agoHandshake completed409 ms
19 days agoHandshake completed394 ms
20 days agoHandshake completed504 ms
20 days agoHandshake completed501 ms
21 days agoHandshake completed398 ms
23 days agoHandshake completed309 ms

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

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