io.tooloracle/riskoracle
REMOTE · TOOLORACLE.IO · SCANNED SEP 20
RiskOracle - 13-tool enterprise risk MCP: heatmaps, KRIs, scenario sims, Basel/ICAAP outputs.
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 Security66
- 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 13 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 378 tokens (~29/item across 13 items; 13 tools + 0 resources), lean.Pass
- 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 Coverage79
- 92% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 54% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.tooloracle/riskoracle MCP server?
io.tooloracle/riskoracle is a hosted endpoint at https://tooloracle.io/risk/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 · tooloracle.io
claude mcp add --transport http io-tooloracle-riskoracle 'https://tooloracle.io/risk/mcp/'
{
"mcpServers": {
"io-tooloracle-riskoracle": {
"url": "https://tooloracle.io/risk/mcp/"
}
}
} {
"servers": {
"io-tooloracle-riskoracle": {
"type": "http",
"url": "https://tooloracle.io/risk/mcp/"
}
}
} [mcp_servers.io-tooloracle-riskoracle] url = "https://tooloracle.io/risk/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-tooloracle-riskoracle": {
"type": "remote",
"url": "https://tooloracle.io/risk/mcp/",
"enabled": true
}
}
} openclaw mcp add io-tooloracle-riskoracle --url 'https://tooloracle.io/risk/mcp/' --transport streamable-http
mcp_servers:
io-tooloracle-riskoracle:
url: "https://tooloracle.io/risk/mcp/" {
"McpServers": {
"io-tooloracle-riskoracle": {
"Transport": "http",
"Url": "https://tooloracle.io/risk/mcp/"
}
}
} assistant mcp add io-tooloracle-riskoracle -t streamable-http -u 'https://tooloracle.io/risk/mcp/'
{
"mcpServers": {
"io-tooloracle-riskoracle": {
"type": "http",
"url": "https://tooloracle.io/risk/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 +1
- 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://tooloracle.io/risk/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tooloracle.io | CN=YE2,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6375d594a6b9fdf6754e5a9a3d1f38b0dbd |
| SANs: mcp.tooloracle.io, tooloracle.io, www.tooloracle.io | ||||||
| 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 secure
Validation of tooloracle.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| tooloracle.io. | present | 45856 | 8 | Verified |
| tooloracle.io. | Verified address RRset verified with the apex keys |
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; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tooloracle.io/risk/mcp/ | Verified | 200 | |
| http (plaintext) | http://tooloracle.io/risk/mcp/ | HTTPS enforced | 308 | https://tooloracle.io/risk/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 →
compare ~33
Head-to-head comparison of 2+ stablecoins
| Name | Type | Req | Description |
|---|---|---|---|
| symbols | array | yes | – |
| use_case | string | – | – |
No output schema declared.
No examples provided.
cross_chain_data ~34
Cross-chain distribution, bridge risk
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Stablecoin symbol e.g. USDC, USDT |
No output schema declared.
No examples provided.
custody_data ~36
Custody model, SIFI status, jurisdiction
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Stablecoin symbol e.g. USDC, USDT |
No output schema declared.
No examples provided.
holder_data ~33
Top holder distribution, whale concentration
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Stablecoin symbol e.g. USDC, USDT |
No output schema declared.
No examples provided.
leaderboard ~21
Stablecoins ranked by risk score
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
methodology ~11
Risk scoring methodology
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
peg_history ~32
30-day peg history
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Stablecoin symbol e.g. USDC, USDT |
No output schema declared.
No examples provided.
peg_status ~34
Current peg status — deviation, stability
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Stablecoin symbol e.g. USDC, USDT |
No output schema declared.
No examples provided.
ping ~10
Server ping
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
redemption_data ~34
Redemption track record, latency, limits
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Stablecoin symbol e.g. USDC, USDT |
No output schema declared.
No examples provided.
risk_assessment ~52
Full risk score — 7 signals, 100-point scale, SAFE/CAUTION/AVOID
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| symbol | string | yes | – |
| use_case | string | – | – |
No output schema declared.
No examples provided.
supply_flow ~35
Supply minting/burning, net flow
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Stablecoin symbol e.g. USDC, USDT |
No output schema declared.
No examples provided.
supported_tokens ~13
List supported stablecoins
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.tooloracle/riskoracle MCP server?
io.tooloracle/riskoracle is an MCP server listed in the public MCP registry as io.tooloracle/riskoracle. RiskOracle - 13-tool enterprise risk MCP: heatmaps, KRIs, scenario sims, Basel/ICAAP outputs. This page covers its hosted endpoint (https://tooloracle.io/risk/mcp/).
Is the io.tooloracle/riskoracle MCP server safe to use?
io.tooloracle/riskoracle scores 75 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 io.tooloracle/riskoracle MCP server expose?
io.tooloracle/riskoracle exposes 13 tools: ping, risk_assessment, peg_status, peg_history, supply_flow, and 8 more. Their descriptions and schemas cost roughly 378 tokens of context every time the server is loaded.
Does the io.tooloracle/riskoracle MCP server require authentication?
No. We connected to io.tooloracle/riskoracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.tooloracle/riskoracle MCP server still maintained?
io.tooloracle/riskoracle 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.