io.tooloracle/mica
REMOTE · TOOLORACLE.IO · SCANNED SEP 24
MiCAOracle — 24 tools for EU MiCA stablecoin compliance: peg, reserves, attestations.
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 24 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 Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1427 tokens (~59/item across 24 items; 24 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 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 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 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/mica MCP server?
io.tooloracle/mica is a hosted endpoint at https://tooloracle.io/mica/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-mica 'https://tooloracle.io/mica/mcp/'
{
"mcpServers": {
"io-tooloracle-mica": {
"url": "https://tooloracle.io/mica/mcp/"
}
}
} {
"servers": {
"io-tooloracle-mica": {
"type": "http",
"url": "https://tooloracle.io/mica/mcp/"
}
}
} [mcp_servers.io-tooloracle-mica] url = "https://tooloracle.io/mica/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-tooloracle-mica": {
"type": "remote",
"url": "https://tooloracle.io/mica/mcp/",
"enabled": true
}
}
} openclaw mcp add io-tooloracle-mica --url 'https://tooloracle.io/mica/mcp/' --transport streamable-http
mcp_servers:
io-tooloracle-mica:
url: "https://tooloracle.io/mica/mcp/" {
"McpServers": {
"io-tooloracle-mica": {
"Transport": "http",
"Url": "https://tooloracle.io/mica/mcp/"
}
}
} assistant mcp add io-tooloracle-mica -t streamable-http -u 'https://tooloracle.io/mica/mcp/'
{
"mcpServers": {
"io-tooloracle-mica": {
"type": "http",
"url": "https://tooloracle.io/mica/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 78
- 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
- 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 24 Sept 2026 · Probed https://tooloracle.io/mica/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/mica/mcp/ | Verified | 200 | |
| http (plaintext) | http://tooloracle.io/mica/mcp/ | HTTPS enforced | 308 | https://tooloracle.io/mica/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 →
article_status ~54
Detailed Ampel for a specific MiCA article with check conditions.
| Name | Type | Req | Description |
|---|---|---|---|
| article | string | – | e.g. Art. 35 |
| entity_id | string | – | Entity ID |
| token_symbol | string | – | Token |
No output schema declared.
No examples provided.
assess_entity ~40
Assess ALL tokens for an entity in one call. Runs live FeedOracle assessment for each linked token.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Entity ID (optional) |
No output schema declared.
No examples provided.
assess_token ~65
Run LIVE MiCA assessment via FeedOracle mica_full_pack. Evaluates 18 checks, updates Ampel.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Entity ID (optional) |
| token_symbol | string | – | Token e.g. USDC, USDT, EURC, RLUSD |
No output schema declared.
No examples provided.
audit_trail ~38
Chain-linked audit log with integrity check.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Entity ID (optional) |
| limit | integer | – | Max entries |
No output schema declared.
No examples provided.
bridge_approve ~74
Approve or reject a bridge resolution. Approval upgrades Ampel to GREEN.
| Name | Type | Req | Description |
|---|---|---|---|
| approved_by | string | – | Name + role of approver |
| reject | boolean | – | Set true to reject |
| rejection_reason | string | – | Reason for rejection |
| resolution_id | string | – | Resolution ID from bridge_resolve |
No output schema declared.
No examples provided.
bridge_resolve ~94
Start bridge resolution for a MiCA gap. Generates template (issuer engagement, risk acceptance, token replacement, monitoring upgrade).
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | – | Check ID e.g. art35_c1, art24_c3 |
| entity_id | string | – | Entity ID |
| expiry_days | integer | – | Days until expiry (default 30) |
| token_symbol | string | – | Token e.g. USDC |
No output schema declared.
No examples provided.
bridge_status ~38
Show all bridge resolutions for an entity/token.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Entity ID |
| token_symbol | string | – | Filter by token |
No output schema declared.
No examples provided.
bus_status ~37
Oracle Event Bus status: events, cross-refs, connected oracles.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Entity ID for cross-refs |
No output schema declared.
No examples provided.
create_entity ~57
Register a new regulated entity.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_type | string | – | CASP, Bank, Verwahrer |
| jurisdiction | string | – | DE, AT |
| lei | string | – | LEI |
| name | string | – | Entity name |
No output schema declared.
No examples provided.
eidas_timestamp ~79
eIDAS-qualified timestamp integration status and assessment. Maps FeedOracle ES256K signatures to EU trust framework (eIDAS Art. 25, 41-42).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | status, assess, or reference |
| entity_id | string | – | Entity ID |
| token_symbol | string | – | Token for assess action |
No output schema declared.
No examples provided.
entity_ampel ~47
Aggregate MiCA Ampel for an entity across ALL tokens it custodies. Shows per-token breakdown + overall score.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Entity ID (optional, uses first) |
No output schema declared.
No examples provided.
entity_list ~13
List all registered entities.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
freshness_check ~70
Expire stale evidence. Downgrades GREEN→YELLOW if evidence older than max_age_days. Run daily.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Entity ID |
| max_age_days | integer | – | Max evidence age in days (default 7) |
| token_symbol | string | – | Token (optional) |
No output schema declared.
No examples provided.
gap_report ~45
MiCA compliance gaps: RED/YELLOW/GREY with priority and actions.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Entity ID (optional) |
| token_symbol | string | – | Token |
No output schema declared.
No examples provided.
generate_report ~51
Generate MiCA compliance report for a token. Full article breakdown, evidence, bridges, audit.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Entity ID |
| token_symbol | string | – | Token e.g. USDC |
No output schema declared.
No examples provided.
health_check ~13
Server + DB status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
insider_escalation ~140
Inside Information classification, delay and disclosure workflow per MiCA Art. 87-88 and Implementing Regulation 2024/2861. AI-assisted with mandatory human sign-off.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | classify, delay, or status |
| approved_by | string | – | Person signing the decision |
| delay_reason | string | – | Reason for delay (Art. 88(2)) |
| entity_id | string | – | Entity ID |
| event_description | string | – | Description of the event |
| event_type | string | – | reserve_breach, peg_deviation, regulatory_action, management_change, material_event, partnership, technical_upgrade |
No output schema declared.
No examples provided.
issuer_list ~22
List all known token issuers with MiCA authorization status and tokens.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
issuer_profile ~51
Issuer profile with all tokens and aggregate MiCA Ampel. Shows authorization status, headquarters, token scores.
| Name | Type | Req | Description |
|---|---|---|---|
| issuer_id | string | – | Issuer ID or name e.g. circle, tether, ripple |
No output schema declared.
No examples provided.
link_token ~53
Link a token to an entity for monitoring.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Entity ID |
| relationship | string | – | custody, trading, settlement |
| token_symbol | string | – | Token e.g. USDC |
No output schema declared.
No examples provided.
mica_watchdog ~47
Monitor ESMA/EBA/BaFin for MiCA regulatory changes. Returns monitored sources and alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| days_back | integer | – | Check items from last N days (default 7) |
No output schema declared.
No examples provided.
readiness_check ~73
Full MiCA readiness score + Ampel per article for a token. GREEN/YELLOW/RED/GREY for 10 articles, score 0-100.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Entity ID (optional) |
| token_symbol | string | – | Token e.g. USDC, USDT, EURC |
No output schema declared.
No examples provided.
stor_workflow ~120
Suspicious Transaction and Order Report (STOR) workflow per MiCA Art. 92. AI-assisted detection with mandatory human sign-off for 'reasonable suspicion'.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | detect, escalate, or status |
| approved_by | string | – | Surveillance Officer signing the escalation |
| description | string | – | Signal description |
| entity_id | string | – | Entity ID |
| signal_type | string | – | wash_trading, spoofing, insider_trading, market_manipulation, front_running, pump_dump, unusual_volume, concentration |
No output schema declared.
No examples provided.
validate_whitepaper ~106
Validate crypto-asset whitepaper against MiCA Art. 6(10)-(11) and ITS 2024/2984. Checks iXBRL/XHTML format, taxonomy tagging, mandatory fields, risk warnings, NCA notification, version archive.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | ixbrl or xhtml |
| token_symbol | string | – | Token e.g. USDC, USDT, EURC |
| url | string | – | Whitepaper URL (optional) |
No output schema declared.
No examples provided.
What is the io.tooloracle/mica MCP server?
io.tooloracle/mica is an MCP server listed in the public MCP registry as io.tooloracle/mica. MiCAOracle, 24 tools for EU MiCA stablecoin compliance: peg, reserves, attestations. This page covers its hosted endpoint (https://tooloracle.io/mica/mcp/).
Is the io.tooloracle/mica MCP server safe to use?
io.tooloracle/mica scores 78 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/mica MCP server expose?
io.tooloracle/mica exposes 24 tools: readiness_check, article_status, gap_report, assess_token, entity_list, and 19 more. Their descriptions and schemas cost roughly 1,427 tokens of context every time the server is loaded.
Does the io.tooloracle/mica MCP server require authentication?
No. We connected to io.tooloracle/mica without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.tooloracle/mica MCP server still maintained?
io.tooloracle/mica is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.