RiskState — Crypto Risk Engine
REMOTE · API.RISKSTATE.AI · SCANNED SEP 20
Live BTC/ETH risk state: risk policy, market structure and trading playbooks. Keyless free tier.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 471 tokens (~157/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the RiskState — Crypto Risk Engine MCP server?
RiskState — Crypto Risk Engine is a hosted endpoint at https://api.riskstate.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.riskstate.ai
claude mcp add --transport http ai-riskstate-mcp 'https://api.riskstate.ai/mcp'
{
"mcpServers": {
"ai-riskstate-mcp": {
"url": "https://api.riskstate.ai/mcp"
}
}
} {
"servers": {
"ai-riskstate-mcp": {
"type": "http",
"url": "https://api.riskstate.ai/mcp"
}
}
} [mcp_servers.ai-riskstate-mcp] url = "https://api.riskstate.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-riskstate-mcp": {
"type": "remote",
"url": "https://api.riskstate.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-riskstate-mcp --url 'https://api.riskstate.ai/mcp' --transport streamable-http
mcp_servers:
ai-riskstate-mcp:
url: "https://api.riskstate.ai/mcp" {
"McpServers": {
"ai-riskstate-mcp": {
"Transport": "http",
"Url": "https://api.riskstate.ai/mcp"
}
}
} assistant mcp add ai-riskstate-mcp -t streamable-http -u 'https://api.riskstate.ai/mcp'
{
"mcpServers": {
"ai-riskstate-mcp": {
"type": "http",
"url": "https://api.riskstate.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.riskstate.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.riskstate.ai | CN=YE2,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 63023db408cc70c2e64dab6c2a69dfd0b7d |
| SANs: api.riskstate.ai, app.riskstate.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.riskstate.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| riskstate.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.riskstate.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.riskstate.ai/mcp | HTTPS enforced | 301 | https://api.riskstate.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_market_structure Get BTC/ETH market structure ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Asset to analyze (default BTC) |
No output schema declared.
No examples provided.
get_playbook_status Get trading playbook status ~92
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_risk_state Get BTC/ETH risk state ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Asset to assess (default BTC) |
No output schema declared.
No examples provided.
What is the RiskState — Crypto Risk Engine MCP server?
RiskState — Crypto Risk Engine is an MCP server listed in the public MCP registry as ai.riskstate/mcp. Live BTC/ETH risk state: risk policy, market structure and trading playbooks. Keyless free tier. This page covers its hosted endpoint (https://api.riskstate.ai/mcp).
Is the RiskState — Crypto Risk Engine MCP server safe to use?
RiskState — Crypto Risk Engine scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RiskState — Crypto Risk Engine MCP server expose?
RiskState — Crypto Risk Engine exposes 3 tools: get_risk_state, get_market_structure, get_playbook_status. Their descriptions and schemas cost roughly 367 tokens of context every time the server is loaded.
Does the RiskState — Crypto Risk Engine MCP server require authentication?
No. We connected to RiskState — Crypto Risk Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RiskState — Crypto Risk Engine MCP server still maintained?
RiskState — Crypto Risk Engine is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.