---
title: "AAIF picked up 170 members in four months. The question is what they're agreeing on."
date: 2026-06-01
summary: "The Agentic AI Foundation grew from 8 founding Platinum members to 170 total in its first four months. The growth is the demand signal; protocol convergence is the work that follows, and the gap between the two is what consumers of agent infrastructure will be reading."
slug: aaif-membership-vs-protocol-convergence
author: "Sebastiaan Hilbers"
hero_glyph: branches
---

The Agentic AI Foundation [formed under the Linux
Foundation](https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-agentic-ai-foundation)
on December 9, 2025, with eight founding Platinum members: Amazon Web
Services, Anthropic, Block, Bloomberg, Cloudflare, Google, Microsoft, and
OpenAI. [Four months
later](https://aaif.io/blog/mcp-is-now-enterprise-infrastructure-everything-that-happened-at-mcp-dev-summit-north-america-2026/),
at the April 2026 MCP Dev Summit, the foundation reported 170 member
organizations across all tiers. That growth rate is notable — the
foundation absorbed [MCP](https://modelcontextprotocol.io),
[goose](https://github.com/block/goose), and
[AGENTS.md](https://agents.md/) as anchor projects on day one and added
~40 organizations per month from there.

What 170 members in four months tells you is that there is real demand
for cross-vendor coordination on agent infrastructure. What it does not
tell you is what those 170 organizations have agreed on. Membership
velocity and protocol convergence are different objects. The first is a
demand signal. The second is a lagging indicator. The agent web is in a
phase where the first is easy to measure and the second is the work
that hasn't shipped yet.

## The growth, in context

A foundation's first four months are mostly governance scaffolding.
AAIF's [project lifecycle
policy](https://aaif.io/blog/mcp-is-now-enterprise-infrastructure-everything-that-happened-at-mcp-dev-summit-north-america-2026/),
approved by the Technical Steering Committee at the April summit,
defines three stages (Growth, Impact, and Emeritus) that mirror
the CNCF's Sandbox / Incubating / Graduated structure. External
project proposals can be submitted to `aaif/project-proposals` on
GitHub; the foundation will evaluate them on adoption, governance, and
community health. None of this is unusual. All of it is necessary
infrastructure before any of the absorbed projects produce a
conformance suite, a graduation badge, or a cross-project version
compatibility statement.

<svg viewBox="0 0 640 300" xmlns="http://www.w3.org/2000/svg" style="max-width:100%;height:auto;display:block;margin:28px auto" role="img" aria-labelledby="aaif-title aaif-desc">
  <title id="aaif-title">AAIF membership growth, December 2025 to April 2026</title>
  <desc id="aaif-desc">A growth curve from December 9, 2025 (8 founding Platinum members) to April 13, 2026 (170 total members across all tiers). Three event markers along the curve: foundation formation in December, MCP donation in December, and the April MCP Dev Summit. The curve rises steeply between January and April.</desc>
  <style>
    .ax { stroke: var(--c-fg-3, #6b7280); stroke-width: 1; }
    .gd { stroke: var(--c-fg-5, #e5e7eb); stroke-width: 1; stroke-dasharray: 3 3; }
    .curve { fill: none; stroke: var(--c-violet, #A855F7); stroke-width: 2.4; }
    .area { fill: var(--c-violet, #A855F7); opacity: 0.08; }
    .dot { fill: var(--c-violet, #A855F7); }
    .lt { font-family: 'Geist', system-ui, sans-serif; font-size: 11px; fill: var(--c-fg, #0a0a0a); }
    .lp { font-family: 'Geist Mono', ui-monospace, monospace; font-size: 11px; fill: var(--c-fg, #0a0a0a); font-weight: 600; }
    .ll { font-family: 'Geist Mono', ui-monospace, monospace; font-size: 10px; fill: var(--c-fg-4, #9ca3af); letter-spacing: 0.14em; }
    .ev { stroke: var(--c-pink, #F472B6); stroke-width: 1.4; stroke-dasharray: 4 3; }
  </style>
  <text x="0" y="18" class="ll">AAIF MEMBER ORGANIZATIONS · DEC 2025 → APR 2026</text>

  <!-- Grid -->
  <line x1="60" y1="60" x2="620" y2="60" class="gd"/>
  <line x1="60" y1="120" x2="620" y2="120" class="gd"/>
  <line x1="60" y1="180" x2="620" y2="180" class="gd"/>
  <line x1="60" y1="240" x2="620" y2="240" class="gd"/>

  <!-- Axes: y-scale 0 (y=240) to 180 (y=40); x-scale Dec 9 (x=60) to Apr 13 (x=620) -->
  <line x1="60" y1="240" x2="620" y2="240" class="ax"/>
  <line x1="60" y1="40" x2="60" y2="240" class="ax"/>

  <!-- Curve points:
       Dec 9, 2025: 8 members -> y = 240 - (8/180)*200 = 240 - 8.9 = 231
       Jan 9: ~30 -> y = 240 - 33 = 207
       Feb 9: ~70 -> y = 240 - 78 = 162
       Mar 9: ~120 -> y = 240 - 133 = 107
       Apr 13: 170 -> y = 240 - 189 = 51
       x spans 126 days from Dec 9 to Apr 13: 60+(0/126)*560=60, 60+(31/126)*560=198, 60+(62/126)*560=336, 60+(90/126)*560=460, 60+(126/126)*560=620
  -->
  <path class="area" d="M 60 231 C 100 220, 150 210, 198 207 C 240 200, 290 180, 336 162 C 380 140, 420 120, 460 107 C 500 90, 560 70, 620 51 L 620 240 L 60 240 Z"/>
  <path class="curve" d="M 60 231 C 100 220, 150 210, 198 207 C 240 200, 290 180, 336 162 C 380 140, 420 120, 460 107 C 500 90, 560 70, 620 51"/>

  <!-- Dots at key markers -->
  <circle cx="60" cy="231" r="4" class="dot"/>
  <circle cx="620" cy="51" r="5" class="dot"/>

  <!-- Annotations -->
  <line x1="60" y1="231" x2="60" y2="251" class="ev"/>
  <text x="60" y="270" text-anchor="start" class="lt">Dec 9, 2025</text>
  <text x="60" y="285" text-anchor="start" class="lp">8 founding members</text>

  <line x1="620" y1="51" x2="620" y2="20" class="ev"/>
  <text x="620" y="14" text-anchor="end" class="lt">Apr 13, 2026 · MCP Dev Summit</text>
  <text x="610" y="48" text-anchor="end" class="lp">170 members</text>

  <!-- Y axis labels -->
  <text x="55" y="240" text-anchor="end" class="ll">0</text>
  <text x="55" y="170" text-anchor="end" class="ll">60</text>
  <text x="55" y="103" text-anchor="end" class="ll">120</text>
  <text x="55" y="44" text-anchor="end" class="ll">180</text>
</svg>

## What's in scope, and what's still TBD

A useful way to read AAIF's first four months is by sorting what has and
hasn't shipped. The shipped column is concrete and operationally
meaningful. The TBD column is the work that turns 170 logos on a
membership page into infrastructure a downstream consumer can rely on.

| Shipped (Dec 2025 – Apr 2026) | TBD (the convergence work) |
|---|---|
| 8 founding Platinum members, 170+ total across tiers | Cross-project version compatibility statements |
| Anchor projects absorbed: MCP, goose, AGENTS.md | First conformance test suite for any anchor project |
| Project lifecycle policy (Growth / Impact / Emeritus) | First graduation from Growth to Impact |
| TSC structure and external-proposal pathway | A registry-of-registries policy for MCP-server publication |
| April 2026 Dev Summit + roadmap discussion | A cross-vendor breaking-change policy for MCP / A2A |

That right-hand column is the part that determines whether AAIF
membership produces something a consumer of an MCP server or an A2A
agent can act on. None of those items are blocked on additional
membership growth; they are blocked on the working groups doing the
specification work that follows from the absorbed projects' existing
roadmaps.

This is not a critique of AAIF specifically. Every foundation, CNCF
included, started in the same shape: rapid membership growth in the
first year, conformance and graduation work in years two and three.
What's worth flagging now, while the AAIF model is still being set, is
which of those items the consumers of agent infrastructure most need.

## What a consumer of MCP actually needs from a foundation

If you're shipping an agent that depends on third-party MCP servers,
the operationally useful outputs from a foundation are not the
membership count. They are, in roughly descending order:

1. **A conformance test suite** that a consumer can re-run against a
   given MCP server to confirm spec adherence. The [population scans
   that found command-injection in roughly a third of MCP servers in
   the wild](https://agenstry.com/blog/mcp-spec-vs-probe-evidence)
   exist precisely because no such suite is operating at scale.
2. **A breaking-change policy** that names what counts as a breaking
   spec revision and what the deprecation window is. Today, [the
   spec carries identical Origin-validation MUST clauses across
   2025-06-18 and
   2025-11-25](https://agenstry.com/blog/google-mcp-origin-validation-seven-months)
   and downstream behavior diverges anyway. A policy is the
   coordination tool that makes that gap visible.
3. **A registry governance statement** for the [hosted MCP
   Registry](https://github.com/modelcontextprotocol/registry).
   Specifically: what is published, what is verified before
   publication, what removal criteria exist, and who decides. The
   registry currently functions as a discovery layer; whether it
   should encode conformance signals is the open question Agenstry
   [keeps coming back
   to](https://agenstry.com/blog/erc-8004-three-registries-honesty).
4. **Cross-protocol version compatibility statements** between MCP,
   A2A, and AGENTS.md, which are now governed under the same
   foundation. The protocols can evolve independently; their
   interactions cannot.

None of those four items has a v1.0 yet. All four are within scope of
what AAIF is structurally set up to produce. The four months of
membership growth tell you the room is full. The next four months will
tell you what gets decided in it.

## What we're watching

Three things, observable within the next two quarters:

1. **Whether AAIF's first project graduates from Growth to Impact.**
   The lifecycle policy was approved at the April summit. The first
   transition will be the first concrete signal of what the bar
   actually is.
2. **Whether the MCP Registry roadmap publishes a conformance-test
   field.** A small change to the registry schema, naming a probe
   result or a conformance score, would close the largest gap between
   publication and verification at the layer that matters most for
   downstream consumers.
3. **Whether the next breaking change to MCP or A2A ships with a
   foundation-mediated deprecation window.** A coordinated policy is
   what distinguishes a project absorbed under a foundation from one
   that simply happens to share a logo with one.

170 members is the number that travelled in the press recap. The
numbers that matter over the next year are smaller and harder to count:
the count of conformance suites published, the count of projects
graduated, the count of cross-project compatibility statements ratified.
Those are what consumers of the agent web will be reading off the
foundation's outputs. The membership growth is the room. The work
happens after the doors close.

## Sources

- [Linux Foundation Announces the Formation of the Agentic AI Foundation](https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-agentic-ai-foundation) — Linux Foundation, December 9, 2025.
- [MCP Is Now Enterprise Infrastructure: Everything That Happened at MCP Dev Summit North America 2026](https://aaif.io/blog/mcp-is-now-enterprise-infrastructure-everything-that-happened-at-mcp-dev-summit-north-america-2026/) — Agentic AI Foundation, April 13, 2026.
- [Agentic AI Foundation homepage](https://aaif.io) — accessed May 2026.
- [Model Context Protocol Registry repository](https://github.com/modelcontextprotocol/registry) — modelcontextprotocol/registry, accessed May 2026.
- [Model Context Protocol — modelcontextprotocol.io](https://modelcontextprotocol.io) — accessed May 2026.
- [goose source repository](https://github.com/block/goose) — Block, Inc., accessed May 2026.
- [AGENTS.md specification](https://agents.md/) — agentsmd, accessed May 2026.