MCPA2A.dev / Specification
A2A v1.0.1 Agent Card & RFC 8785 JCS Spec
Exact schema fields, deterministic UTF-16 key ordering, and cryptographic fingerprinting required for verifiable agent-to-agent discovery.
1. Well-Known Discovery Contract
Every A2A v1.0.1 compliant agent publishes a static or signed JSON document at https://<host>/.well-known/agent-card.json with Content-Type: application/json:
{
"protocolVersion": "1.0.1",
"name": "Citation Verification Agent",
"url": "https://agent.example.com/a2a",
"version": "1.0.0",
"capabilities": { "streaming": true, "pushNotifications": false, "stateTransitionHistory": true },
"defaultInputModes": ["application/json", "text/plain"],
"defaultOutputModes": ["application/json"],
"skills": [
{
"id": "verify_citation",
"name": "Verify Citation",
"description": "Checks live HTTP status, canonical tags, and structured claims for one URL.",
"tags": ["verification", "citations"]
}
]
}
2. RFC 8785 JCS Canonicalization Rules
- No insignificant whitespace: strip spaces/newlines outside string literals.
- Deterministic object key sorting: sort all object keys recursively by UTF-16 code units.
- Exact number serialization: follow ES6
Number.prototype.toString()representation so signatures match across Python, Go, Rust, and JS. - SHA-256 fingerprint: hash the UTF-8 bytes of the JCS canonical string to produce an immutable Agent Card digest before attaching JWS/Ed25519 signatures.
Interoperability Cluster
Validate upstream MCP 2026-07-28 tool manifests on modelcontextpro.dev →