Discovery, coordination, tool access, and identity in open agent protocols and standards research.
Interoperability begins with practical questions: how does an agent find a counterpart, establish a basis for communication, and reach the resources needed to complete a task? Recent announcements from protocol stewards separate these concerns into agent coordination, access to tools and data, and work on identity and authentication. Reading those concerns together offers a way to compare approaches without assuming that every protocol addresses the whole problem.
Consider two independently operated agents asked to cooperate. A useful explanation needs to cover finding a candidate, communicating a request, and deciding whether the interaction can proceed. Treating these as separate questions makes a comparison clearer: a mechanism for locating a participant answers something different from a convention for exchanging messages.
The discussion of FIPA standards provides the context for this comparison. Here, the focus is on what present-day stewards report about their protocols and research. Similar questions provide a common frame for reading their announcements; similarity alone does not establish technical compatibility or a direct line of succession.
In its 9 April 2026 report on A2A's first year, the Linux Foundation described the Agent-to-Agent Protocol as providing a common semantic model and version negotiation for discovery, communication, and transactions. The project is hosted by the Linux Foundation. The report recorded more than 150 supporting organizations, compared with more than 50 in April 2025.
The announcement identified version 1.0 as the first stable specification. Features included Signed Agent Cards for cryptographic identity verification, alongside multi-protocol support and a defined migration path for early adopters. It also reported that the software development kit ecosystem had expanded from one Python implementation to five languages, including JavaScript, Java, Go, and .NET. These are reported implementation and specification milestones, with different implications from a count of supporting organizations.
The release describes A2A as coordinating agents across organizational boundaries, while MCP connects agents to tools and data sources. This separation helps a reader ask which relationship a protocol governs. The A2A roadmap also includes an interoperability specification and registry work. Those items describe the direction of further work; they should not be read as already completed features on the strength of the announcement.
The Linux Foundation's 9 December 2025 announcement introduced AAIF as a neutral, open foundation, with founding project contributions including MCP, goose, and AGENTS.md. Anthropic contributed MCP, and Block contributed goose. The release describes MCP as a protocol for connecting models to tools, data, and applications.
The other contributions illustrate different concerns within the same foundation. The announcement describes goose as an open source framework that combines language models, extensible tools, and MCP-based integration. AGENTS.md provides project-specific guidance for coding agents working across repositories and toolchains. A connection protocol, an agent framework, and a convention for project guidance therefore need to be considered according to their respective purposes.
For a hypothetical workflow, imagine an agent coordinating a task with a partner and then consulting a data source while doing its share. The coordination relationship is the part to examine through the A2A description; access to the source is the part to examine through the MCP description. This separates responsibilities when sketching a system, before considering the details of either specification.
For interoperability, the useful distinction is the relationship being organized. An agent coordinating with another agent and an agent reaching a data source need explanations of different interactions. The Linux Foundation explicitly presents A2A and MCP as complementary. That framing lets readers consider how the two roles fit together while keeping the scope of each protocol visible.
NIST's agent standards initiative, on a page created 17 February 2026, sets out work toward agents operating securely for users and interoperating smoothly. It organizes that work around three pillars: industry-led standards, community-led protocols, and research. Its protocol work includes identifying and reducing barriers to interoperable agent protocols.
The research pillar covers agent authentication and identity infrastructure for secure human-agent and multi-agent interactions. NIST also describes security evaluations intended to inform protocol development and consumer comparison. This adds a research and evaluation perspective to the specification milestones reported by the Linux Foundation. An announced protocol feature and a research programme answer different questions about the work underway.
For someone comparing agent systems, this suggests asking where identity is established and how security claims are evaluated, alongside asking how messages travel. These are ways to organize the reading, rather than a claim that the initiative certifies a particular implementation. The initiative's stated research topics identify questions to investigate.
The Directory Facilitator and ACL performatives discussed on the FIPA page offer useful comparison points. Compare directory discovery with the identity question raised by Signed Agent Cards: locating a candidate and checking identity are distinguishable concerns. Compare message meaning with A2A's reported common semantic model: both invite a reader to ask what the parties must understand about an exchange.
These comparisons are a reading framework, rather than a mapping between specifications. Keep discovery, identity, message meaning, and tool access visible as separate questions. Then distinguish what a steward reports as available, what appears on a roadmap, and what remains a research topic. That approach makes the announcements easier to assess without turning shared vocabulary into a claim of demonstrated interoperability.