Remote MCP · Endpoint

Openagenda MCP server

No. Openagenda answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/openagenda/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/openagenda
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
77 ms
Tools exposed
46 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
OpenAgenda MCP.
Listing
From the official MCP registry (active).
Recent checks of Openagenda
CheckedResultHandshake
2 hours agoHandshake completed77 ms
22 hours agoHandshake completed131 ms
2 days agoHandshake completed102 ms
3 days agoHandshake completed119 ms
4 days agoHandshake completed81 ms
5 days agoHandshake completed107 ms
6 days agoHandshake completed82 ms
8 days agoHandshake completed66 ms
11 days agoHandshake completed57 ms
13 days agoHandshake completed102 ms
16 days agoHandshake completed309 ms
18 days agoHandshake completed65 ms
20 days agoHandshake completed84 ms
22 days agoHandshake completed72 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed52 ms
27 days agoHandshake completed59 ms
29 days agoHandshake completed44 ms

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

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