Srdcheck vs MCP Stockfish — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Srdcheck vs MCP Stockfish
In-depth architectural comparison of the Srdcheck and MCP Stockfish 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
Srdcheck
Gaming · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
MCP Stockfish
Gaming · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Srdcheck if you need specialized Gaming tools running via a local process. Choose MCP Stockfish 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 Srdcheck 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).
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 server connecting AI systems to Stockfish chess engine.
Srdcheck is categorized under Gaming and uses a local stdio subprocess. In contrast, MCP Stockfish belongs to Gaming using local stdio subprocess. Select Srdcheck when you need capabilities focused on gaming and MCP Stockfish when you require tools for gaming.