Skip to content

io.tooloracle/riskoracle

by tooloracle.io · remote · no sign-in to list tools · v1.0.0 · published by io.tooloracle

RiskOracle - 13-tool enterprise risk MCP: heatmaps, KRIs, scenario sims, Basel/ICAAP outputs.

Changes · 9
CompareRegistry entry

13 tools: 9 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http riskoracle https://tooloracle.io/risk/mcp/

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

13 tools

Changes things 9Claude Code: ask
  • cross_chain_dataCross-chain distribution, bridge riskNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Cross-chain distribution, bridge risk
  • custody_dataCustody model, SIFI status, jurisdictionNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Custody model, SIFI status, jurisdiction
  • holder_dataTop holder distribution, whale concentrationNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Top holder distribution, whale concentration
  • leaderboardStablecoins ranked by risk scoreNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Stablecoins ranked by risk score
  • methodologyRisk scoring methodologyNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Risk scoring methodology
  • peg_history30-day peg historyNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    30-day peg history
  • redemption_dataRedemption track record, latency, limitsNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Redemption track record, latency, limits
  • risk_assessmentFull risk score — 7 signals, 100-point scale, SAFE/CAUTION/AVOIDNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full risk score — 7 signals, 100-point scale, SAFE/CAUTION/AVOID
  • supply_flowSupply minting/burning, net flowNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Supply minting/burning, net flow
Only reads 4Claude Code: allow
  • compareHead-to-head comparison of 2+ stablecoinsNo findings

    Why it is in this group

    • The name "compare" says "compare": a word for reading.
    Description, as the server wrote it
    Head-to-head comparison of 2+ stablecoins
  • peg_statusCurrent peg status — deviation, stabilityNo findings

    Why it is in this group

    • The name "peg_status" says "status": a word for reading.
    Description, as the server wrote it
    Current peg status — deviation, stability
  • pingServer pingNo findings

    Why it is in this group

    • The name "ping" says "ping": a word for reading.
    Description, as the server wrote it
    Server ping
  • supported_tokensList supported stablecoinsNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List supported stablecoins

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.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http riskoracle https://tooloracle.io/risk/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__riskoracle__ping",
      "mcp__riskoracle__peg_status",
      "mcp__riskoracle__compare",
      "mcp__riskoracle__supported_tokens"
    ],
    "ask": [
      "mcp__riskoracle__risk_assessment",
      "mcp__riskoracle__peg_history",
      "mcp__riskoracle__supply_flow",
      "mcp__riskoracle__holder_data",
      "mcp__riskoracle__custody_data",
      "mcp__riskoracle__redemption_data",
      "mcp__riskoracle__cross_chain_data",
      "mcp__riskoracle__leaderboard",
      "mcp__riskoracle__methodology"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as riskoracle. Review it before you use it.