OTel GenAI vs OpenInference vs OpenLLMetry vs OpenLIT: the neutral option is the one still moving
Of the four ways to shape an agent trace, the only one that calls itself the standard is the only one you cannot pin: on 12 June 2026 OpenTelemetry deprecated all sixty gen_ai attributes and moved them to a repository that still has no tagged release and a TODO where its schema URL should be. Eight renames and two deletions landed in that one version — including both token-usage attributes. Pick by the vocabulary your backend dispatches on, translate at the collector, and never point a cost chart at a Development-stability attribute name.
A dropped subscription looks exactly like a quiet week
OpenAI shipped plugin automations on all plans on 29 September 2026 against MCP Events — a draft with no SEP number, in a repository whose README calls its contents exploratory. The draft gets the webhook hardening right and makes the two envelopes that report absence optional, so a revoked permission, a lost buffer and a genuinely quiet upstream all reach your agent as the same empty stream.
WebMCP makes your page an API, and the session is the only auth it has
WebMCP lets a page hand an AI agent a list of callable tools, and Chrome is shipping it behind a flag while the W3C community group draft is still moving. The part worth arguing about is not discovery but authority: a registered tool executes as your page's own JavaScript, inside the session the logged-in user already established, so your server sees a request it cannot distinguish from a click. You are publishing an API whose only credential belongs to someone who is not the caller.
On 4 September Docusign said its MCP server opens to every agent on 30 September — Claude, ChatGPT, Gemini, Copilot, Slack, any MCP client — governed by account-level admin controls. The law has allowed an automated agent to bind its principal since 1999, on one condition: the act must be attributable to that person. A per-account toggle attributes a class of acts, which is what carried deterministic scripts and is exactly what a model that negotiates strains. Closing that gap is the deployer’s job, and nothing in MCP does it for you.
FastMCP vs the TypeScript SDK vs mcp-go vs rmcp: who negotiates the revision for you
These four are benchmarked on throughput, which is a 1.9 ms spread inside a 50–500 ms upstream call — and ranked on it while the axis with a date attached goes unmeasured. Three of the four implement the 2026-07-28 stateless revision and the most-used Go library does not, but the sharper question is which of them absorbs your dual-revision window instead of turning it into your topology.
MHS vs SiLA 2 vs OPC UA LADS vs ROS 2: the wire format was never the problem
Lab and factory interoperability has been standardised three times already — SiLA 2 since 2019, OPC UA LADS since January 2024, ROS 2 as robotics middleware — and instruments still ship with vendor SDKs, so a fourth spec is not obviously the answer. What Anthropic's Model Hardware Standard adds is the thing none of the three tried: a device that describes its own limits in language a model can read, and a driver that enforces them whichever model is driving. Useful, and not a safety function — keep those apart.
CopilotKit vs assistant-ui vs AI Elements vs Chainlit: you are picking a coupling, not a chat box
All four render a streaming message list, and the demo looks the same in each. What differs is the layer you cannot swap later — a wire protocol, an npm dependency, a source tree copied into your repo, or a whole Python server whose front end you never wrote — and after a year in which one canvas archived itself and another changed hands, "what do I still own if this goes quiet" is the axis worth deciding on.
agentgateway vs ContextForge vs Obot vs Docker MCP Gateway: whose identity reaches the server
The MCP specification settles the negative — as of revision 2026-07-28 a server MUST NOT pass through the token it received from its client — but leaves RFC 8693 token exchange on the roadmap, so four gateways answer the question four different ways. agentgateway and ContextForge exchange the token; Obot attaches the user’s stored upstream token and is mid-migration between the two; Docker MCP Gateway has no user concept at all, which is honest for a workstation and disqualifying for a fleet. Pick on that axis, and notice that Docker’s isolation story is the best of the four on an axis the others do not compete on.
Sharing a coding-agent session: every handoff that works throws the transcript away
Claude Code, Codex and Gemini CLI all persist sessions as append-only JSONL, so moving one to another agent looks like a file-conversion problem. It is not. An assistant turn is a claim conditioned on a system prompt, a tool schema, a model and a warm cache that the receiving agent does not have — replay it verbatim and you hand over a false memory. The one converter in the wild strips tool calls into prose on purpose, Anthropic documents its own transcript format as internal and unstable, and Claude Code refuses to resume a hand-copied transcript at all. Four transfer layers, and the useful ones all trade fidelity for something the receiver can re-verify against the repo.
The AI AGENT Act Asks for a Record Your Stack Does Not Keep
S. 5051 would require an agent acting for a person to keep real-time records, stay inside its granted authority, and never sub-delegate without explicit permission. Traces record behaviour; all three duties are about permission — which is why the bill hands NIST the job of finding a delegation protocol that does not exist.
A2A Moved In With MCP. The Identity Layer Stayed Outside.
On 20 August Google moved A2A into the Agentic AI Foundation, so both protocols in the standard agent stack now share a board, a roadmap and a trademark holder. What they still do not share is a delegation primitive — and the identity work that would supply one is being stewarded at a different foundation entirely.
The 2026-07-28 MCP spec deleted the initialize handshake and the session-id header, so a server can now run behind a plain round-robin load balancer. That operational win is real — but statelessness is a transport property, not a system property. The session did not disappear; its bookkeeping moved onto every request, and the durability that long-running agents actually need came back in through the AWS-contributed Tasks extension as explicit handles. Read the two together before you celebrate a simpler protocol.
x402 vs AP2 vs ACP vs MPP: The Only Difference That Changes Your Risk
Four agent-payment standards, usually compared on rails. The axis that matters is where the spending cap is stored — a pre-funded wallet, an issuer rule, a one-checkout token, or a mandate the user signed — because that fixes how much a prompt-injected agent can spend before anything else gets a vote.
Generative UI Has Two Standards, and They Split Over Who Owns the Catalog
A2UI sends JSON and MCP Apps sends sandboxed HTML — the least consequential difference between them. One has the agent compose components you own, moving the review into your design system; the other installs an interface someone else wrote, moving it to the server boundary. Sort your surfaces by whether you can enumerate them, then pick.
Agent Plugins 1.0 Standardises the Bundle and Leaves Trust to Whoever Installs It
Five rival vendors agreed on a directory layout on 6 August, and explicitly declined to agree on install, distribution, permissions, sandboxing or provenance. The format makes one bundle of instructions plus credentialed tool access portable across six clients — which is exactly why the compensating controls are now yours.
Auth0 vs Descope vs Stytch vs WorkOS: Agent Auth Is Two Products
Every identity vendor now sells “auth for AI agents”, and the phrase covers two opposite problems: letting an agent into your app, and letting your agent out to someone else’s API. Pick on direction first — and notice that a token vault holding a user’s full grant has relocated the credential rather than shrunk it.
Google's Agent Calls the Store, and Every Protocol Guarantee Falls Off
Google's shopping agent now phones local shops to check stock — a channel that carries none of the signed identity, scoped authorisation, replay protection or verifiable receipts that AP2 and its rivals were built to provide. The phone is not a stopgap on the way to universal protocol adoption; it is the permanent floor of agent commerce, covering the merchant tail that will never implement an API, and it has no trust primitives at all.
The 28 July specification retires the initialize handshake and the Mcp-Session-Id header, and every write-up so far has framed that as plumbing. It is not. Dropping the held-open connection forced Sampling, Roots and Logging onto a twelve-month deprecation clock — and those were the features that made an MCP client a peer rather than a caller. The protocol just settled what it is.
MCP at 97 Million Downloads: How the Model Context Protocol Won — and What's Still Broken at Scale
Two years from Anthropic's launch, MCP isn't a debate — it's a dependency. Every frontier vendor, every major IDE, and one Pinterest team saving 7,000 engineering hours a month all ship against it. The interesting question is no longer *should you use MCP* — it's what fails at this scale and how the 2026 roadmap plans to fix it.