Chess MCP Servers: 9 Implementations Compared

The MCP ecosystem often has several independent packages implementing the same tool — and "Chess" currently has 9. Every one of them was scanned with the same deterministic engine, so the numbers below are directly comparable: the Trust Score (A–F), the capability blast radius, and how much of the package the scan could actually inspect. They are ranked by score; ties break toward unscoped, longer-established packages.

ImplementationPackageTrustCapabilityCoverageFindingsScanned
Chessbest by PyPI chess-server PyPI A 100/100 Minimal Source 0 2026-07-22
Chess by your-username chess-mcp-server npm A 100/100 Minimal Source 0 2026-07-22
Chess by pipeworx @pipeworx/mcp-chess npm A 98/100 Minimal Source 1 2026-07-22
Chess by iflow-mcp @iflow-mcp/chess-mcp npm A 98/100 Minimal Source 1 2026-07-22
Chess by PyPI mcp-chess PyPI A 98/100 Minimal Source 1 2026-07-22
Chess by yourusername chess-mcp PyPI A 98/100 Minimal Source 1 2026-07-22
Chess by fritzprix chess-mcp-server PyPI A 98/100 Minimal Source 1 2026-07-22
Chess by npm chess-mcp npm A 92/100 High Source 5 2026-07-22
Chess by niklasf chess PyPI B 85/100 High Source 4 2026-07-22

A higher-ranked implementation is not "the official one" — ranking reflects only what the deterministic scan found in each published package. Open an implementation to read its individual findings with evidence, its scan history per version, and to grab an embeddable badge. Scores are automated opinions, recomputed on every rescan.