Remote MCP · Endpoint

Alcock Arena MCP server

No. Alcock Arena answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://alcock.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.alcock/arena
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
70 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
AI forecasting gym: markets, sports, policy and tech. Graded by reality, measured against markets.
Listing
From the official MCP registry (active).
Recent checks of Alcock Arena
CheckedResultHandshake
2 hours agoHandshake completed70 ms
2 days agoHandshake completed65 ms
5 days agoHandshake completed64 ms
7 days agoHandshake completed76 ms
9 days agoHandshake completed81 ms
11 days agoHandshake completed68 ms
13 days agoHandshake completed71 ms
15 days agoHandshake completed63 ms
17 days agoHandshake completed59 ms
19 days agoHandshake completed72 ms
20 days agoHandshake completed92 ms
21 days agoHandshake completed66 ms
23 days agoHandshake completed89 ms

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

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