What is the key difference between RiskState — Crypto Risk Engine and Dockhold?

RiskState — Crypto Risk Engine belongs to the Version Control category with cloud HTTP/SSE execution, while Dockhold belongs to the Version Control category with cloud HTTP/SSE execution.

How do I install RiskState — Crypto Risk Engine or Dockhold in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are RiskState — Crypto Risk Engine and Dockhold free or paid?

RiskState — Crypto Risk Engine operates under a Free / Open Source model (No auth required). Dockhold operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

RiskState — Crypto Risk Engine lists 0 tools with 0 views and 0 GitHub stars. Dockhold lists 0 tools with 0 views and 0 GitHub stars.

Can I use both RiskState — Crypto Risk Engine and Dockhold together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install RiskState — Crypto Risk Engine or Dockhold in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are RiskState — Crypto Risk Engine and Dockhold free to use, or do they require API keys?

RiskState — Crypto Risk Engine is listed under a Free / Open Source model with No auth required . Dockhold operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both RiskState — Crypto Risk Engine and Dockhold at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both riskstate-crypto-risk-engine and dockhold as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, RiskState — Crypto Risk Engine has a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars. Dockhold holds a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

RiskState — Crypto Risk Engine vs Dockhold

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

RiskState — Crypto Risk Engine

Version Control · Remote HTTP/SSE

Quality: 42/100 (Fair) | Auth: No auth required

Dockhold

Version Control · Remote HTTP/SSE

Quality: 42/100 (Fair) | Auth: No auth required

Verdict Summary: Choose RiskState — Crypto Risk Engine if you need specialized Version Control tools running via a hosted cloud SSE transport. Choose Dockhold if your workspace requires Version Control integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose RiskState — Crypto Risk Engine when:

You need dedicated capabilities in the Version Control domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore RiskState — Crypto Risk Engine Details

Choose Dockhold when:

You need dedicated capabilities in the Version Control domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Dockhold Details

Feature & Specification Comparison

Specification	R RiskState — Crypto Risk Engine Version Control	D Dockhold Version Control
Summary	Live BTC/ETH risk state: risk policy, market structure and trading playbooks. Keyless free tier.	Deploy a GitHub repo to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.
Category & Scope	Version Control	Version Control
Quality signal

Tools & Capabilities Breakdown

RiskState — Crypto Risk Engine Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Dockhold Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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).

RiskState — Crypto Risk Engine Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "riskstate-crypto-risk-engine": {
      "url": "https://gitlab.com/likidodefi/riskstate-mcp"
    }
  }
}

Dockhold Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "dockhold": {
      "url": "https://dockhold.eu"
    }
  }
}

Frequently Asked Questions

RiskState — Crypto Risk Engine is categorized under Version Control and uses a remote streaming HTTP/SSE transport. In contrast, Dockhold belongs to Version Control using remote streaming HTTP/SSE transport. Select RiskState — Crypto Risk Engine when you need capabilities focused on version control and Dockhold when you require tools for version control.

More alternatives to RiskState — Crypto Risk Engine More alternatives to Dockhold Version Control category hub Canonical compare URL