Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for peptides.What this is
The registry holds what the door answers from: one substance record per molecule, one presentation record per authorised presentation, one rule set per jurisdiction, and the dated enforcement events. Every field is {value, source_url, read_by, read_at, state}; a value with no source page does not exist here. The counts on this page are produced from the records at build time, never typed.
The records table is never rendered as a page. Records are served signed, one file each, and resolved by identifier through the resolver below; the door serves the same records through its twenty tools.
Register metrics
- Pathway rows by jurisdiction — CA 68 · CH 45 · EU 65 · JP 20 · KR 54 · US 81
- Rule sets — CA v1.2-2026-09-17 (100 rules) · CH v1.2-2026-09-17 (80 rules) · EU v1.2-2026-09-17 (98 rules) · GB v1.2-2026-09-17 (34 rules) · JP v1.2-2026-09-17 (54 rules) · KR v1.2-2026-09-17 (88 rules) · MX v1.2-2026-09-17 (32 rules) · SG v1.2-2026-09-17 (34 rules) · US v1.2-2026-09-17 (118 rules)
- Enforcement events — 106 dated, URL'd documents on the watch
- Door — mcp.a2a-peptides.ai/mcp · health /health.json
Resolver
A substance record resolves by Unique Ingredient Identifier (UNII); the index lists every record with its identifier, name and jurisdictions.
- /records/index.json — the index of signed substance records (177)
/records/substance/<UNII>.json— one signed record, ES256 under kid a2ap-2026-09, verify against the keyring- Example: /records/substance/53AXN4NNHX.json (semaglutide)
- Presentation records and rule sets resolve through the door's tools get_item and get_pathway_status; the metered truth tools settle through peptides-x402.ai.
Contact
A person reads the form.
The form is the only human door on this surface.