mica
Server Details
MiCAOracle — 24 tools for EU MiCA stablecoin compliance: peg, reserves, attestations.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.4/5 across 24 of 24 tools scored. Lowest: 2.5/5.
Most tools target distinct actions or resources, but some overlap exists (e.g., assess_token vs. assess_entity, readiness_check vs. generate_report) that could cause minor confusion. Descriptions help differentiate, but a few boundaries are fuzzy.
Naming patterns are mixed: some use verb_noun (assess_token, create_entity), others noun_verb (bridge_approve, bridge_resolve), and some noun_noun (audit_trail, bus_status). The lack of a consistent convention may confuse agents when choosing tools.
At 24 tools, the server covers a broad domain (MiCA compliance). While slightly heavy, each tool serves a clear purpose and the count is justified by the complexity of regulatory requirements.
The tool set is remarkably comprehensive, covering entity management, token assessment, compliance reporting, bridge workflows, regulatory monitoring, insider trading, STOR, whitepaper validation, and audit trails. No obvious gaps for the stated domain.
Available Tools
24 toolsarticle_statusInspect
Detailed Ampel for a specific MiCA article with check conditions.
| Name | Required | Description | Default |
|---|---|---|---|
| article | No | e.g. Art. 35 | |
| entity_id | No | Entity ID | |
| token_symbol | No | Token |
assess_entityInspect
Assess ALL tokens for an entity in one call. Runs live FeedOracle assessment for each linked token.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity ID (optional) |
assess_tokenInspect
Run LIVE MiCA assessment via FeedOracle mica_full_pack. Evaluates 18 checks, updates Ampel.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity ID (optional) | |
| token_symbol | No | Token e.g. USDC, USDT, EURC, RLUSD |
audit_trailInspect
Chain-linked audit log with integrity check.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max entries | |
| entity_id | No | Entity ID (optional) |
bridge_approveInspect
Approve or reject a bridge resolution. Approval upgrades Ampel to GREEN.
| Name | Required | Description | Default |
|---|---|---|---|
| reject | No | Set true to reject | |
| approved_by | No | Name + role of approver | |
| resolution_id | No | Resolution ID from bridge_resolve | |
| rejection_reason | No | Reason for rejection |
bridge_resolveInspect
Start bridge resolution for a MiCA gap. Generates template (issuer engagement, risk acceptance, token replacement, monitoring upgrade).
| Name | Required | Description | Default |
|---|---|---|---|
| check_id | No | Check ID e.g. art35_c1, art24_c3 | |
| entity_id | No | Entity ID | |
| expiry_days | No | Days until expiry (default 30) | |
| token_symbol | No | Token e.g. USDC |
bridge_statusInspect
Show all bridge resolutions for an entity/token.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity ID | |
| token_symbol | No | Filter by token |
bus_statusInspect
Oracle Event Bus status: events, cross-refs, connected oracles.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity ID for cross-refs |
create_entityInspect
Register a new regulated entity.
| Name | Required | Description | Default |
|---|---|---|---|
| lei | No | LEI | |
| name | No | Entity name | |
| entity_type | No | CASP, Bank, Verwahrer | |
| jurisdiction | No | DE, AT |
eidas_timestampInspect
eIDAS-qualified timestamp integration status and assessment. Maps FeedOracle ES256K signatures to EU trust framework (eIDAS Art. 25, 41-42).
| Name | Required | Description | Default |
|---|---|---|---|
| action | No | status, assess, or reference | |
| entity_id | No | Entity ID | |
| token_symbol | No | Token for assess action |
entity_ampelInspect
Aggregate MiCA Ampel for an entity across ALL tokens it custodies. Shows per-token breakdown + overall score.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity ID (optional, uses first) |
entity_listInspect
List all registered entities.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
freshness_checkInspect
Expire stale evidence. Downgrades GREEN→YELLOW if evidence older than max_age_days. Run daily.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity ID | |
| max_age_days | No | Max evidence age in days (default 7) | |
| token_symbol | No | Token (optional) |
gap_reportInspect
MiCA compliance gaps: RED/YELLOW/GREY with priority and actions.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity ID (optional) | |
| token_symbol | No | Token |
generate_reportInspect
Generate MiCA compliance report for a token. Full article breakdown, evidence, bridges, audit.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity ID | |
| token_symbol | No | Token e.g. USDC |
health_checkInspect
Server + DB status.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
insider_escalationInspect
Inside Information classification, delay and disclosure workflow per MiCA Art. 87-88 and Implementing Regulation 2024/2861. AI-assisted with mandatory human sign-off.
| Name | Required | Description | Default |
|---|---|---|---|
| action | No | classify, delay, or status | |
| entity_id | No | Entity ID | |
| event_type | No | reserve_breach, peg_deviation, regulatory_action, management_change, material_event, partnership, technical_upgrade | |
| approved_by | No | Person signing the decision | |
| delay_reason | No | Reason for delay (Art. 88(2)) | |
| event_description | No | Description of the event |
issuer_listInspect
List all known token issuers with MiCA authorization status and tokens.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
issuer_profileInspect
Issuer profile with all tokens and aggregate MiCA Ampel. Shows authorization status, headquarters, token scores.
| Name | Required | Description | Default |
|---|---|---|---|
| issuer_id | No | Issuer ID or name e.g. circle, tether, ripple |
link_tokenInspect
Link a token to an entity for monitoring.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity ID | |
| relationship | No | custody, trading, settlement | |
| token_symbol | No | Token e.g. USDC |
mica_watchdogInspect
Monitor ESMA/EBA/BaFin for MiCA regulatory changes. Returns monitored sources and alerts.
| Name | Required | Description | Default |
|---|---|---|---|
| days_back | No | Check items from last N days (default 7) |
readiness_checkInspect
Full MiCA readiness score + Ampel per article for a token. GREEN/YELLOW/RED/GREY for 10 articles, score 0-100.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity ID (optional) | |
| token_symbol | No | Token e.g. USDC, USDT, EURC |
stor_workflowInspect
Suspicious Transaction and Order Report (STOR) workflow per MiCA Art. 92. AI-assisted detection with mandatory human sign-off for 'reasonable suspicion'.
| Name | Required | Description | Default |
|---|---|---|---|
| action | No | detect, escalate, or status | |
| entity_id | No | Entity ID | |
| approved_by | No | Surveillance Officer signing the escalation | |
| description | No | Signal description | |
| signal_type | No | wash_trading, spoofing, insider_trading, market_manipulation, front_running, pump_dump, unusual_volume, concentration |
validate_whitepaperInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Whitepaper URL (optional) | |
| format | No | ixbrl or xhtml | |
| token_symbol | No | Token e.g. USDC, USDT, EURC |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!