Riskstate

Name: Riskstate
Author: likidodefi

@likidodefi

About Riskstate

Deterministic risk governance for crypto trading agents. Answers "How much can I risk?" with policy level, max position size, leverage limits, and blocked actions — computed from 9+ real-time data sources (on-chain, derivatives, macro, sentiment). Supports BTC and ETH. One tool:

#crypto #bitcoin #mcp #ethereum #trading-bot #policy-engine #ai-agents #defi #ai-trading #model-context-protocol #mcp-server #trading-agents #defi-risk-management #risk-governance

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "riskstate": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "RISKSTATE_API_KEY",
        "ghcr.io/likidodefi/riskstate-mcp"
      ],
      "env": {
        "RISKSTATE_API_KEY": "<your_api_key>"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Riskstate?

Riskstate is a risk governance API designed for autonomous crypto trading agents, providing deterministic policy computations from 9+ real-time data sources.

How to use Riskstate?

Invoke the get_risk_policy tool with the required asset parameter (either "BTC" or "ETH"), and optionally supply wallet_address, protocol ("spark" or "aave"), and include_details to receive a full risk policy and classification response.

Key features of Riskstate

Five policy levels from BLOCK (survival) to GREEN (expansion)
Max position size as percentage of portfolio (0–100)
Leverage limit – maximum allowed multiplier
Allowed and blocked actions for the agent
Confidence score reflecting signal agreement and data quality
Classification: cycle phase, market regime, macro regime, direction
Auditability with composite score, policy hash, and TTL

Use cases of Riskstate

A trading agent queries risk policy before opening a new position
Automated rebalancing based on policy level changes
Compliance logging via policy hash for audit trails
Multi-source risk assessment with confidence and subscores

FAQ from Riskstate

What parameters does `get_risk_policy` require?

The asset parameter (BTC or ETH) is required. Optional parameters include wallet_address, protocol (spark or aave), and include_details.

What does the response contain?

The response includes exposure_policy (policy level, max size, leverage, allowed/blocked actions), classification (cycle phase, market regime, macro regime, direction), and auditability (composite score, confidence score, policy hash, TTL).