MCPA2A.dev — Agent Card & Strict Validator
The protocol bridge between MCP 2026-07-28 tool surfaces and A2A v1.0.1 agent delegation. Validate an Agent Card, canonicalize it per RFC 8785, and fingerprint it with SHA-256 — deterministic output, zero egress.
A2A v1.0.1 Agent Card Validator + JCS + SHA-256
Paste an A2A Agent Card. The validator checks required v1.0 fields, canonicalizes it per RFC 8785 (JCS), and fingerprints it with WebCrypto SHA-256 — all locally.
Paste an Agent Card and press Validate.
Validation rules
- Required fields:
name,url(absolute http(s)),version. skillsmust be an array;capabilitiesan object.- Empty
authentication.schemesproduces a note — declare a scheme or omit the block. - Canonicalization follows RFC 8785: lexicographic UTF-16 key ordering, minimal number and string serialization.
- SHA-256 fingerprint via WebCrypto — the same digest peers will compute for card pinning.
JCS + fingerprinting
Two agents holding the same Agent Card should agree on one byte sequence. RFC 8785 removes JSON ambiguity (key order, whitespace, number formatting), and the SHA-256 digest gives you a stable fingerprint for /.well-known/agent-card.json pinning and change detection.
Cluster
Sibling properties in the MCP/A2A protocol bridge and guardrail runtimes.
MCP Context ProMCP↔A2A HubA2A→MCP CompilerOverwatcherTypedBotsStrictBotsRunWeights · ForwardRouterReverseHarnessLinkProducers