A2A Passport — one GTIN, one call, everything GSC knows, signed
RemoteAbout A2A Passport — one GTIN, one call, everything GSC knows, signed
A2A Passport, called A2A Record in the README, issues signed records for product GTINs or retail banners using live data from GSC hubs. It is for trade participants who need to inspect source, market clearance, and signature validity; it does not infer missing information.
Key features
- 01Retrieve records by GTIN or banner
- 02Read live data from GSC hubs
- 03List and filter registered records
- 04Verify signatures, version chains, and timestamps
Use cases
- 01Inspect hub records and clearance for a product
- 02Validate a record signature and version chain
- 03Filter registered records by market or type
MCP support
It exposes three tools—get_record, list_records, and verify_record—over streamable HTTP for MCP clients to retrieve and validate signed records.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.a2a-passport.ai/mcpclaude mcp add --transport http greencore-solutions-a2a-passport https://mcp.a2a-passport.ai/mcp{"mcpServers":{"greencore-solutions-a2a-passport":{"type":"http","url":"https://mcp.a2a-passport.ai/mcp"}}}Open in Cursor{"servers":{"greencore-solutions-a2a-passport":{"type":"http","url":"https://mcp.a2a-passport.ai/mcp"}}}Open in VS Code{"mcpServers":{"greencore-solutions-a2a-passport":{"type":"http","url":"https://mcp.a2a-passport.ai/mcp"}}}{"mcpServers":{"greencore-solutions-a2a-passport":{"serverUrl":"https://mcp.a2a-passport.ai/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
3| Parameter | Type | Required | Description |
|---|---|---|---|
| kind | any | No | |
| subject | string | Yes |
Details
From the project READMEA2A Record — one GTIN, one call, everything GSC knows, signed
The hubs are the records; A2A-Record.ai issues the record.
The hubs are the records; A2A-Record.ai issues the record. A record is a signed document for a product or a retail banner: where its record lives, where it is cleared, who lists it, where the money door is. Issued live from the GSC hubs, stamped every week. A2A Record is operated by GreenCore Solutions Corp.: one signed document per product (a Global Trade Item Number, GTIN) or retail banner, composed live from the GSC hubs — A2A Grocery, A2A Cosmetics, A2A Peptides, A2A Retailmedia and the compliance records — and signed (EdDSA). Three tools: get_record, list_records, verify_record. Every field is a hub's answer, word for word, with the door and the time it was read, or it is absent with a note: the record never infers. A product no hub holds gets no record. Reads are open; a verified, countersigned copy settles by x402. Artificial intelligence makes mistakes. A2A Record is an agentic information source, not a recommendation. No ads, ever. No rank for sale. Trade only.
A2A Record is built and run by GreenCore Solutions Corp. (github.com/greencore-solutions). This is the public connect kit, MIT.
The door
streamable-HTTP, stateless, server name a2a-record, door version 1.0.2, 3 tools (read from the wire)
- Endpoint:
https://mcp.a2a-record.ai/mcp— any client that speaks streamable-HTTP:{ "url": "https://mcp.a2a-record.ai/mcp", "transport": "streamable-http" } - Agent Card (signed):
https://a2a-record.ai/.well-known/agent-card.json - Key:
https://a2a-record.ai/.well-known/jwks.json(EdDSA, key ida2apass-2026-10) - No registration and no token: every read is open.
The tools
get_record— The signed record of a product (a Global Trade Item Number, GTIN) or a retail banner (market/banner, e.g. FR/Carrefour): which hub holds its record, where it is cleared, its compliance records, who lists it, where the payment door is. Read live from the GSC hubs on every call; the first call issues version 1. subject = a GTIN (8 to 14 digits) or market/banner; kind = gtin or banner (optional).list_records— The records on the register: ids, kinds, markets, versions and issue times, newest first. No bodies. Filter by kind (gtin or banner), market, or issued since a time; paginated.verify_record— Check a record: is the signature valid, is the chain of versions intact, how old is the stamp, was any section not read. Verifies from the published key at /.well-known/jwks.json.
The document
One envelope for both kinds (a product by its GTIN, or a retail banner as market/banner): record_id, kind, subject, issued_at, version, previous_version_hash, issuer, signature, delta, and the body.
Every field in the body is a hub's answer, word for word, with the door, the tool and the time it was read — or it is absent with a note. The record never infers.
- Current version:
https://a2a-record.ai/record/{id}.json - One version:
https://a2a-record.ai/record/{id}/v{n}.json - Record #1:
https://a2a-record.ai/record/gtin-03284230006408.json - The register (live counts):
https://a2a-record.ai/records/register.json
A product that no hub holds on its record gets no record.
Verify a record yourself
The signature is a detached JSON Web Signature (EdDSA) over the record without its signature field, keys sorted, compact JSON, UTF-8. examples/verify_record.py does it with the published key and nothing else.
The countersigned copy
Reading a record is free. A verified, countersigned copy settles at https://a2a-record.ai/api (x402, two accept entries). A record that is not on the register answers HTTP 403 and is not charged.
Examples
examples/generic_mcp_client.py— a stock client: lists the tools, reads record #1, verifies it on the door.examples/verify_record.py— fetches a record and the key over plain HTTP and verifies the signature offline.
Artificial intelligence makes mistakes. A2A Record is an agentic information source, not a recommendation. No ads, ever. No rank for sale. Trade only.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.