OpenChainGraph Suite · ART-602 · MiCA Registers

MiCA Register Presence Check

Answers one question, and only that question: was this entity present in the register extract you captured, on the date you captured it? You paste the extract, name which ESMA register it came from, give the entity identifier and give the capture date. The page digests the pasted bytes exactly as pasted, searches them, and writes a single dated sentence you can quote.

Presence as of a date, never authorisationPaste-in only, zero lookupsNo clock: the retrieval date is yours
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
What This Does and Does Not Prove

A match proves a line carrying your identifier was in the text you pasted. It is not authorisation, not licensing, not registration in good standing, and not a statement about today. A no-match proves absence from that same pasted text and nothing more: a partial page, a filtered export, the wrong register, or an identifier the register spells differently would each read the same way. Nothing here proves the extract came from ESMA, was unmodified, or was captured on the date you supplied. The digest pins the bytes that were checked; it does not attest where they came from.

This page never fetches anything, ships no copy of either register, and has no clock. retrieval_date is your input because a machine clock would date the run rather than the capture, and those are different facts.

The Four Facts the Verdict Is Built From
Names the register in the verdict sentence. No default is inferred.
LEI or register ID, compared as a literal string against the extract's own cells.
ISO YYYY-MM-DD. The date you captured the extract, never read from a clock.
Free text recording where the extract came from. Echoed into the receipt, never checked.
Digested exactly as pasted. Quoted fields may contain the delimiter, line breaks and doubled quotes. Oversized extracts are refused rather than truncated.
Header name or a 0-based index. Leave blank to compare every cell. An unresolvable column is raised, never quietly widened back to an any-cell search.
register_snapshot_digest
Matched rows (verbatim)
Judgment required
Execution Hash (SHA-256)
Where This Sits Beside the Other MiCA Surfaces
art-512 Check MiCA Reserve Disclosurea published reserve disclosure against your declared terms
art-102 Crypto-Asset White Paper Linterstructural lint of a white paper, not of the register of white papers
332 MiCA CASP Authorization Checkerthe authorisation question this node refuses to answer
mica-register-crosscheckthis node beside the reserve and attestation recomputes







  

    
Ask your agent

    
  

  
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.

  
Run the AINumbers MCP tool `check_mica_register_presence`. Task: Report whether a named entity was present in a pasted ESMA MiCA register extract as of a caller-supplied retrieval date, pinned by a SHA-256 digest of the pasted bytes.
Call it with arguments: {"policy_parameters":{"register_type":"white_paper","entity_identifier":"984500XXXXXXXXXXXX02","register_extract":"lei,issuer_name,crypto_asset_name,notification_date,home_member_state\n984500XXXXXXXXXXXX01,Example Issuer SA,EXAMPLE-EURO-TOKEN,2026-01-15,FR\n984500XXXXXXXXXXXX02,Second Issuer NV,SECOND-TOKEN,2026-02-03,NL\n984500XXXXXXXXXXXX03,Third Issuer GmbH,THIRD-TOKEN,2026-03-21,DE\n","retrieval_date":"2026-08-11","register_source_ref":"ESMA crypto-asset white paper register export (synthetic sample)","delimiter":",","header_row":true,"match_column":"lei","case_sensitive":true}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-602-mica-register-presence-check.html#p=v1.H4sIAAAAAAAA_wE4Asf9eyJyZWdpc3Rlcl90eXBlIjoid2hpdGVfcGFwZXIiLCJlbnRpdHlfaWRlbnRpZmllciI6Ijk4NDUwMFhYWFhYWFhYWFhYWDAyIiwicmVnaXN0ZXJfZXh0cmFjdCI6ImxlaSxpc3N1ZXJfbmFtZSxjcnlwdG9fYXNzZXRfbmFtZSxub3RpZmljYXRpb25fZGF0ZSxob21lX21lbWJlcl9zdGF0ZVxuOTg0NTAwWFhYWFhYWFhYWFhYMDEsRXhhbXBsZSBJc3N1ZXIgU0EsRVhBTVBMRS1FVVJPLVRPS0VOLDIwMjYtMDEtMTUsRlJcbjk4NDUwMFhYWFhYWFhYWFhYWDAyLFNlY29uZCBJc3N1ZXIgTlYsU0VDT05ELVRPS0VOLDIwMjYtMDItMDMsTkxcbjk4NDUwMFhYWFhYWFhYWFhYWDAzLFRoaXJkIElzc3VlciBHbWJILFRISVJELVRPS0VOLDIwMjYtMDMtMjEsREVcbiIsInJldHJpZXZhbF9kYXRlIjoiMjAyNi0wOC0xMSIsInJlZ2lzdGVyX3NvdXJjZV9yZWYiOiJFU01BIGNyeXB0by1hc3NldCB3aGl0ZSBwYXBlciByZWdpc3RlciBleHBvcnQgKHN5bnRoZXRpYyBzYW1wbGUpIiwiZGVsaW1pdGVyIjoiLCIsImhlYWRlcl9yb3ciOnRydWUsIm1hdGNoX2NvbHVtbiI6ImxlaSIsImNhc2Vfc2Vuc2l0aXZlIjp0cnVlfULrrUA4AgAA