Remote MCP · Endpoint

Council of AI GSPC MCP server

No. Council of AI GSPC answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://councilof.ai/mcp/

The last check completed an MCP handshake.

Registry name
ai.councilof/gspc
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
604 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
19 tools (14 free, 5 x402-metered): GSPC board, evidence, Ed25519 card verify. Measurement only.
Listing
From the official MCP registry (active).
Recent checks of Council of AI GSPC
CheckedResultHandshake
1 hour agoHandshake completed604 ms
1 day agoHandshake completed156 ms
3 days agoHandshake completed429 ms
6 days agoHandshake completed552 ms
7 days agoHandshake completed401 ms
9 days agoHandshake completed596 ms
10 days agoHandshake completed140 ms
11 days agoHandshake completed453 ms
13 days agoHandshake completed416 ms
15 days agoHandshake completed120 ms
17 days agoHandshake completed163 ms
19 days agoHandshake completed965 ms
20 days agoHandshake completed82 ms
21 days agoHandshake completed88 ms
22 days agoHandshake completed382 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 Council of AI GSPC and makes no claim about it beyond what these checks measured.