Remote MCP · Endpoint

OpenMandate MCP server

No. OpenMandate answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://mcp.openmandate.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.openmandate/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
58 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
OpenMandate is in private development and is not accepting new mandates or integrations.
Listing
From the official MCP registry (active).
Recent checks of OpenMandate
CheckedResultHandshake
8 hours agoHandshake completed58 ms
2 days agoHandshake completed49 ms
4 days agoHandshake completed58 ms
5 days agoHandshake completed56 ms
7 days agoHandshake completed104 ms
8 days agoHandshake completed52 ms
9 days agoHandshake completed40 ms
12 days agoHandshake completed53 ms
13 days agoHandshake completed56 ms
15 days agoHandshake completed59 ms
16 days agoHandshake completed41 ms
17 days agoHandshake completed57 ms
18 days agoHandshake completed34 ms
19 days agoHandshake completed46 ms
20 days agoHandshake completed50 ms
21 days agoHandshake completed46 ms
23 days agoHandshake completed54 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 OpenMandate and makes no claim about it beyond what these checks measured.