RiskState — Crypto Risk Engine MCP server
ai.riskstate/mcpriskstate.aistreamable-httpv1.0.1Scanned
Live BTC/ETH risk state: risk policy, market structure and trading playbooks. Keyless free tier.
3 tools: 3 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the RiskState — Crypto Risk Engine MCP server can do
The RiskState — Crypto Risk Engine MCP server is published by riskstate.ai, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools bring in text other people can write (get_risk_state, get_market_structure and get_playbook_status).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Only reads 3Show 3 read-only tools
get_market_structureMarket Structure Engine view for BTC or ETH: validated structural events firing now (breakouts, breakdowns, cycle bottom/top, funding resets), expected asymmetry, distance to the n…Reads text others writeNo findings
Why it is in this group
- The name "get_market_structure" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
get_playbook_statusTrading 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 stat…Reads text others writeNo findings
Why it is in this group
- The name "get_playbook_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
get_risk_stateCurrent 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…Reads text others writeNo findings
Why it is in this group
- The name "get_risk_state" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:27 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http riskstate https://api.riskstate.ai/mcpclaude mcp add --transport http riskstate https://api.riskstate.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__riskstate__get_risk_state",
"mcp__riskstate__get_market_structure",
"mcp__riskstate__get_playbook_status"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as riskstate. Review it before you use it.
Capability tags behind 3 rules
- mcp__riskstate__get_risk_state untrusted-input
- mcp__riskstate__get_market_structure untrusted-input
- mcp__riskstate__get_playbook_status untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.riskstate/mcp/verify?hash=c90047391d934878697bd22ea6c9c88867034ccc066bacf9fd76dea292064251" | jq -e '.changed == false'Pinned hash c90047391d93, from Nov 10, 2026, 04:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.riskstate/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.riskstate/mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:43 UTC.
RiskState — Crypto Risk Engine MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RiskState — Crypto Risk Engine MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the RiskState — Crypto Risk Engine MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the RiskState — Crypto Risk Engine MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the RiskState — Crypto Risk Engine MCP server have?
- 3 tools: 3 read. get_risk_state, get_market_structure and get_playbook_status.
Does the RiskState — Crypto Risk Engine MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RiskState — Crypto Risk Engine MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the RiskState — Crypto Risk Engine MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.