Riskstate

Created By
likidodefi2 months ago
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: get_risk_policy.
Overview

RiskState MCP Server

Risk governance API for autonomous crypto trading agents.

What it does

Your agent asks: "How much can I risk?"

RiskState answers with a deterministic policy computed from 9+ real-time data sources:

  • Policy level — 5 levels from BLOCK (survival) to GREEN (expansion)
  • Max position size — % of portfolio cap (0-100)
  • Leverage limit — Maximum allowed multiplier
  • Allowed/blocked actions — What the agent can and cannot do
  • Confidence score — Signal agreement × data quality

Tool: get_risk_policy

ParameterTypeRequiredDescription
asset"BTC" or "ETH"YesAsset to analyze
wallet_addressstringNoDeFi wallet for on-chain position data
protocol"spark" or "aave"NoLending protocol (default: spark)
include_detailsbooleanNoFull breakdown (subscores, macro, risk flags)

Example Response

{
  "exposure_policy": {
    "policy_level": "CAUTIOUS",
    "max_size_pct": 35,
    "leverage_max": 1.5,
    "allowed_actions": ["DCA", "WAIT", "SPOT_LONG_CONFIRMED"],
    "blocked_actions": ["LEVERAGE_GT_2X", "NEW_POSITIONS_UNCONFIRMED"]
  },
  "classification": {
    "cycle_phase": "MID",
    "market_regime": "RANGE",
    "macro_regime": "NEUTRAL",
    "direction": "SIDEWAYS"
  },
  "auditability": {
    "composite_score": 52,
    "confidence_score": 0.72,
    "policy_hash": "a3f8c2...",
    "ttl_seconds": 60
  }
}

Server Config

{
  "mcpServers": {
    "riskstate": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "RISKSTATE_API_KEY",
        "ghcr.io/likidodefi/riskstate-mcp"
      ],
      "env": {
        "RISKSTATE_API_KEY": "<your_api_key>"
      }
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
likidodefi
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago