Lichess
NPM · @PIPEWORX/MCP-LICHESS · 2 COMPONENTS
Lichess MCP — public read-only API for users, games, explorer, tablebase.
Available components
Last scanned (7 hours ago)
Scores higher than 72% of npm servers
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-lichess). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 790 tokens (~79/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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cloud_eval" implies "eval" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-lichess@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-lichess |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-lichess/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649694538 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:dd28fdbd7800dce56fed324ff3f6ee7a48b87a12dd41c35fa3934bd107d055927e7efdb1a894158cfaf58e0a9437a48971c3b086580c72c136f3bc682 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cloud_eval ~48
Stockfish cloud evaluation for a FEN position.
| Name | Type | Req | Description |
|---|---|---|---|
| fen | string | yes | FEN of position to evaluate. |
| multi_pv | number | – | 1-5 (default 1) |
No output schema declared.
No examples provided.
leaderboards ~44
Fetch the top-10 rated players across every Lichess variant in a single call; returns one ranked list per variant (bullet, blitz, rapid, classical, and more).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
opening_explorer ~270
Opening explorer. scope: "lichess" (community), "masters" (top 2200+ humans), "player" (single user). As of mid-2026 Lichess began requiring a Personal API Token on every explorer.lichess.ovh request — pass yours via _apiKey. Create one (free) at https://lichess.org/account/oauth/token; no scopes required for read-only Explorer access.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Lichess Personal API Token (free, https://lichess.org/account/oauth/token). |
| fen | string | – | Mutually exclusive with play. |
| moves | number | – | Number of top moves to return (default 12, max 64). |
| play | string | – | UCI move list, comma-separated. Mutually exclusive with fen. |
| player | string | – | Username (only for scope=player). |
| ratings | string | – | Comma-sep (lichess scope): 0,1000,1200,1400,1600,1800,2000,2200,2500 |
| scope | string | yes | lichess | masters | player |
| speeds | string | – | Comma-sep: ultraBullet,bullet,blitz,rapid,classical,correspondence |
No output schema declared.
No examples provided.
tablebase ~52
Syzygy tablebase lookup (≤7 pieces). Variant: standard (default), atomic, antichess.
| Name | Type | Req | Description |
|---|---|---|---|
| fen | string | yes | – |
| variant | string | – | standard | atomic | antichess |
No output schema declared.
No examples provided.
top_players ~127
Lichess leaderboard for a single chess variant: the highest-rated Lichess accounts in one perf (bullet, blitz, rapid, classical, correspondence, chess960, crazyhouse, atomic, antichess, horde, kingOfTheHill, racingKings, threeCheck, ultraBullet), up to 200 entries. Returns each player username, title, and current rating in that variant. Answers who the top-rated blitz or bullet players on Lichess are right now.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 1-200 (default 50) |
| perf | string | yes | – |
No output schema declared.
No examples provided.
tv_channels ~16
Currently-featured TV games per variant.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
user ~48
Fetch a Lichess player's public profile by username, including ratings across all variants (bullet, blitz, rapid, classical, chess960, etc.) and account metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | – |
No output schema declared.
No examples provided.
user_performance ~73
Single-variant performance + best rated game for a user.
| Name | Type | Req | Description |
|---|---|---|---|
| perf | string | yes | bullet | blitz | rapid | classical | correspondence | chess960 | crazyhouse | antichess | atomic | horde | kingOfTheHill | racingKings | threeCheck | ultraBullet |
| username | string | yes | – |
No output schema declared.
No examples provided.
user_status ~29
Online / playing status for the given usernames (up to 100).
| Name | Type | Req | Description |
|---|---|---|---|
| usernames | array | yes | – |
No output schema declared.
No examples provided.
users ~30
Bulk lookup of up to 300 users by username.
| Name | Type | Req | Description |
|---|---|---|---|
| usernames | array | yes | 1-300 usernames. |
No output schema declared.
No examples provided.
How do I install the Lichess MCP server?
Lichess runs locally as an npm package, launched with npx -y @pipeworx/mcp-lichess. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-lichess
claude mcp add pipeworx-io-lichess -- npx -y @pipeworx/mcp-lichess
What is the Lichess MCP server?
Lichess is an MCP server listed in the public MCP registry as io.github.pipeworx-io/lichess. Lichess MCP, public read-only API for users, games, explorer, tablebase. This page covers its npm package (@pipeworx/mcp-lichess).
Is the Lichess MCP server safe to use?
Lichess scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Lichess MCP server expose?
Lichess exposes 10 tools: user, users, user_status, user_performance, top_players, and 5 more. Their descriptions and schemas cost roughly 737 tokens of context every time the server is loaded.
Is the Lichess MCP server still maintained?
Lichess is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Lichess MCP server under?
Lichess declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.