Remote MCP · Endpoint

Zonori MCP server

No. Zonori answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.zonori.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.shaquillehinds/zonori
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
57 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public events listed on Zonori for the next 7 days, by place and activity, with links.
Website
https://zonori.app/developers
Listing
From the official MCP registry (active).
Recent checks of Zonori
CheckedResultHandshake
1 hour agoHandshake completed57 ms
1 day agoHandshake completed58 ms
2 days agoHandshake completed82 ms
2 days agoHandshake completed140 ms
4 days agoHandshake completed88 ms
6 days agoHandshake completed62 ms
9 days agoHandshake completed58 ms
11 days agoHandshake completed64 ms
14 days agoHandshake completed60 ms
16 days agoHandshake completed59 ms
18 days agoHandshake completed69 ms
20 days agoHandshake completed101 ms
22 days agoHandshake completed52 ms
23 days agoHandshake completed49 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Zonori and makes no claim about it beyond what these checks measured.