RiskState — Crypto Risk Engine: MCP server
Tells an agent how much risk is allowed right now: policy level, leverage cap and blocked actions for BTC and ETH.
claude mcp add --transport http mcp https://api.riskstate.ai/mcpWhat RiskState — Crypto Risk Engine does
Four read-only tools ship with the server. get_risk_policy reports the policy level, the largest position size as a percentage, the leverage ceiling, and which actions are permitted or barred. get_market_structure flags whether price sits near a structural turning point. get_playbook_status says if a setup is live, and check_trade tests a proposed position against what the portfolio already holds.
The package is a thin wrapper. MCP calls become REST requests, and every score is computed on the provider's side. What it adds locally: Zod validation of inputs, a plain-language policy summary at the top of each response, and distinct error messages for auth, rate limit and timeout so an agent can react. Nothing is cached here; the API keeps its own 60-second cache.
The stdio build wants RISKSTATE_API_KEY in your environment. Write tools are absent by design, so an agent cannot rewrite the limits it is judged by. No key yet? Point your client at the hosted connector https://api.riskstate.ai/mcp and you get the public summary without installing anything.
What it helps with
- cap position size before entering a trade
- check whether a leverage level is blocked
- see if the market is near a structural inflection
- find out whether a setup is actionable or in cooldown
- test a hypothetical portfolio before opening a position
Example prompts for the agent
- What's the current risk state for BTC?
- Run
check_tradeon a 0.5 BTC position given that I already hold 0.2 BTC - Call
get_playbook_statusand tell me if there's an actionable ETH setup
How to install RiskState — Crypto Risk Engine
Platform CLI: remote server
claude mcp add --transport http mcp https://api.riskstate.ai/mcpPlatform CLI: remote server
codex mcp add riskstate-crypto-risk-engine --url https://api.riskstate.ai/mcpConfig file
{
"mcpServers": {
"riskstate-crypto-risk-engine": {
"url": "https://api.riskstate.ai/mcp"
}
}
}Config file
{
"servers": {
"riskstate-crypto-risk-engine": {
"type": "http",
"url": "https://api.riskstate.ai/mcp"
}
}
}Platform CLI: remote server
gemini mcp add -t http riskstate-crypto-risk-engine https://api.riskstate.ai/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about RiskState — Crypto Risk Engine
How do I install RiskState — Crypto Risk Engine in Claude Code?
Run claude mcp add --transport http riskstate-crypto-risk-engine https://api.riskstate.ai/mcp. No API key is needed for this remote setup.
What does RiskState — Crypto Risk Engine do?
It computes a risk policy for BTC and ETH: allowed exposure, leverage limits and blocked actions. The agent reads that policy before trading and cannot alter it.
Do I need an API key?
Not for the remote connector, which returns the public summary. The local @riskstate/mcp-server package requires RISKSTATE_API_KEY and returns the full payload.
