Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.tooloracle/mica

REMOTE · TOOLORACLE.IO

MiCAOracle — 24 tools for EU MiCA stablecoin compliance: peg, reserves, attestations.

Available components

0 this week 78 Trust /100

Last scanned (19 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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
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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 28 Sept 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
  • 25 Sept 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 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
  • 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
Diagnostics

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 21 Nov 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=YE1,O=Let's Encrypt,C=US 12 Nov 2026 10 Feb 2027 ECDSA 256 ECDSA-SHA384 56ada3c3c9667f6eeefdd0b9dbc93811aa2
SANs: mcp.tooloracle.io, tooloracle.io, www.tooloracle.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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. DS published 38690 8 Verified
tooloracle.io. DS published 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/
MCP tools · 24 exposed · ~1,427 tokens

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 →

Tool Tokens
article_status ~54

Detailed Ampel for a specific MiCA article with check conditions.

NameTypeReqDescription
articlestring–e.g. Art. 35
entity_idstring–Entity ID
token_symbolstring–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.

NameTypeReqDescription
entity_idstring–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.

NameTypeReqDescription
entity_idstring–Entity ID (optional)
token_symbolstring–Token e.g. USDC, USDT, EURC, RLUSD

No output schema declared.

No examples provided.

audit_trail ~38

Chain-linked audit log with integrity check.

NameTypeReqDescription
entity_idstring–Entity ID (optional)
limitinteger–Max entries

No output schema declared.

No examples provided.

bridge_approve ~74

Approve or reject a bridge resolution. Approval upgrades Ampel to GREEN.

NameTypeReqDescription
approved_bystring–Name + role of approver
rejectboolean–Set true to reject
rejection_reasonstring–Reason for rejection
resolution_idstring–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).

NameTypeReqDescription
check_idstring–Check ID e.g. art35_c1, art24_c3
entity_idstring–Entity ID
expiry_daysinteger–Days until expiry (default 30)
token_symbolstring–Token e.g. USDC

No output schema declared.

No examples provided.

bridge_status ~38

Show all bridge resolutions for an entity/token.

NameTypeReqDescription
entity_idstring–Entity ID
token_symbolstring–Filter by token

No output schema declared.

No examples provided.

bus_status ~37

Oracle Event Bus status: events, cross-refs, connected oracles.

NameTypeReqDescription
entity_idstring–Entity ID for cross-refs

No output schema declared.

No examples provided.

create_entity ~57

Register a new regulated entity.

NameTypeReqDescription
entity_typestring–CASP, Bank, Verwahrer
jurisdictionstring–DE, AT
leistring–LEI
namestring–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).

NameTypeReqDescription
actionstring–status, assess, or reference
entity_idstring–Entity ID
token_symbolstring–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.

NameTypeReqDescription
entity_idstring–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.

NameTypeReqDescription
entity_idstring–Entity ID
max_age_daysinteger–Max evidence age in days (default 7)
token_symbolstring–Token (optional)

No output schema declared.

No examples provided.

gap_report ~45

MiCA compliance gaps: RED/YELLOW/GREY with priority and actions.

NameTypeReqDescription
entity_idstring–Entity ID (optional)
token_symbolstring–Token

No output schema declared.

No examples provided.

generate_report ~51

Generate MiCA compliance report for a token. Full article breakdown, evidence, bridges, audit.

NameTypeReqDescription
entity_idstring–Entity ID
token_symbolstring–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.

NameTypeReqDescription
actionstring–classify, delay, or status
approved_bystring–Person signing the decision
delay_reasonstring–Reason for delay (Art. 88(2))
entity_idstring–Entity ID
event_descriptionstring–Description of the event
event_typestring–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.

NameTypeReqDescription
issuer_idstring–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.

NameTypeReqDescription
entity_idstring–Entity ID
relationshipstring–custody, trading, settlement
token_symbolstring–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.

NameTypeReqDescription
days_backinteger–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.

NameTypeReqDescription
entity_idstring–Entity ID (optional)
token_symbolstring–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'.

NameTypeReqDescription
actionstring–detect, escalate, or status
approved_bystring–Surveillance Officer signing the escalation
descriptionstring–Signal description
entity_idstring–Entity ID
signal_typestring–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.

NameTypeReqDescription
formatstring–ixbrl or xhtml
token_symbolstring–Token e.g. USDC, USDT, EURC
urlstring–Whitepaper URL (optional)

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http io-tooloracle-mica 'https://tooloracle.io/mica/mcp/'
Common questions

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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.tooloracle/mica MCP server?

VerifyMCP ran 12 checks on io.tooloracle/mica, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.tooloracle/mica: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.