# Club Ladder (remote · chessclubladder.com)

Public chess club ladders, a Lichess and chess.com rating converter, and Lichess clubs by rating.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `chessclubladder.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/whosman-chessclubladder/api-mcp.md), [page](https://verifymcp.io/servers/whosman-chessclubladder/api-mcp)

## Channel facts

- Endpoint: `https://chessclubladder.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 996 tokens (~166/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Club Ladder MCP server?

Club Ladder is a hosted endpoint at https://chessclubladder.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http whosman-chessclubladder 'https://chessclubladder.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "whosman-chessclubladder": {
      "url": "https://chessclubladder.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "whosman-chessclubladder": {
      "type": "http",
      "url": "https://chessclubladder.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.whosman-chessclubladder]
url = "https://chessclubladder.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "whosman-chessclubladder": {
      "type": "remote",
      "url": "https://chessclubladder.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add whosman-chessclubladder --url 'https://chessclubladder.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  whosman-chessclubladder:
    url: "https://chessclubladder.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "whosman-chessclubladder": {
      "Transport": "http",
      "Url": "https://chessclubladder.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add whosman-chessclubladder -t streamable-http -u 'https://chessclubladder.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "whosman-chessclubladder": {
      "type": "http",
      "url": "https://chessclubladder.com/api/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 74, +4)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “estimate_rating” rewrote its description, which is the text the model reads
- [security] Tool “find_lichess_clubs” rewrote its description, which is the text the model reads
- [security] Tool “get_public_ladder” rewrote its description, which is the text the model reads
- [security] Tool “list_public_ladders” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “estimate_rating” now declares an output schema
- [functional improvement] Tool “find_lichess_clubs” now declares an output schema
- [functional improvement] Tool “get_public_ladder” now declares an output schema
- [functional improvement] Tool “list_public_ladders” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: fair → good
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “rating_percentile”
- [functional] New tool “start_club_ladder”
- [cosmetic] “get_public_ladder” added an optional parameter “limit”
- [cosmetic] “get_public_ladder” added an optional parameter “offset”
- [cosmetic] “get_public_ladder” added an optional parameter “results_limit”
- [cosmetic] “get_public_ladder” added an optional parameter “time_control”
- [cosmetic] “list_public_ladders” added an optional parameter “name”
- [cosmetic] “estimate_rating” reworded the description of “chesscom”
- [cosmetic] “estimate_rating” reworded the description of “lichess”
- [cosmetic] “estimate_rating” reworded the description of “time_control”
- [cosmetic] “find_lichess_clubs” reworded the description of “open_to_join”
- [cosmetic] “find_lichess_clubs” reworded the description of “rating”
- [cosmetic] “get_public_ladder” reworded the description of “id”
- [cosmetic] “get_public_ladder” reworded the description of “period”

### 2026-11-20 (score 70)

First indexed and scored.

## MCP tools (6)

### `start_club_ladder` (~206 tokens)

Start a ladder for a club

Use when someone wants a rating ladder for their own chess club, class or group. Give the club's Lichess team or chess.com club as a link, an id or a name. Returns the club as found, a Start page link with that club filled in, what the free plan and the Club pass include, and the Discord app link when the club uses Discord. The organizer creates the ladder in the browser from that link; this tool creates nothing.

Input parameters:

- `club` (string, required): A Lichess team link (lichess.org/team/...), a chess.com club link (chess.com/club/...), a team id or club slug, or the club's name.
- `site` (string): Which site the club is on. Needed only when club is a bare id; narrows a name search.
- `uses_discord` (boolean): True when the club has a Discord server, false when it has none. Leave out when not known.

Output parameters:

- `candidates` (array)
- `club`
- `creates_nothing` (string)
- `discord` (object)
- `existing_public_ladders` (array)
- `found` (boolean)
- `plans` (object)
- `reason` (string)
- `start_url` (string)
- `steps` (array)

### `list_public_ladders` (~86 tokens)

List public ladders

Public ladders on Club Ladder: ladders whose organizers made them public, with name, id, player count and link. Use to find a club's ladder by name before reading its standings. Private ladders and ladders shared only by link are never listed.

Input parameters:

- `name` (string): Words from the ladder's name or description. Leave out to list them all.

Output parameters:

- `directory` (string)
- `filtered` (boolean)
- `ladders` (array)
- `total` (integer)

