Home / MCP registry index / io.tooloracle/mica
io.tooloracle/mica
io.tooloracle/mica in the official MCP registry.
Endpoint https://tooloracle.io/mica/mcp/. Source: github.com/ToolOracle/mica.
The registry describes it as: MiCAOracle — 24 tools for EU MiCA stablecoin compliance: peg, reserves, attestations.
We read its 24 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
readiness_check article_status gap_report assess_token entity_list create_entity audit_trail health_check issuer_profile entity_ampel issuer_list link_token assess_entity bridge_resolve bridge_approve bridge_status bus_status freshness_check mica_watchdog generate_report validate_whitepaper insider_escalation stor_workflow eidas_timestamp
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-tooloracle-mica)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.