RiskState — Crypto Risk Engine vs Docfork MCP

In-depth architectural comparison of the RiskState — Crypto Risk Engine and Docfork MCP 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?

Choose RiskState — Crypto Risk Engine when:

• You need dedicated capabilities in the Version Control domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore RiskState — Crypto Risk Engine Details

Choose Docfork MCP when:

• You need dedicated capabilities in the Version Control domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Docfork MCP Details

Feature & Specification Comparison

Specification	RiskState — Crypto Risk Engine Version Control	Docfork MCP Version Control
Summary	Live BTC/ETH risk state: risk policy, market structure and trading playbooks. Keyless free tier.	Up-to-date docs for AI agents. DEPRECATED: Use io.github.docfork/docfork instead.
Category & Scope	Version Control	Version Control

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": {
    "riskstate-crypto-risk-engine": {
      "command": "npx",
      "args": [
        "-y",
        "riskstate-crypto-risk-engine"
      ]
    }
  }
}

{
  "mcpServers": {
    "docfork-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "dgrep"
      ]
    }
  }
}

Related MCP Server Comparisons