Every product on the shelf, watched weekly.

Coverage is a firm's list of issuers held against the record: each sweep, what changed on every name — filings, results, holders, auditors, going-concern notes — dated and sourced. Built for the duty a dealer cannot decline: know every product on the shelf, continuously. Twelve markets, one list.

Toronto first: investment dealers and wealth platforms under CIRO carry KYP, every product on the shelf known continuously and the file that proves it; Coverage is that file, held against the Canada node. London next: brokers, wealth managers and platforms under the FCA product governance rules (PROD) hold the same list against the UK node. Then the other nine markets, one list.

Scope

1.1

Unit: a coverage list — the issuers a firm shelves, by identifier, across any market on the roster.

1.2

Motion: weekly per node (the sweep clock of each market); one delta per name per sweep.

1.3

State: the sweep motion is armed (ORDER-020 §10); the coverage-list product is offered under the Dealer MCP access licence.

What a coverage list is

2.1

A list of identifiers (ticker with exchange, ISIN or LEI) a firm holds against the record.

2.2

Each identifier resolves to one record on one node; a dual listing resolves to two records, each in its own jurisdiction.

2.3

The list is the firm's; the record is the estate's. Nothing about the list leaves the region the firm's agents call.

What a weekly delta contains

3.1

New disclosure events since the last sweep, typed: results · agm_egm · director_change · directors_dealings · major_holder · takeover · prospectus · halt_suspension · corporate_news · ad_hoc · regulatory_filing · register_change.

3.2

Identity fields that changed between drops (name, auditor, registrar, fiscal period, registration status), with the old and new value and the source of each.

3.3

Going-concern language where the annual report carries it, as filed.

3.4

Gaps opened or closed on the record.

3.5

The drop date and the record version on every line.

The duty by jurisdiction

Duty doors and getissuer

4.1

getissuer.ai — the issuer record for any market, one door.

4.2

agent-kyp.ai — Know Your Product (KYP), Canada

4.3

agent-prod.ai — PROD / Consumer Duty, UK

4.4

agent-mifid.ai — MiFID II product governance, Germany · France · Netherlands

4.5

agent-finsa.ai — Financial Services Act (FinSA), Switzerland

4.6

agent-ddo.ai — Design and Distribution Obligations (DDO), Australia

4.7

agent-regbi.ai — Regulation Best Interest (Reg BI), United States

Access

5.1

Apex door (MCP, streamable-http, no auth): https://mcp.getissuer.ai/mcp — routes by identifier to the node that holds the name

5.2

Apex Agent Card (A2A): https://agent.getissuer.ai/.well-known/agent-card.json

5.3

Tools: resolve_issuer · get_record · list_aliases · list_events_since · list_nodes

5.4

Regional doors: mcp.<node>-cm-kg.ai/mcp, answers scoped to the node; descriptors at /mcp.json and /openapi.json

5.5

Registry entry: registry.modelcontextprotocol.io · io.github.allooloo/cm-kg

5.6

Coverage lists ride on list_events_since per identifier and on the Numbers Log per node; the list itself is held by the firm.

Provenance

6.1

Every field carries its source URL, the reader (registry, exchange list, filing tag or named engine) and a state (sourced · filled · confirmed); none is served without source and read date.

6.2

Public-record only: no prices, quotes or licensed market data; blank stays blank; nothing inferred.

6.3

Records are versioned and never deleted; the record as_of and the field read dates are separate fields.

6.4

"Confirmed" is the word; signing is reserved for CMR (cm-record.org) and is not yet in service.

Estate

7.1

One door per market on the roster, each in its own Azure region, records stored and served in the issuer's jurisdiction; the apex holds an index only and forwards; no fallback across borders.

7.2

Hong Kong: a beacon at Width 0, local partner wanted, no door.

source: list_nodes at https://mcp.getissuer.ai/mcp, read at render

Machine kit

8.1

/llms.txt · /facts.json · /.well-known/agent-card.json · /.well-known/security.txt · /sitemap.xml · /robots.txt

8.2

Headers on every response: Content-Security-Policy (strict), Strict-Transport-Security, X-Content-Type-Options, Referrer-Policy, X-Frame-Options, X-CMR-Node, X-CMR-As-Of, X-CMR-Version, X-CMR-Source, X-CMR-Operator, X-Surface-Version.

Contact Us