Remote MCP · Endpoint

SAID Protocol MCP server

No. SAID Protocol answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://api.saidprotocol.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Jugmaster/said-protocol
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
98 ms
Tools exposed
3 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Check a Solana wallet before you pay it, a token before you buy it. Agent identity and reputation.
Listing
From the official MCP registry (active).
Recent checks of SAID Protocol
CheckedResultHandshake
5 hours agoHandshake completed98 ms
4 days agoHandshake completed101 ms
7 days agoHandshake completed95 ms

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

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