AIP: Agent Identity Protocol for Verifiable Delegation Across MCP and A2A
arXiv cs.AI / 3/27/2026
💬 OpinionDeveloper Stack & InfrastructureIdeas & Deep AnalysisModels & Research
Key Points
- The paper highlights that existing Model Context Protocol (MCP) tool calling and Agent-to-Agent (A2A) delegation lack mechanisms to verify agent identity, and a scan of ~2,000 MCP servers found no authentication.
- It proposes AIP (Agent Identity Protocol) using Invocation-Bound Capability Tokens (IBCTs) that combine public-key verifiable identity, holder-side attenuation, chained expressive policy, transport binding across MCP/A2A/HTTP, and provenance-oriented completion records.
- IBCTs support two wire formats: compact mode using a signed JWT for single-hop delegation, and chained mode using a Biscuit token with Datalog policies for multi-hop delegation.
- Reference implementations are provided in Python and Rust with cross-language interoperability, and performance tests show very low verification cost (≈0.049–0.189ms) and small deployment overhead (≈0.22ms in real MCP-over-HTTP; ≈2.35ms in a multi-agent Gemini 2.5 Flash setup).
- In adversarial testing (600 attack attempts), AIP achieved a 100% rejection rate and uniquely detected delegation-depth violations and audit-evasion attempts that plain JWT or unsigned approaches missed.
Related Articles
I Extended the Trending mcp-brasil Project with AI Generation — Full Tutorial
Dev.to
The Rise of Self-Evolving AI: From Stanford Theory to Google AlphaEvolve and Berkeley OpenSage
Dev.to
AI 自主演化的時代來臨:從 Stanford 理論到 Google AlphaEvolve 與 Berkeley OpenSage
Dev.to
Most Dev.to Accounts Are Run by Humans. This One Isn't.
Dev.to
Neural Networks in Mobile Robot Motion
Dev.to