Chess DNA
REMOTE · MHMWMGESYGUAPHNIIEDP.SUPABASE.CO
Chess ratings explained, an Elo calculator, and any Chess.com or Lichess player's recent games.
Available components
Last scanned (5 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Entertainment and Games
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 309 tokens (~103/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 72
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 6 Nov 2026 · Probed https://mhmwmgesyguaphniiedp.supabase.co/functions/v1/chess-dna-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d2b50611cd88e9c50e4e2231f4d3f059 |
| SANs: supabase.co, *.supabase.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mhmwmgesyguaphniiedp.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| supabase.co. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mhmwmgesyguaphniiedp.supabase.co/functions/v1/chess-dna-mcp | Verified | 200 | |
| http (plaintext) | http://mhmwmgesyguaphniiedp.supabase.co/functions/v1/chess-dna-mcp | HTTPS enforced | 301 | https://mhmwmgesyguaphniiedp.supabase.co/functions/v1/chess-dna-mcp |
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 →
elo_change Elo rating change calculator ~94
Calculates how many rating points a player wins or loses for a win, draw and loss against an opponent, using the Elo formula. Also returns the expected score.
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | K-factor (default 20; FIDE uses 40 for new players, 20 normally, 10 above 2400) |
| opponent | integer | yes | The opponent's rating |
| rating | integer | yes | The player's rating |
No output schema declared.
No examples provided.
rating_meaning What does a chess rating mean? ~81
Explains what a chess rating (Elo, Chess.com or Lichess) means: whether it is good, where it sits among online players, and a link to the full guide for that level. Use for questions like "is 1200 a good chess rating?"
| Name | Type | Req | Description |
|---|---|---|---|
| rating | integer | yes | The rating, e.g. 1200 |
No output schema declared.
No examples provided.
recent_games A player's recent games ~98
Summarizes a player's recent public games on Chess.com or Lichess: wins, draws and losses, rating trend, results by colour, and most played openings. Links to a free Chess DNA analysis of the player's strengths and weaknesses.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many recent games (default 30) |
| site | string | – | Which site (default chesscom) |
| username | string | yes | Chess.com or Lichess username |
No output schema declared.
No examples provided.
How do I install the Chess DNA MCP server?
Chess DNA is a hosted endpoint at https://mhmwmgesyguaphniiedp.supabase.co/functions/v1/chess-dna-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.
remote · mhmwmgesyguaphniiedp.supabase.co
claude mcp add --transport http app-chessdna-chess-dna 'https://mhmwmgesyguaphniiedp.supabase.co/functions/v1/chess-dna-mcp'
What is the Chess DNA MCP server?
Chess DNA is an MCP server listed in the public MCP registry as app.chessdna/chess-dna. Chess ratings explained, an Elo calculator, and any Chess.com or Lichess player's recent games. This page covers its hosted endpoint (https://mhmwmgesyguaphniiedp.supabase.co/functions/v1/chess-dna-mcp).
Is the Chess DNA MCP server safe to use?
Chess DNA scores 72 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 Chess DNA MCP server expose?
Chess DNA exposes 3 tools: rating_meaning, elo_change, recent_games. Their descriptions and schemas cost roughly 273 tokens of context every time the server is loaded.
Does the Chess DNA MCP server require authentication?
No. We connected to Chess DNA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Chess DNA MCP server still maintained?
Chess DNA is still listed as active in the MCP registry. We last reached this channel on 6 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 Chess DNA MCP server?
VerifyMCP ran 13 checks on Chess DNA, 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.