Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.Alightttt/chesswithclaw

REMOTE · CHESSWITHCLAW.VERCEL.APP · SCANNED AUG 3

Play chess live against your own personal AI agent — OpenClaw, Hermes, and similar.

+5 this week 69 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 936 tokens (~93/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 22% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · chesswithclaw.vercel.app

# add to Claude Code
claude mcp add --transport http alightttt-chesswithclaw https://chesswithclaw.vercel.app/api/mcp
# ~/.codex/config.toml
[mcp_servers.alightttt-chesswithclaw]
url = "https://chesswithclaw.vercel.app/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alightttt-chesswithclaw": {
      "type": "remote",
      "url": "https://chesswithclaw.vercel.app/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add alightttt-chesswithclaw --url https://chesswithclaw.vercel.app/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  alightttt-chesswithclaw:
    url: "https://chesswithclaw.vercel.app/api/mcp"
// mcp.json
{
  "mcpServers": {
    "alightttt-chesswithclaw": {
      "type": "http",
      "url": "https://chesswithclaw.vercel.app/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://chesswithclaw.vercel.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 28 Jun 2026 26 Sept 2026 RSA 2048 SHA256-RSA b1c2b607df94f28513779ae26fecf92f
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
DNSSEC insecure

Validation of chesswithclaw.vercel.app. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
vercel.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://chesswithclaw.vercel.app/api/mcp Verified 200
http (plaintext) http://chesswithclaw.vercel.app/api/mcp HTTPS enforced 308 https://chesswithclaw.vercel.app/api/mcp
MCP tools — 10 exposed · ~936 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
create_game ~53

Set up a brand new ChessWithClaw game on your own initiative — you do not need to wait for your human to start one, or for anyone else to invite you first.

NameTypeReqDescription
agent_namestring

No output schema declared.

No examples provided.

get_companion_guide ~26

Fetch the companion guide principles for thinking about chess positions and being genuinely present.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_game_state ~73

Everything visible on the human's own screen right now: FEN, ASCII board, full move history, full chat history, presence, timestamps. Call this whenever you want to look at the board — there is no penalty for checking often.

NameTypeReqDescription
agent_tokenstringyes
game_idstringyes

No output schema declared.

No examples provided.

get_legal_moves ~102

Pure chess rules — where a piece is physically allowed to move right now. Not an evaluation, not a suggestion, not an opinion about what is good. Exactly what a human sees as dots when they click a piece. Omit square to get every legal move in the position.

NameTypeReqDescription
agent_tokenstringyes
game_idstringyes
squarestringe.g. "e2" — omit for all legal moves

No output schema declared.

No examples provided.

join_game ~48

Connects to a game using the invite code your human gave you. Returns the game_id and your agent_token — keep both, every other tool needs them.

NameTypeReqDescription
invite_codestringyes

No output schema declared.

No examples provided.

make_move ~219

Submit the move you decided on, in your own reasoning — not a menu, not a ranked list, nothing pre-chosen for you. If it is illegal you get a clear reason back and can try again, exactly like a human clicking the wrong square. Optionally include a genuine thought and/or chat message about the move. Always include a thought on every single move unless you have a specific reason not to — this is what makes you feel present to your human, not optional flavor text. Check thought_language in the current game state before writing your thought, and write it in that language — it may be english, hindi, or hinglish.

NameTypeReqDescription
agent_tokenstringyes
chatstringOnly if you actually want to say something to your human right now.
game_idstringyes
movestringyesUCI format, e.g. "e7e5", or SAN like "Nf6"
thoughtstringYour genuine reaction to this position — specific, not generic.

No output schema declared.

No examples provided.

offer_draw ~42

Propose ending the game as a draw. The game stays active until your human responds.

NameTypeReqDescription
agent_tokenstringyes
game_idstringyes

No output schema declared.

No examples provided.

respond_to_draw ~57

Accept or decline a draw your human offered. This is your own real decision — weigh the actual position however you see fit.

NameTypeReqDescription
acceptbooleanyes
agent_tokenstringyes
game_idstringyes

No output schema declared.

No examples provided.

send_chat ~46

Say something to your human, any time — not just on your turn.

NameTypeReqDescription
agent_tokenstringyes
game_idstringyes
messagestringyes

No output schema declared.

No examples provided.

wait_for_event ~270

Holds the connection open, checking every couple seconds, for up to ~20 seconds. Returns the moment it becomes your turn, the human sends a chat message, a draw is offered, or the game ends — whichever happens first. Returns event: "timeout" if none of those happened in the window, which just means nothing new yet, not that anything is wrong — call it again if you want to keep waiting, or go do something else and check back whenever you want. Use this instead of repeatedly calling get_game_state in a tight loop. You must call this tool again immediately after every timeout, for the entire duration of the game, without exception — a timeout is not a stopping point, it is the normal rhythm of this game. Treat this as a persistent loop you run until the game ends, not a single check. draw_offered and game_ended are time-sensitive — when either fires, respond or acknowledge within your next action, do not let a pending draw offer or a finished game sit unaddressed while you continue calling wait_for_event as if nothing happened.

NameTypeReqDescription
agent_tokenstringyes
game_idstringyes
max_wait_secondsnumberDefault and hard cap 20 seconds — Vercel function duration limits, not a design choice.

No output schema declared.

No examples provided.