MCP.Market

A2A Passport — one GTIN, one call, everything GSC knows, signed MCP server

online · 100% uptime
by greencore-solutions·io.github.greencore-solutions/a2a-passport·v1.0.2

The hubs are the records; A2A-Passport.ai issues the passport.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed A2A Passport — one GTIN, one call, everything GSC knows, signed yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

A2A Passport — one GTIN, one call, everything GSC knows, signed tools (3)

write = sends, deletes, buys or posts
  • get_passportFree

    The signed passport 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 on the record, 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_passportsFree

    The passports 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_passportFree

    Check a passport: 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.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1263ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How A2A Passport — one GTIN, one call, everything GSC knows, signed compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,273 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
258 ms
faster than 53% of 30,037 servers

What its tools let an agent do: 3 read

Install A2A Passport — one GTIN, one call, everything GSC knows, signed in Claude Code, Cursor or VS Code

claude mcp add --transport http a2a-passport https://mcp.a2a-passport.ai/mcp
Add to Cursor

What the publisher says

From the A2A Passport — one GTIN, one call, everything GSC knows, signed repository's README, as published. We do not edit it. Read it on GitHub

A2A 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: getrecord, listrecords, 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 id a2apass-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): recordid, kind, subject, issuedat, version, previousversionhash, 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/genericmcpclient.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.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

A2A Passport — one GTIN, one call, everything GSC knows, signed: common questions

Is A2A Passport — one GTIN, one call, everything GSC knows, signed MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the A2A Passport — one GTIN, one call, everything GSC knows, signed safety report
How do I install A2A Passport — one GTIN, one call, everything GSC knows, signed?
It runs remotely at mcp.a2a-passport.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does A2A Passport — one GTIN, one call, everything GSC knows, signed need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is A2A Passport — one GTIN, one call, everything GSC knows, signed maintained?
The last commit was 27 days ago (2026-10-06). The latest release is v1.0.2.
Is A2A Passport — one GTIN, one call, everything GSC knows, signed up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does A2A Passport — one GTIN, one call, everything GSC knows, signed compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,273 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from greencore-solutions →