MCP Stockfish vs Srdcheck — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Stockfish vs Srdcheck
In-depth architectural comparison of the MCP Stockfish and Srdcheck MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Stockfish
Gaming · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Srdcheck
Gaming · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Stockfish if you need specialized Gaming tools running via a local process. Choose Srdcheck if your workspace requires Gaming integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Stockfish when:
You need dedicated capabilities in the Gaming domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
MCP server connecting AI systems to Stockfish chess engine.
Deterministic D&D 5e (SRD 5.2.1) rules verdicts for agents: cited legality checks for whole turns, legal-action enumeration, advantage math, and hash-stamped game-state lineage. Refuses what the rules don't decide (exit 2), quotes the rule text on every verdict, zero dependencies.
MCP Stockfish is categorized under Gaming and uses a local stdio subprocess. In contrast, Srdcheck belongs to Gaming using local stdio subprocess. Select MCP Stockfish when you need capabilities focused on gaming and Srdcheck when you require tools for gaming.