OpenChainGraph Suite · OCG v0.8.13 · Digital-Asset Rails

MiCA Register Cross-Check

Note (dated 2026-08-11): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site.

Four dated readings about one MiCA-authorised issuer, produced independently and laid beside each other by whoever is asking. Was the entity present in the register extract you captured, on the date you captured it? Does its published reserve disclosure hold up against the terms you are holding it to? And do two separate recomputes of the stablecoin side agree with each other? Each stage emits its own hash-anchored artifact. Nothing here certifies anything.

OpenChainGraph · 4 Nodes, Linear compliance mandate Hash-Anchored §4 Presence Is Dated, Never Authorisation Client-Side · Zero PII · Zero Network Read
Not a compliance certification, not an audit opinion, not a solvency opinion, and not a regulatory filing. Every figure and every document below is SUPPLIED by the reader and treated as asserted: no stage fetches a register, an issuer disclosure, a price, or anything else. Stage 1 is the one to read most carefully. Presence in a register extract is a dated fact about the text that was pasted, never authorisation and never a statement about today; absence is absence from that text, which a partial page, a filtered export or an identifier the register spells differently would each produce.
Workflow Stages · 4 Nodes · Linear
1 ROOT node
MiCA Register Presence Check art-602-mica-register-presence-check
Stage 1, root: whether a named entity was present in a pasted ESMA MiCA register extract, the register of crypto-asset white papers or the register of authorised crypto-asset service providers, as of the reader's own capture date, with the pasted bytes pinned by register_snapshot_digest. The reading is a dated fact about that snapshot. It is never an authorisation or current-status determination.
MCP Call · check_mica_register_presence
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_mica_register_presence",
    "arguments": {
      "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\n",
      "retrieval_date": "2026-08-11",
      "match_column": "lei"
    }
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
2 STAGE 2 node
Check MiCA Reserve Disclosure art-512-check-mica-reserve-disclosure
Stage 2: the same issuer's published reserve disclosure read against the composition, concentration, segregation and publication-cadence terms the reader declares, with coverage arithmetic in exact fixed point. Every rule tested here is the reader's own, transcribed from the terms the issuer is being held to, never a bundled template.
MCP Call · check_mica_reserve_disclosure
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_mica_reserve_disclosure",
    "arguments": {
      "issuer_id": "ISSUER-DEMO-01",
      "token_type": "EMT",
      "as_of": "2026-06-30",
      "tokens_in_circulation": "500000000",
      "reserve_components": [
        {"asset_class": "bank_deposit", "amount": "205000000", "custodian_type": "credit_institution", "segregated": true}
      ],
      "declared_rules": {"eligible_asset_classes": ["bank_deposit"], "cadence_days": 31}
    }
  },
  "id": 2
}
https://mcp.ainumbers.co/mcp
3 STAGE 3 node
GENIUS Act Reserve Attestation Pre-Check art-06-genius-act-reserve-attestation
Stage 3: a GENIUS Act reserve-attestation precheck over the reader's declared reserve and attestation figures, computed independently of Stage 2 from its own declared inputs. A second reading of the same subject, reached by a different route, is what makes a divergence visible.
MCP Call · precheck_reserve_attestation
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "precheck_reserve_attestation",
    "arguments": {
      "issuer_name": "SYNTHETIC-ISSUER",
      "outstanding_tokens": 500000000,
      "total_reserves_usd": 512500000
    }
  },
  "id": 3
}
https://mcp.ainumbers.co/mcp
4 TERMINAL node
GENIUS Act Reserve-Disclosure Conformance Monitor art-582-genius-reserve-disclosure-conformance-monitor
Stage 4, terminal: GENIUS-shaped conformance over the published monthly reserve disclosure, covering coverage arithmetic and attestation presence and timeliness, each with its own verdict of MET, NOT_MET or INDETERMINATE. Permitted-asset composition stays out of scope while no final implementing rule text exists to check it against.
MCP Call · check_genius_reserve_disclosure_conformance
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_genius_reserve_disclosure_conformance",
    "arguments": {
      "report_period": "2026-07",
      "period_end_date": "2026-07-31",
      "outstanding_tokens_reported": 500000000,
      "token_price": 1,
      "total_reserves_usd": 512500000,
      "attestation_present": true,
      "attestation_date": "2026-08-14"
    }
  },
  "id": 4
}
https://mcp.ainumbers.co/mcp
What a Divergence Between These Four Readings Does and Does Not Mean

If Stage 1 finds no match while Stages 2 to 4 read cleanly, the likeliest explanations are mundane: the wrong register was pasted, the extract was a filtered page, or the identifier is spelled differently in the register than in the disclosure. None of those is evidence about the issuer, and this chain deliberately says nothing about which explanation applies.

If Stages 3 and 4 disagree with each other over the same declared figures, that disagreement is worth reading, because both are recomputes of the same subject from the same reader-declared numbers by different routes. What it is not is a finding: the reader's own inputs, and the rules the reader declared, are equally capable of producing it.

Fence
Register datapasted by the reader, never fetched
Retrieval datea caller input, never a clock read
Refresh cadencenone, by design
Verdict scopepresence in a dated snapshot
Out of scopeauthorisation, status, solvency, certification