A community-driven registry for the Claude Code ecosystem. Not affiliated with Anthropic.
Are you the author? Sign in to claim
MCP server for RiskState — pre-trade risk permissions for BTC/USD and ETH/USD. Spot, perps, and DeFi aware. Wraps POST /
MCP server for RiskState — pre-trade risk permissions for BTC/USD and ETH/USD. Spot, perpetual futures (perps), and DeFi borrowing aware.
Your system asks: "How much can I risk right now?" RiskState answers with: policy level, max exposure, leverage limits, blocked actions — computed from 30+ real-time signals.
Wraps the RiskState /v1/risk-state API as an MCP tool. One tool: get_risk_policy.
| Field | Description |
|---|---|
policy_level | 5 levels: BLOCK_SURVIVAL, BLOCK_DEFENSIVE, CAUTIOUS, GREEN_SELECTIVE, GREEN_EXPANSION |
max_size_pct | Maximum position size as % of portfolio (0-100) |
leverage_max | Maximum allowed leverage multiplier |
allowed_actions | What the agent CAN do at this policy level |
blocked_actions | What the agent CANNOT do |
confidence_score | Signal agreement x data quality (0-1) |
The API aggregates 9+ real-time data sources server-side. See API docs for details.
This is a thin wrapper — it translates MCP tool calls into REST API requests to POST /v1/risk-state and returns the response. All computation (scoring, policy engine, data ingestion) happens server-side.
This wrapper adds:
This wrapper does NOT:
npm install @riskstate/mcp-server
| Variable | Required | Description |
|---|---|---|
RISKSTATE_API_KEY | Yes | API key from riskstate.ai (free during beta) |
RISKSTATE_API_URL | No | Custom API base URL (default: https://api.riskstate.ai) |
Add to ~/.config/Claude/claude_desktop_config.json:
{
"mcpServers": {
"riskstate": {
"command": "npx",
"args": ["-p", "@riskstate/mcp-server", "riskstate-mcp"],
"env": {
"RISKSTATE_API_KEY": "your-api-key"
}
}
}
}
claude mcp add riskstate -- npx -p @riskstate/mcp-server riskstate-mcp
Set the API key in your environment:
export RISKSTATE_API_KEY=your-api-key
npm install -g @riskstate/mcp-server
riskstate-mcp # starts MCP server on stdio
The server exposes one tool: get_risk_policy
| Parameter | Type | Required | Description |
|---|---|---|---|
asset | "BTC" | "ETH" | Yes | Asset to analyze |
wallet_address | string | No | DeFi wallet for on-chain position data |
protocol | "spark" | "aave" | No | Lending protocol (default: spark) |
include_details | boolean | No | Include full breakdown (subscores, macro, risk flags) |
{
"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
}
}
Call get_risk_policy before every trade:
policy_level starts with BLOCK → do not open new positionsmax_size_pct to cap position sizingblocked_actions before executingttl_seconds (60s cache)MIT
Run Claude Code as an MCP server so any agent can delegate coding tasks to it
Browser automation using accessibility snapshots instead of screenshots
MCP server integration for DaVinci Resolve Studio
Secure MCP server for MySQL database interaction, queries, and schema management
0
via CLI