Analytics

riskstate.ai

Provides real-time risk assessment, market structure analysis, and trading playbook status for Bitcoin and Ethereum.

1 endpoint3 known toolsFirst detected May 29, 2026Last detected July 25, 2026

ENDPOINT 1

https://api.riskstate.ai/mcp

No auth detected

MCP server metadata

Name: riskstate
Version: 1.0.0

Capabilities

tools

Server instructions

RiskState is a deterministic risk engine for BTC and ETH (spot, perps, DeFi borrowing). Use get_risk_state whenever the user asks about the current state, risk, or outlook of Bitcoin or Ethereum. These tools return a free public summary refreshed ~every 2 minutes. The full auditable response (policy_hash, composite subscores, positioning, macro detail, portfolio /v2 endpoints) requires an API key — https://riskstate.ai. Risk governance data, not financial advice.

Known tools 3

get_risk_state

Current risk state of Bitcoin (BTC) or Ethereum (ETH): 5-level risk policy (BLOCK to GREEN) with max position size, leverage limit, direction bias and allowed/blocked actions, plus composite score (0-100), structural and tactical scores, market regime (BULL/SIDEWAYS/BEAR), volatility regime, cycle phase and macro state.

Inferred read-only

get_market_structure

Market Structure Engine view for BTC or ETH: validated structural events firing now (breakouts, breakdowns, cycle bottom/top, funding resets), expected asymmetry, distance to the next bullish/bearish triggers, key structural levels (ATH, 200W MA, 180d range) and a friction map of confluence-scored support/resistance walls between spot and the triggers.

Inferred read-only

get_playbook_status

Trading Playbook Engine status: the registry of rule-based trade setups (playbooks) for BTC and ETH and which ones are firing right now, with structure-gate verdicts, cooldown state and why non-firing setups do not match (failed predicates with live market readings).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.riskstate]
url = "https://api.riskstate.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "riskstate": {
      "type": "http",
      "url": "https://api.riskstate.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: riskstate
Remote MCP URL: https://api.riskstate.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "riskstate": {
      "url": "https://api.riskstate.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "riskstate": {
      "type": "http",
      "url": "https://api.riskstate.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "riskstate",
  "transport": "streamable-http",
  "url": "https://api.riskstate.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.