Remote MCP · Endpoint

Agora MCP server

No. Agora answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://agora-console-production.up.railway.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.mo-grantsmith/agora
Transport
Streamable HTTP
Protocol negotiated
2026-07-28
Handshake latency
99 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Find governed AI capabilities and verify signed receipts. Read-only, no account.
Listing
From the official MCP registry (active).
Recent checks of Agora
CheckedResultHandshake
5 hours agoHandshake completed99 ms
2 days agoHandshake completed93 ms
4 days agoHandshake completed100 ms
5 days agoHandshake completed117 ms
7 days agoHandshake completed105 ms
8 days agoHandshake completed94 ms
9 days agoHandshake completed94 ms
12 days agoHandshake completed96 ms
13 days agoHandshake completed90 ms
15 days agoHandshake completed99 ms
16 days agoHandshake completed98 ms
17 days agoHandshake completed107 ms
18 days agoHandshake completed94 ms
19 days agoHandshake completed93 ms
20 days agoHandshake completed94 ms
21 days agoHandshake completed103 ms
22 days agoHandshake completed121 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 Agora and makes no claim about it beyond what these checks measured.