# Lichess (npm · @pipeworx/mcp-lichess)

Lichess MCP — public read-only API for users, games, explorer, tablebase.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 84/100, [markdown](https://verifymcp.io/servers/pipeworx-io-lichess/lichess-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-lichess/lichess-mcp)
- npm · `@pipeworx/mcp-lichess`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-lichess/pipeworx-mcp-lichess.md), [page](https://verifymcp.io/servers/pipeworx-io-lichess/pipeworx-mcp-lichess)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-lichess`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-lichess).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 790 tokens (~79/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 74% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 11 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 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.

### Claude

```bash
claude mcp add pipeworx-io-lichess -- npx -y @pipeworx/mcp-lichess
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-lichess": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-lichess"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-lichess": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-lichess"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-lichess -- npx -y @pipeworx/mcp-lichess
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-lichess": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-lichess"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-lichess --command npx --arg -y --arg @pipeworx/mcp-lichess
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-lichess:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-lichess"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-lichess": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-lichess"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-lichess -t stdio -c npx -a -y @pipeworx/mcp-lichess
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-lichess": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-lichess"
      ]
    }
  }
}
```

## 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-05 (score 82, +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.

### 2026-11-03 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 66, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (10)

### `user` (~48 tokens)

Fetch a Lichess player's public profile by username, including ratings across all variants (bullet, blitz, rapid, classical, chess960, etc.) and account metadata.

Input parameters:

- `username` (string, required)

### `users` (~30 tokens)

Bulk lookup of up to 300 users by username.

Input parameters:

- `usernames` (array, required): 1-300 usernames.

### `user_status` (~29 tokens)

Online / playing status for the given usernames (up to 100).

Input parameters:

- `usernames` (array, required)

### `user_performance` (~73 tokens)

Single-variant performance + best rated game for a user.

Input parameters:

- `perf` (string, required): bullet | blitz | rapid | classical | correspondence | chess960 | crazyhouse | antichess | atomic | horde | kingOfTheHill | racingKings | threeCheck | ultraBullet
- `username` (string, required)

### `top_players` (~127 tokens)

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.

Input parameters:

- `limit` (number): 1-200 (default 50)
- `perf` (string, required)

### `leaderboards` (~44 tokens)

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).

### `tv_channels` (~16 tokens)

Currently-featured TV games per variant.

### `cloud_eval` (~48 tokens)

Stockfish cloud evaluation for a FEN position.

Input parameters:

- `fen` (string, required): FEN of position to evaluate.
- `multi_pv` (number): 1-5 (default 1)

### `tablebase` (~52 tokens)

Syzygy tablebase lookup (≤7 pieces). Variant: standard (default), atomic, antichess.

Input parameters:

- `fen` (string, required)
- `variant` (string): standard | atomic | antichess

### `opening_explorer` (~270 tokens)

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.

Input parameters:

- `_apiKey` (string, required): 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, required): lichess | masters | player
- `speeds` (string): Comma-sep: ultraBullet,bullet,blitz,rapid,classical,correspondence

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-lichess/pipeworx-mcp-lichess#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 66
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-lichess
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-lichess
- Repository: https://github.com/pipeworx-io/mcp-lichess
- Website: https://pipeworx.io/packs/lichess
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-lichess/pipeworx-mcp-lichess.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-lichess/pipeworx-mcp-lichess.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-lichess/pipeworx-mcp-lichess