mcp-registry/io.tooloracle/mica · v1.0.0
As of 2026-10-26 16:41 UTC, the Tooloracle Mica MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 13 minutes.
MiCAOracle — 24 tools for EU MiCA stablecoin compliance: peg, reserves, attestations.
Point your MCP client at this streamable-http endpoint: https://tooloracle.io/mica/mcp/
24 of 24 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
1 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.tooloracle%2Fmica/fixes
{
"name": "article_status",
"description": "Detailed Ampel for a specific MiCA article with check conditions.",
"inputSchema": {
"type": "object",
"properties": {
"article": {
"type": "string",
"description": "e.g. Art. 35"
},
"entity_id": {
"type": "string",
"description": "Entity ID"
},
"token_symbol": {
"type": "string",
"description": "Token"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "bridge_approve",
"description": "Approve or reject a bridge resolution. Approval upgrades Ampel to GREEN.",
"inputSchema": {
"type": "object",
"properties": {
"reject": {
"type": "boolean",
"description": "Set true to reject"
},
"approved_by": {
"type": "string",
"description": "Name + role of approver"
},
"resolution_id": {
"type": "string",
"description": "Resolution ID from bridge_resolve"
},
"rejection_reason": {
"type": "string",
"description": "Reason for rejection"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "bridge_resolve",
"description": "Start bridge resolution for a MiCA gap. Generates template (issuer engagement, risk acceptance, token replacement, monitoring upgrade).",
"inputSchema": {
"type": "object",
"properties": {
"check_id": {
"type": "string",
"description": "Check ID e.g. art35_c1, art24_c3"
},
"entity_id": {
"type": "string",
"description": "Entity ID"
},
"expiry_days": {
"type": "integer",
"description": "Days until expiry (default 30)"
},
"token_symbol": {
"type": "string",
"description": "Token e.g. USDC"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.tooloracle/mica"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.tooloracle/mica"}) over MCP.
insider_escalation ~226 tokensstor_workflow ~201 tokensbridge_resolve ~148 tokensvalidate_whitepaper ~144 tokensbridge_approve ~135 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fmica?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fmica?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fmica.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fmica.svg :target: https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fmica?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5b1bc4a7b219d763…, first seen 2026-10-17, included at leaf 6490 of 74,175. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable ml servers · most reliable security servers · most reliable other servers · most reliable devops servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 16:41 UTC, the Tooloracle Mica MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 13 minutes.
Tooloracle Mica MCP server advertises 24 tools, including article_status, assess_entity, assess_token, audit_trail, bridge_approve.
Point your MCP client at this streamable-http endpoint: https://tooloracle.io/mica/mcp/
Glimind scanned all 24 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.