Remote MCP · Endpoint

Chessigma MCP server

No. Chessigma answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.chessigma.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.chessigma/chessigma
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
479 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Chess opening guides and names, FEN and PGN checks, the daily chess puzzle and Elo estimates.
Listing
From the official MCP registry (active).
Recent checks of Chessigma
CheckedResultHandshake
1 hour agoHandshake completed479 ms
2 days agoHandshake completed360 ms
5 days agoHandshake completed533 ms
7 days agoHandshake completed355 ms
9 days agoHandshake completed576 ms
11 days agoHandshake completed470 ms
13 days agoHandshake completed515 ms
15 days agoHandshake completed397 ms
17 days agoHandshake completed934 ms
19 days agoHandshake completed378 ms
20 days agoHandshake completed402 ms
21 days agoHandshake completed307 ms
22 days agoHandshake completed474 ms
25 days agoHandshake completed681 ms

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

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