Skip to main content
Glama

Lichess

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

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

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
30.3% over 40 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-lichess
GitHub Stars
0
Server Listing
mcp-lichess

TDQS

B3.3/5.0

Scored across 41 tools

Disambiguation3/5

Descriptions are unusually detailed and often explicitly route between tools, but there are dense overlapping clusters: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all answer routed questions, and bet_research / polymarket_arbitrage / polymarket_edges / polymarket_edge_tracker / polymarket_fill_risk / polymarket_kalshi_spread all cover prediction-market analysis. The text mostly disambiguates them, but the beta tool admitting it currently matches the stable one is a clear boundary failure.

Naming Consistency3/5

Consistently snake_case and no camelCase contamination, which helps. However the pattern is mixed: some tools are verb_noun (compare_entities, validate_claim, resolve_entity, recent_alerts), others are bare nouns (leaderboards, user, users, tv_channels, tablebase, cloud_eval), so there is no single predictable convention.

Tool Count2/5

41 tools is well above the heavy threshold, and the set is a domain mismatch — a server named Lichess whose surface is dominated by Pipeworx data-gateway and Polymarket tooling, with only ~10 actual chess tools. The volume suggests two unrelated servers bundled together rather than one well-scoped surface.

Completeness2/5

Judged against the stated Lichess/chess domain, the surface is notably incomplete: there is no way to fetch a user's games, puzzles, studies, or opening repertoire, and no game/challenge lifecycle beyond TV and tablebase lookups. The generic Pipeworx meta-tooling is broad, but it does not fill the chess gaps the server name implies.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
  3. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."

Related MCP Connectors

Related MCP Servers

  • chess ceo

    chessceo
    A
    license
    A
    quality
    B
    maintenance
    MCP server for chess.ceo — 11.7M+ games, ~1.5M FIDE player profiles, per-player opening preparation, position statistics, head-to-head, live tournament broadcasts. No API key.
    10
    305 npm
    MIT

  • lichess-mcp

    Anay704
    A
    license
    A
    quality
    C
    maintenance
    MCP server that exposes the Lichess public API through tools for querying player profiles, games, analysis, openings, puzzles, and tournaments, allowing natural-language chess questions without an API key.
    8
    MIT

  • chesscom-mcp

    rrrmaster
    A
    license
    B
    quality
    B
    maintenance
    MCP server for Chess.com's API, providing access to player profiles, stats, games, clubs, tournaments, and puzzles. It serializes requests to reduce rate limit errors and includes an unofficial tool for retrieving game data by ID.
    29
    4 npm
    MIT

  • Lichess MCP

    karayaman
    A
    license
    C
    quality
    C
    maintenance
    An MCP server that enables natural language interaction with the Lichess chess platform, allowing users to play games, analyze positions, manage their account, and participate in tournaments through Claude.
    90
    58 npm
    18
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources