Club Ladder MCP server
io.github.whosman/chessclubladderwhosmanstreamable-httpv1.0.0Scanned
Public chess club ladders, a Lichess and chess.com rating converter, and Lichess clubs by rating.
4 tools: 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Club Ladder MCP server can do
The Club Ladder MCP server is published by the GitHub account whosman. It has 4 tools. It can create or change data (1 tool: estimate_rating), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
estimate_ratingEstimate the other site's rating for one rating, from people who play on both.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Estimate the other site's rating for one rating, from people who play on both. Give lichess or chesscom (one of them) and a time control. Returns the estimate and the range most people fall in.
Annotations the server declares
- title: Convert a Lichess or chess.com rating
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
find_lichess_clubsUp to ten open Lichess clubs (teams) where the given rating sits in the middle half of the members' blitz or rapid ratings, largest first, with member counts, medians and how many …No findings
Why it is in this group
- The name "find_lichess_clubs" says "find": a word for reading.
Description, as the server wrote it Up to ten open Lichess clubs (teams) where the given rating sits in the middle half of the members' blitz or rapid ratings, largest first, with member counts, medians and how many were active in 30 days.
Annotations the server declares
- title: Find Lichess clubs at a rating
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_public_ladderStandings and recent results for one public ladder by id.No findings
Why it is in this group
- The name "get_public_ladder" says "get": a word for reading.
Description, as the server wrote it Standings and recent results for one public ladder by id. period is 7 or 30 days.
Annotations the server declares
- title: Get a public ladder
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_public_laddersLadders whose organizers chose to list them: name, id and player count.No findings
Why it is in this group
- The name "list_public_ladders" says "list": a word for reading.
Description, as the server wrote it Ladders whose organizers chose to list them: name, id and player count.
Annotations the server declares
- title: List public ladders
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:20 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://chessclubladder.com/api/mcp: tools/list returned 6 tools to an anonymous client, including start_club_ladder (write), estimate_rating (write), rating_percentile (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http chessclubladder https://chessclubladder.com/api/mcpclaude mcp add --transport http chessclubladder https://chessclubladder.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__chessclubladder__list_public_ladders",
"mcp__chessclubladder__get_public_ladder",
"mcp__chessclubladder__find_lichess_clubs"
],
"ask": [
"mcp__chessclubladder__estimate_rating"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as chessclubladder. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.whosman/chessclubladder/verify?hash=1e220c529635d259144a901fd954a3ee5d06af37af4f4fa9507b39b59d3ec97f" | jq -e '.changed == false'Pinned hash 1e220c529635, from Nov 20, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.whosman/chessclubladder/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.whosman/chessclubladder)Source: MCP Registry · repository. Synced Nov 20, 2026, 07:18 UTC.
Club Ladder MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Club Ladder MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Club Ladder MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Club Ladder MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Club Ladder MCP server have?
- 4 tools: 1 write, 3 read. estimate_rating, list_public_ladders, get_public_ladder and find_lichess_clubs.
Does the Club Ladder MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Club Ladder MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Club Ladder MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.