MODEL CONTEXT PROTOCOL

ATP + MCP

MCP moves context and tool calls. ATP can add portable agent identity and verifiable trust evidence around that interaction without replacing MCP.

INTEGRATION APPROACH

Build at the boundary.

01

Identify the agent or service at the boundary.

02

Evaluate issuer authority, credential status, and applicable policy.

03

Record an auditable decision in the host application.

Implementation status

The binding and cross-protocol conformance work are in development. Treat this as an integration pattern, not a promise that every MCP call is automatically verified.

Inspect ATP Core →Start with the SDK →All integration patterns →

Community Group drafts are not endorsed by W3C and are not W3C Standards.