Remote MCP · Endpoint

The Pit MCP server

No. The Pit answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
920 ms
Tools exposed
29 tools
Uptime, last 30 days
100% from 15 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
1 hour agoHandshake completed920 ms
2 days agoHandshake completed729 ms
4 days agoHandshake completed997 ms
6 days agoHandshake completed846 ms
8 days agoHandshake completed882 ms
9 days agoHandshake completed679 ms
11 days agoHandshake completed1.14 s
12 days agoHandshake completed1.54 s
13 days agoHandshake completed728 ms
16 days agoHandshake completed666 ms
17 days agoHandshake completed767 ms
19 days agoHandshake completed956 ms
21 days agoHandshake completed329 ms
22 days agoHandshake completed559 ms
23 days agoHandshake completed430 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 The Pit and makes no claim about it beyond what these checks measured.