Skip to content

mica MCP server

io.tooloracle/micatooloracle.iostreamable-httpv1.0.0Scanned

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

24 tools: 18 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 18 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

18 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the mica MCP server can do

The mica MCP server is published by tooloracle.io, a domain the MCP Registry verified. It has 24 tools. It can create or change data (18 tools: readiness_check, gap_report, assess_token, create_entity and 14 more), but cannot delete data. 6 tools only read.

1 tool can send data out of your system (validate_whitepaper).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

24 tools

Changes things 18Claude Code: ask
  • assess_entityAssess ALL tokens for an entity in one call.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Assess ALL tokens for an entity in one call. Runs live FeedOracle assessment for each linked token.
  • assess_tokenRun LIVE MiCA assessment via FeedOracle mica_full_pack.No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    Run LIVE MiCA assessment via FeedOracle mica_full_pack. Evaluates 18 checks, updates Ampel.
  • audit_trailChain-linked audit log with integrity check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Chain-linked audit log with integrity check.
  • bridge_approveApprove or reject a bridge resolution.No findings

    Why it is in this group

    • The name "bridge_approve" says "approve": a word for a change.
    Description, as the server wrote it
    Approve or reject a bridge resolution. Approval upgrades Ampel to GREEN.
  • bridge_resolveStart bridge resolution for a MiCA gap.No findings

    Why it is in this group

    • The name "bridge_resolve" says "resolve": a word for reading.
    • The description's first verb is "start": a word for a change.
    Description, as the server wrote it
    Start bridge resolution for a MiCA gap. Generates template (issuer engagement, risk acceptance, token replacement, monitoring upgrade).
  • create_entityRegister a new regulated entity.No findings

    Why it is in this group

    • The name "create_entity" says "create": a word for a change.
    Description, as the server wrote it
    Register a new regulated entity.
  • eidas_timestampeIDAS-qualified timestamp integration status and assessment.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    eIDAS-qualified timestamp integration status and assessment. Maps FeedOracle ES256K signatures to EU trust framework (eIDAS Art. 25, 41-42).
  • entity_ampelAggregate MiCA Ampel for an entity across ALL tokens it custodies.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Aggregate MiCA Ampel for an entity across ALL tokens it custodies. Shows per-token breakdown + overall score.
  • freshness_checkExpire stale evidence.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Expire stale evidence. Downgrades GREEN→YELLOW if evidence older than max_age_days. Run daily.
  • gap_reportMiCA compliance gaps: RED/YELLOW/GREY with priority and actions.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    MiCA compliance gaps: RED/YELLOW/GREY with priority and actions.
  • generate_reportGenerate MiCA compliance report for a token.No findings

    Why it is in this group

    • The name "generate_report" says "generate": a word for a change.
    Description, as the server wrote it
    Generate MiCA compliance report for a token. Full article breakdown, evidence, bridges, audit.
  • health_checkServer + DB status.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Server + DB status.
  • insider_escalationInside Information classification, delay and disclosure workflow per MiCA Art.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Inside Information classification, delay and disclosure workflow per MiCA Art. 87-88 and Implementing Regulation 2024/2861. AI-assisted with mandatory human sign-off.
  • issuer_profileIssuer profile with all tokens and aggregate MiCA Ampel.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Issuer profile with all tokens and aggregate MiCA Ampel. Shows authorization status, headquarters, token scores.
  • mica_watchdogMonitor ESMA/EBA/BaFin for MiCA regulatory changes.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Monitor ESMA/EBA/BaFin for MiCA regulatory changes. Returns monitored sources and alerts.
  • readiness_checkFull MiCA readiness score + Ampel per article for a token.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full MiCA readiness score + Ampel per article for a token. GREEN/YELLOW/RED/GREY for 10 articles, score 0-100.
  • stor_workflowSuspicious Transaction and Order Report (STOR) workflow per MiCA Art.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Suspicious Transaction and Order Report (STOR) workflow per MiCA Art. 92. AI-assisted detection with mandatory human sign-off for 'reasonable suspicion'.
