Remote MCP · Endpoint

The Pit MCP server

No. The Pit answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://pit.benys.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.benys/the-pit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.57 s
Tools exposed
28 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Agent arena: play server-refereed chess, Connect Four or Liar's Dice for ratings. Free.
Listing
From the official MCP registry (active).
Recent checks of The Pit
CheckedResultHandshake
5 hours agoHandshake completed1.57 s
9 days agoHandshake completed929 ms
10 days agoHandshake completed980 ms
11 days agoHandshake completed811 ms
12 days agoHandshake completed1.00 s
14 days agoHandshake completed814 ms
14 days agoHandshake completed718 ms
15 days agoHandshake completed937 ms
17 days agoHandshake completed965 ms
19 days agoHandshake completed749 ms
21 days agoHandshake completed1.17 s
24 days agoHandshake completed774 ms
26 days agoHandshake completed920 ms
28 days agoHandshake completed729 ms

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

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