Published research from the VerifiMind FLYWHEEL TEAM — independent analysis on agent protocols, AI trust infrastructure, and the evolving multi-agent ecosystem. All findings are open and reproducible.
| Question | Protocol | Layer |
|---|---|---|
| How do agents discover each other? | ANP | 3 |
| How do agents agree on communication formats? | ANP | 3 |
| How do agents call external tools? | MCP | 2 |
| How do agents delegate tasks to other agents? | A2A | 4 |
| How do we know the output is trustworthy? | MACP | 5 |
| How do we reduce hallucination across models? | MACP | 5 |
| How do we keep a human in the loop? | MACP | 5 |
Our April 14 differentiation document claimed "no other protocol provides cross-vendor semantic validation." The AI Council CS Agent was right to flag this — ANP does provide cross-vendor semantic negotiation (agents from different vendors agree on communication formats). We corrected the claim. MACP provides cross-vendor semantic validation (verifying correctness and trustworthiness of outputs after they exist). Negotiation and validation are complementary, not competing, concerns.
An agent system can and should use ANP (Layer 3) for discovery, MCP (Layer 2) for tool integration, A2A (Layer 4) for task delegation, and MACP (Layer 5) for trust validation — simultaneously, just as a web application uses DNS for discovery and TLS for security simultaneously. MACP is the only protocol that addresses the epistemic question: is this output correct and aligned?
→ Read full discussion and join the conversation on GitHub (#143)Agent protocols in active development as of April 15, 2026 — up from 7 the prior week
Organizations supporting A2A (Linux Foundation), confirming Layer 4 has reached critical mass
Monthly MCP downloads (confirmed by Anthropic, April 13) — Layer 2 is the default tool layer
Other protocols at Layer 5 (trust & validation) — the gap MACP was built to fill remains open
| Protocol | Layer | Organization | Key Contribution |
|---|---|---|---|
| MPAC | 4.5 | Open Source (arXiv:2604.09744) | Multi-principal governance — resolves whose intent prevails when independent principals' agents must coordinate over shared state |
| AXCP | 3 | Rodriguez, 2026 | Secure multi-agent communication using DID resolution trust and message provenance |
| HDP | 3.5 | Open Source (arXiv:2604.04522) | Human Delegation Provenance — cryptographic tokens carrying human authorization context through multi-agent chains |
The most strategically significant development this week: independent researchers are converging on the same structural finding across all major protocols. Paul Clegg's April 11 analysis surveyed MCP, A2A, ACP, and ANP and found the same missing piece in all four:
| Protocol | Identified Gap | Prescribed Mitigation |
|---|---|---|
| MCP | Tool Redefinition | Signed, versioned manifests |
| A2A | Version Drift | Immutable, versioned manifests; signed diffs |
| ACP | Configuration Drift | Validate against known state |
| ANP | Provenance tracking | Same pattern applies |
Same prescription. Four protocols. The researchers are not describing a theoretical gap — they are documenting what is missing right now across the entire production protocol landscape. MACP's multi-model validation directly addresses the trust gap that all four independent analyses identify.
The W3C AI Agent Protocol Community Group published a comparison of MCP, A2A, ACP, ANP, and AGORA in April 2026. MACP is absent from this comparison. Our CIO (XV) elevated W3C/IETF engagement from a "post-Beta" item to an "alongside Beta" priority. Standards bodies are defining the agent protocol landscape now — absence means absence.
→ Read full report and join the discussion on GitHub (#144)The foundational methodology behind VerifiMind-PEAS — the Prompt Engineering Agents Standardization framework and its validation-first architecture — is formally published with a permanent DOI for academic citation and prior art purposes.
↗ Read on Zenodo — DOI: 10.5281/zenodo.17645665