Skip to content

RiskState — Crypto Risk Engine

by riskstate.ai · remote · no sign-in to list tools · v1.0.1 · published by ai.riskstate

Live BTC/ETH risk state: risk policy, market structure and trading playbooks. Keyless free tier.

Read only
CompareRegistry entry

3 tools: 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http riskstate https://api.riskstate.ai/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Only reads 3Claude Code: allow
  • get_market_structureMarket Structure Engine view for BTC or ETH: validated structural events firing now (breakouts, breakdowns, cycle bottom/top, funding resets), expected asymmetry, distance to the n…No findings

    Why it is in this group

    • The name "get_market_structure" says "get": a word for reading.
    Description, as the server wrote it
    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. Use for questions about levels, support/resistance, breakouts or what would change the picture.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • get_playbook_statusTrading 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 stat…No findings

    Why it is in this group

    • The name "get_playbook_status" says "get": a word for reading.
    Description, as the server wrote it
    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). Strategy-level only — no prices, sizes or portfolio data. Use for questions about active trade setups or what the playbooks are watching.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • get_risk_stateCurrent 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…No findings

    Why it is in this group

    • The name "get_risk_state" says "get": a word for reading.
    Description, as the server wrote it
    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. Computed from 9+ real-time data sources (price, funding, RSI, MVRV, ETF flows, on-chain, macro). Use whenever the user asks how BTC or ETH is doing, whether it is a good time to buy/sell/hold, or how much risk to take.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http riskstate https://api.riskstate.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__riskstate__get_risk_state",
      "mcp__riskstate__get_market_structure",
      "mcp__riskstate__get_playbook_status"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as riskstate. Review it before you use it.