MCP server · free · no key

Ask your AI assistant about any MiCA-registered company.

Plug the EU crypto-asset registers straight into Claude, ChatGPT, Cursor or any Model Context Protocol client. Is this exchange authorised? Who supervises it? Where can it passport? Your assistant answers from ESMA and every national register, with a link to the source page. No account, no key, nothing to install.

https://mica.seqlense.com/mcp

Streamable HTTP transport · 10 tool calls/minute and 500/day per IP. Need more, or bulk data? Use the keyed JSON API.

Connect it

Any client that speaks remote MCP works. The common ones:

# claude.ai or Claude Desktop: Settings → Connectors → Add custom connector
Name: Seqlense MICA
URL:  https://mica.seqlense.com/mcp

claude mcp add --transport http seqlense-mica https://mica.seqlense.com/mcp

// .cursor/mcp.json or .vscode/mcp.json
{
  "mcpServers": {
    "seqlense-mica": { "url": "https://mica.seqlense.com/mcp" }
  }
}

# stdio-only clients: bridge with mcp-remote
npx mcp-remote https://mica.seqlense.com/mcp

# or talk JSON-RPC directly
curl -s https://mica.seqlense.com/mcp -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_mica_authorisation","arguments":{"name":"Revolut"}}}'

Tools

Six read-only tools. Every result carries the url of its public page, so answers come with a citation.

`check_mica_authorisation`

Name, brand or LEI in; matching register entries out, each with a plain verdict: authorised CASP, token issuer, on the ESMA warning list, or not found.

`search_mica_entities`

Faceted search by text, register (CASP, EMT, ART, NCASP), country, status, MiCA service A–J and passporting state.

`get_mica_entity`

The full record: services, passporting, competent authority, GLEIF company data (legal form, address, parent) and change history.

`list_early_detections`

Providers already in a national register but not yet in the consolidated ESMA list. New authorisations, first.

`list_recent_mica_changes`

The register changelog, newest first: new authorisations, withdrawals, status changes, warning-list additions.

`get_mica_stats`

Totals by register, status and country, the MiCA service legend and how fresh the data is.

Try asking

“Is Binance authorised under MiCA anywhere in the EU?”
“Which crypto custodians are licensed in France and can passport into Germany?”
“List the e-money token issuers and who supervises each one.”
“What changed in the MiCA registers this week?”
“Is this website on the ESMA warning list?”

Questions

Is it really free, with no sign-up?

Yes. The data is public regulator data, and an assistant should be able to check a licence without anyone creating an account. Calls are metered per IP (10/minute, 500/day) to keep it healthy for everyone.

Where does the data come from?

The ESMA interim MiCA register plus every national competent authority register in the EU/EEA, deduplicated and LEI-verified against GLEIF. See about the data. It is not legal advice; verify against the competent authority before relying on a result.

Which protocol versions are supported?

MCP 2025-06-18, 2025-03-26 and 2024-11-05 over Streamable HTTP, stateless, JSON responses. No session and no server-sent events are needed.

I need more calls or the whole dataset.

Use the JSON API: a free key gives you higher page sizes, filters, the changelog and CSV export.