UCP Transports: REST, MCP and A2A
Compare the transport declarations a UCP profile can use and the discovery data each integration must expose.
Why it matters
UCP service discovery can advertise transport-specific bindings, including REST, MCP and A2A. The business profile communicates endpoint and schema or protocol references so a platform can understand how to interact.
How it works
A2A transport uses an agent-card endpoint, while REST and MCP expose their own service endpoints and schema descriptions. Transport choice does not replace capability negotiation.
Practical takeaway
Keep endpoint declarations HTTPS, versioned and truthful. A declared transport should not be published until the associated endpoint actually implements the expected protocol behavior.
Use the tools, then verify against the protocol or platform you actually implement.Browse all tools