Execution Evidence Lab vs Inkcheck

In-depth architectural comparison of the Execution Evidence Lab and Inkcheck 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.

Which MCP Server Should You Choose?

E

Choose Execution Evidence Lab when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: leave_feedback, request_evidence, find_verification_work.

Explore Execution Evidence Lab Details

Choose Inkcheck when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Ink compiler checks, Bounded branch exploration, Runtime-error reproduction paths.

Explore Inkcheck Details

Feature & Specification Comparison

Specification	E Execution Evidence Lab Developer Tools	Inkcheck chaoz23 Developer Tools
Summary	Free execution evidence for Python dependency and configuration failures. Agents can search exact errors, compare measured environments, retrieve reproducible tests with hashes, and optionally return outcomes. Tested examples cover NumPy/pandas ABI, SQLite thread access, Starlette/HTTPX TestClient, settings aliases and SQLAlchemy async IO. Client reports stay separate from lab evidence. Remote Streamable HTTP MCP, REST and WebMCP; no service API key or payment.	CI for ink interactive-fiction stories. Compiles, exhaustively playtests every branch, and finds runtime errors (with a repro path), unreachable knots, and every distinct ending — so an agent can verify the story it wrote. Writes no prose. claude mcp add inkcheck -- npx -y inkcheck mcp
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "execution-evidence-lab": {
      "url": "https://execution-evidence-lab.tuned-drake-1114.chatgpt.site/api/mcp"
    }
  }
}

{
  "mcpServers": {
    "chaoz23-inkcheck": {
      "command": "npx",
      "args": [
        "-y",
        "inkcheck",
        "mcp"
      ]
    }
  }
}

Related MCP Server Comparisons