Only reads 6Show 6 read-only tools
  • article_statusDetailed Ampel for a specific MiCA article with check conditions.No findings

    Why it is in this group

    • The name "article_status" says "status": a word for reading.
    Description, as the server wrote it
    Detailed Ampel for a specific MiCA article with check conditions.
  • bridge_statusShow all bridge resolutions for an entity/token.No findings

    Why it is in this group

    • The name "bridge_status" says "status": a word for reading.
    Description, as the server wrote it
    Show all bridge resolutions for an entity/token.
  • bus_statusOracle Event Bus status: events, cross-refs, connected oracles.No findings

    Why it is in this group

    • The name "bus_status" says "status": a word for reading.
    Description, as the server wrote it
    Oracle Event Bus status: events, cross-refs, connected oracles.
  • entity_listList all registered entities.No findings

    Why it is in this group

    • The name "entity_list" says "list": a word for reading.
    Description, as the server wrote it
    List all registered entities.
  • issuer_listList all known token issuers with MiCA authorization status and tokens.No findings

    Why it is in this group

    • The name "issuer_list" says "list": a word for reading.
    Description, as the server wrote it
    List all known token issuers with MiCA authorization status and tokens.
  • validate_whitepaperValidate crypto-asset whitepaper against MiCA Art.Can send data outNo findings

    Why it is in this group

    • The name "validate_whitepaper" says "validate": a word for reading.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:30 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
18
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://tooloracle.io/.well-known/oauth-protected-resource/mica/mcp
Authorization servers
https://feedoracle.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 18 tools that change things (18 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://tooloracle.io/mica/mcp/: tools/list returned 24 tools to an anonymous client, including readiness_check (write), gap_report (write), assess_token (write), create_entity (write), audit_trail (write) and 13 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http mica https://tooloracle.io/mica/mcp/
claude mcp add --transport http mica https://tooloracle.io/mica/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mica__article_status",
      "mcp__mica__entity_list",
      "mcp__mica__issuer_list",
      "mcp__mica__bridge_status",
      "mcp__mica__bus_status"
    ],
    "ask": [
      "mcp__mica__readiness_check",
      "mcp__mica__gap_report",
      "mcp__mica__assess_token",
      "mcp__mica__create_entity",
      "mcp__mica__audit_trail",
      "mcp__mica__health_check",
      "mcp__mica__issuer_profile",
      "mcp__mica__entity_ampel",
      "mcp__mica__link_token",
      "mcp__mica__assess_entity",
      "mcp__mica__bridge_resolve",
      "mcp__mica__bridge_approve",
      "mcp__mica__freshness_check",
      "mcp__mica__mica_watchdog",
      "mcp__mica__generate_report",
      "mcp__mica__validate_whitepaper",
      "mcp__mica__insider_escalation",
      "mcp__mica__stor_workflow",
      "mcp__mica__eidas_timestamp"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mica. Review it before you use it.

Capability tags behind 1 rule
  • mcp__mica__validate_whitepaper outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.tooloracle/mica/verify?hash=5a20fbd87343a244180e0c3696e77889e7ea2f9d593334763f83629579d69a0e" | jq -e '.changed == false'

Pinned hash 5a20fbd87343, from Nov 21, 2026, 16:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.tooloracle/mica/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.tooloracle/mica
[![Anlyon Radar](https://radar.anlyon.com/badge/io.tooloracle/mica.svg)](https://radar.anlyon.com/servers/io.tooloracle/mica)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.

mica MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the mica MCP server safe?

No scan can promise that. What its definitions show: 24 tools, 18 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the mica MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the mica MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the mica MCP server have?

24 tools: 18 write, 6 read. readiness_check, gap_report, assess_token, create_entity, audit_trail, health_check, issuer_profile, entity_ampel and 16 more.

Does the mica MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the mica MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): validate_whitepaper.

Has the mica MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.