# A2A Passport — one GTIN, one call, everything GSC knows, signed (remote · mcp.a2a-passport.ai)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `mcp.a2a-passport.ai`: 76/100 (this document), [markdown](https://verifymcp.io/servers/greencore-solutions-a2a-passport/mcp.md), [page](https://verifymcp.io/servers/greencore-solutions-a2a-passport/mcp)

## Channel facts

- Endpoint: `https://mcp.a2a-passport.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 421 tokens (~140/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the A2A Passport — one GTIN, one call, everything GSC knows… MCP server?

A2A Passport — one GTIN, one call, everything GSC knows… is a hosted endpoint at https://mcp.a2a-passport.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http greencore-solutions-a2a-passport 'https://mcp.a2a-passport.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "greencore-solutions-a2a-passport": {
      "url": "https://mcp.a2a-passport.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "greencore-solutions-a2a-passport": {
      "type": "http",
      "url": "https://mcp.a2a-passport.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.greencore-solutions-a2a-passport]
url = "https://mcp.a2a-passport.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "greencore-solutions-a2a-passport": {
      "type": "remote",
      "url": "https://mcp.a2a-passport.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add greencore-solutions-a2a-passport --url 'https://mcp.a2a-passport.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  greencore-solutions-a2a-passport:
    url: "https://mcp.a2a-passport.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "greencore-solutions-a2a-passport": {
      "Transport": "http",
      "Url": "https://mcp.a2a-passport.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add greencore-solutions-a2a-passport -t streamable-http -u 'https://mcp.a2a-passport.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "greencore-solutions-a2a-passport": {
      "type": "http",
      "url": "https://mcp.a2a-passport.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 71, 0)

- [security] Tool “get_passport” rewrote its description, which is the text the model reads

### 2026-10-12 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 23. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 70)

First indexed and scored.

## MCP tools (3)

### `get_passport` (~124 tokens)

Get Passport

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).

Input parameters:

- `kind`
- `subject` (string, required)

### `list_passports` (~81 tokens)

List Passports

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.

Input parameters:

- `kind`
- `limit` (integer)
- `market`
- `offset` (integer)
- `since`

### `verify_passport` (~65 tokens)

Verify Passport

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.

Input parameters:

- `passport_id` (string, required)
- `version`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/greencore-solutions-a2a-passport/mcp#diagnostics

## Score history

- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 71
- 2026-10-13: 71
- 2026-10-12: 71
- 2026-10-10: 70

## Common questions

### What is the A2A Passport — one GTIN, one call, everything GSC knows… MCP server?

A2A Passport — one GTIN, one call, everything GSC knows… is an MCP server listed in the public MCP registry as io.github.greencore-solutions/a2a-passport. The hubs are the records; A2A-Passport.ai issues the passport. This page covers its hosted endpoint (https://mcp.a2a-passport.ai/mcp).

### Is the A2A Passport — one GTIN, one call, everything GSC knows… MCP server safe to use?

A2A Passport — one GTIN, one call, everything GSC knows… scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the A2A Passport — one GTIN, one call, everything GSC knows… MCP server expose?

A2A Passport — one GTIN, one call, everything GSC knows… exposes 3 tools: get_passport, list_passports, verify_passport. Their descriptions and schemas cost roughly 270 tokens of context every time the server is loaded.

### Does the A2A Passport — one GTIN, one call, everything GSC knows… MCP server require authentication?

No. We connected to A2A Passport — one GTIN, one call, everything GSC knows… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the A2A Passport — one GTIN, one call, everything GSC knows… MCP server still maintained?

A2A Passport — one GTIN, one call, everything GSC knows… is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.a2a-passport.ai/mcp
- Repository: https://github.com/greencore-solutions/a2a-passport
- Website: https://a2a-passport.ai/
- Changelog RSS feed: https://verifymcp.io/servers/greencore-solutions-a2a-passport/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/greencore-solutions-a2a-passport/mcp.json
- HTML version of this page: https://verifymcp.io/servers/greencore-solutions-a2a-passport/mcp