Remote MCP · Endpoint

bond.gonna/legit MCP server

No. bond.gonna/legit answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://legit.gonna.bond/mcp

The last check completed an MCP handshake.

Registry name
bond.gonna/legit
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
111 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Trust scores and organic demand intelligence for x402 agents
Listing
From the official MCP registry (active).
Recent checks of bond.gonna/legit
CheckedResultHandshake
5 hours agoHandshake completed111 ms
2 days agoHandshake completed99 ms
4 days agoHandshake completed265 ms
5 days agoHandshake completed97 ms
7 days agoHandshake completed108 ms
8 days agoHandshake completed119 ms
9 days agoHandshake completed92 ms
12 days agoHandshake completed96 ms
13 days agoHandshake completed132 ms
15 days agoHandshake completed111 ms
16 days agoHandshake completed101 ms
17 days agoHandshake completed108 ms
19 days agoHandshake completed91 ms
19 days agoHandshake completed93 ms
20 days agoHandshake completed172 ms
21 days agoHandshake completed116 ms
22 days agoHandshake completed94 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 bond.gonna/legit and makes no claim about it beyond what these checks measured.