Skip to content

io.tooloracle/mica

by tooloracle.io · remote · no sign-in to list tools · v1.0.0 · published by io.tooloracle

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

Changes · 18

24 tools: 18 change things and 6 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

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 6Claude Code: allow
  • 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.No findings

    Why it is in this group

    • The name "validate_whitepaper" says "validate": a word for reading.
    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.

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/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, 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",
      "mcp__mica__validate_whitepaper"
    ],
    "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__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. It assumes the server is installed as mica. Review it before you use it.