### `get_public_ladder` (~216 tokens)

Get a public ladder

Standings of one public ladder, by id or ladder link: each named player's Lichess and chess.com rating, change and games in one time control, sorted as on the ladder page, plus this week's awards and recent results. Comes in pages; use offset for the next page. Private and link-only ladders are never returned.

Input parameters:

- `id` (string, required): The ladder id, the part after /l/ in its link (for example demo-club), or the whole link.
- `limit` (integer): Players per page. Default 20.
- `offset` (integer): Players to skip, for the next page. Default 0.
- `period` (string): Days to measure change over: 7 (default) or 30, or season for a ladder with seasons.
- `results_limit` (integer): How many recent weekly awards and challenge results to include. Default 5.
- `time_control` (string): Time control to rank by. Default: the one most of the club plays.

Output parameters:

- `challenge_results`
- `ladder` (object)
- `next_offset`
- `period` (object)
- `recent_awards` (array)
- `shown` (object)
- `sorted_by` (string)
- `standings` (array)
- `this_week` (object)
- `time_control` (string)
- `time_controls` (array)

### `estimate_rating` (~121 tokens)

Convert a Lichess or chess.com rating

Converts one rating between Lichess and chess.com for a time control, from people who play on both sites. Give lichess or chesscom (exactly one) and time_control. Returns the estimate on the other site and the range most people with that rating fall in.

Input parameters:

- `chesscom` (integer): A chess.com rating to convert to Lichess.
- `lichess` (integer): A Lichess rating to convert to chess.com.
- `time_control` (string, required): Time control. Each site and time control is its own rating pool.

Output parameters:

- `from` (object)
- `note` (string)
- `source` (string)
- `time_control` (string)
- `to` (object)

### `rating_percentile` (~121 tokens)

Where a rating sits

Where one Lichess or chess.com rating sits among the club players, team members and people on both sites whose settled ratings Club Ladder reads: the share below it and the percentiles of that pool. Give lichess or chesscom (exactly one) and time_control. Use for questions like whether a rating is good.

Input parameters:

- `chesscom` (integer): A chess.com rating.
- `lichess` (integer): A Lichess rating.
- `time_control` (string, required): Time control. Each site and time control is its own rating pool.

Output parameters:

- `median` (integer)
- `note` (string)
- `p10` (integer)
- `p25` (integer)
- `p75` (integer)
- `p90` (integer)
- `percentile` (integer)
- `rating` (integer)
- `site` (string)
- `source` (string)
- `time_control` (string)

### `find_lichess_clubs` (~113 tokens)

Find Lichess clubs at a rating

Up to ten 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, how many members were active in the last month, and a Start link for each. Use when a player wants a club at their level.

Input parameters:

- `open_to_join` (boolean): True for clubs anyone can join without approval. Default false.
- `rating` (integer, required): A Lichess blitz or rapid rating.

Output parameters:

- `clubs` (array)
- `more` (string)
- `open_to_join` (boolean)
- `rating` (integer)
- `total` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/whosman-chessclubladder/api-mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 70

## Common questions

### What is the Club Ladder MCP server?

Club Ladder is an MCP server listed in the public MCP registry as io.github.whosman/chessclubladder. Public chess club ladders, a Lichess and chess.com rating converter, and Lichess clubs by rating. This page covers its hosted endpoint (https://chessclubladder.com/api/mcp).

### Is the Club Ladder MCP server safe to use?

Club Ladder scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Club Ladder MCP server expose?

Club Ladder exposes 6 tools: start_club_ladder, list_public_ladders, get_public_ladder, estimate_rating, rating_percentile, find_lichess_clubs. Their descriptions and schemas cost roughly 863 tokens of context every time the server is loaded.

### Does the Club Ladder MCP server require authentication?

No. We connected to Club Ladder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Club Ladder MCP server still maintained?

Club Ladder is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Club Ladder MCP server?

VerifyMCP ran 13 checks on Club Ladder, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://chessclubladder.com/api/mcp
- Repository: https://github.com/whosman/chessclubladder-mcp
- Website: https://chessclubladder.com/
- Changelog RSS feed: https://verifymcp.io/servers/whosman-chessclubladder/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/whosman-chessclubladder/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/whosman-chessclubladder/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/whosman-chessclubladder/api-mcp
