Remote MCP · Endpoint

Zambo MCP server

No. Zambo answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://zambo.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.zambo/zambo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
121 ms
Tools exposed
35 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Trust Layer for AI work. Give your AI hands. Every run returns a verifiable receipt. No key needed.
Listing
From the official MCP registry (active).
Recent checks of Zambo
CheckedResultHandshake
2 hours agoHandshake completed121 ms
1 day agoHandshake completed88 ms
4 days agoHandshake completed113 ms
6 days agoHandshake completed89 ms
8 days agoHandshake completed70 ms
9 days agoHandshake completed136 ms
11 days agoHandshake completed63 ms
12 days agoHandshake completed81 ms
13 days agoHandshake completed81 ms
16 days agoHandshake completed298 ms
17 days agoHandshake completed94 ms
19 days agoHandshake completed62 ms
20 days agoHandshake completed129 ms
21 days agoHandshake completed61 ms
22 days agoHandshake completed194 ms

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

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