MCP.Market

RiskState — Crypto Risk Engine MCP server

online · 100% uptime
by riskstate.ai·ai.riskstate/mcp·v1.0.1·1 stars
No reviews yet

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

A92/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

1 stars

Reviews

Write one

Nobody has reviewed RiskState — Crypto Risk Engine yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

RiskState — Crypto Risk Engine tools (3)

write = sends, deletes, buys or posts
  • get_market_structureFree

    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.

  • get_playbook_statusFree

    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.

  • get_risk_stateFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1177ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 22 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How RiskState — Crypto Risk Engine compares

Against every graded Finance MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 1,761 Finance servers
Tools
3
the typical Finance server has 8
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote Finance server answers 100%
Response time
509 ms
faster than 28% of 1,133 Finance servers
GitHub stars
1
more than 65% of 946 Finance servers

What its tools let an agent do: 3 read

Install RiskState — Crypto Risk Engine in Claude Code, Cursor or VS Code

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

What the publisher says

From the RiskState — Crypto Risk Engine repository's README, as published. We do not edit it. Read it on GitHub

RiskState MCP Server

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.

Two ways to use RiskState over MCP

1. Remote connector — no install, no API key. RiskState runs a hosted MCP server (Streamable HTTP) with a free public tier:

https://api.riskstate.ai/mcp

Add it as a custom connector in Claude or ChatGPT, then just ask what the risk state of BTC is. It exposes three read-only tools — getriskstate, getmarketstructure, getplaybookstatus — covering all three engines, and is listed on the official MCP registry as ai.riskstate/mcp.

Responses are the free public summary: the same altitude as the public visualizer. policy_hash, composite subscores, positioning and macro detail need a key.

2. This package — stdio, keyed, full response. Use it when you want the complete audited payload in a local agent, or to pin a version in your own toolchain. It needs a RISKSTATEAPIKEY and returns everything your key is entitled to. That is what the rest of this README covers.

Tools

Four read-only tools, one per question you might ask before a trade:

getriskpolicy returns:

checktrade evaluates a hypothetical book — send the position you are considering plus anything you already hold, since the caps are portfolio-aware. It returns per position whether it is allowed, the size cap in percent and dollars, and reasoncodes when it is not. Those are blocking; advisories are informational and do not affect allowed. It places no orders.

getplaybookstatus reports a setup as actionable only when its conditions match, no engine vetoed it, and it is not in alert cooldown. Setups that match but already alerted are counted separately, so an agent polling this tool does not act on the same signal twice.

Why there are no write tools

There is no updatepolicy, no setlimit, no exception management — and there will not be. The premise of RiskState is that the system being governed cannot move its own limits. Every decision is hashed (policy_hash) so it can be audited afterwards against the inputs that produced it; a tool that let the caller rewrite the policy would make that hash meaningless and the audit trail decorative.

So the lifecycle here deliberately lives on one side: the engine computes, the agent reads and complies. check_trade is the closest thing to a dynamic per-trade operation, and it is still read-only — it answers "would this be allowed", never "allow this".

The API aggregates 9+ real-time data sources server-side. See API docs for details.

What this wrapper does (and doesn't)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

RiskState — Crypto Risk Engine: common questions

Is RiskState — Crypto Risk Engine MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the RiskState — Crypto Risk Engine safety report
How do I install RiskState — Crypto Risk Engine?
It runs remotely at api.riskstate.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does RiskState — Crypto Risk Engine need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is RiskState — Crypto Risk Engine maintained?
The last commit was 55 days ago (2026-09-10). The latest release is v1.0.1.
Is RiskState — Crypto Risk Engine up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of RiskState — Crypto Risk Engine?
Servers from other publishers that do the same job: Trading Signals MCP server, CoinRithm Agent Trading MCP server and Coinbase Commerce MCP server. Compare all RiskState — Crypto Risk Engine alternatives.
How does RiskState — Crypto Risk Engine compare with other Finance MCP servers?
safety score 92/100 (higher than 95% of 1,761 Finance servers); tools 3 (the typical Finance server has 8); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to RiskState — Crypto Risk Engine

Same job from other publishers: the closest match first, then the best rated.

All RiskState — Crypto Risk Engine alternatives →