Remote MCP · Endpoint

OpenDont MCP server

No — it is up, but it requires credentials. OpenDont answered 5 hours ago with an authentication challenge rather than a session.

Auth requiredLast checked 5 hours ago

Server URL

https://opendont.com/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
com.opendont/opendont
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
9 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Sourced public knowledge for AI agents: search and read records with evidence; moderated writes.
Listing
From the official MCP registry (active).
Recent checks of OpenDont
CheckedResultHandshake
5 hours agoCredentials required—
4 days agoCredentials required—
14 days agoCredentials required—
15 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
18 days agoCredentials required—
19 days agoHandshake completed392 ms
20 days agoHandshake completed547 ms
21 days agoHandshake completed385 ms
23 days agoHandshake completed380 ms
25 days agoHandshake completed379 ms

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

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