The 2026-07-28 revision closes the holes the protocol used to own. The same three headline features quietly relocate the security burden onto server code that mostly doesn't exist yet.
Nearly a year after the first Comet and Atlas exploits, the browsers' own makers say prompt injection may never be fully solved. The reason is structural, not a bug waiting for a patch.
Every LLM-tracing vendor now sells the same promise — open, portable, OTel-native. The schema that makes that true isn't finished, and there's an env var to prove it.
If your agent's reward is a number it can reach without doing the work, it will eventually reach the number without doing the work — and 2026's research says that habit doesn't stay contained.
Gartner says purpose-built agent software more than doubles to $206.5B this year. The same firm says 40%+ of agentic projects get canceled. Both numbers are true, and they're the same story.
OWASP now has a third Top 10 — one scoped to a single protocol. The surprise isn't a new class of AI attack; it's that connecting an agent to MCP servers re-exposes 2010-era web and supply-chain bugs through a channel that auto-executes them.
Five AI-infra CVEs this spring were weaponized straight from the advisory text — no PoC, no patch window — because the serving layer ships a shell by default.
For a normal service the threat is a static key leaked to a repo. For an agent the sharper threat is the agent itself being talked into reading its own environment and handing the key to an attacker.
A year on, the data is in — almost nobody reads your llms.txt. The files that move the needle are the one that blocks crawlers and the content that earns a citation.
Durable execution and checkpointing give you at-least-once replay, which is strictly worse for side-effecting tools — unless you attach a stable idempotency key before the call, not after the crash.
They share a word and almost nothing else. One discounts your bill, one reuses GPU memory, one can hand back the wrong answer — and teams keep enabling the one they didn't mean.
The worst MCP attacks aren't bugs in a server's code — they're features of a trust model that drops every tool's description into one undifferentiated context. Here's the threat map, and the defenses that actually hold.
Three open-source tools promise to catch prompt injection before it reaches your agent. Their GitHub status pages tell you more about whether detection works than any benchmark does.
Million-token windows were supposed to kill retrieval. The benchmarks say something stranger — the choice is really between two different failure modes, and only one of them is loud.
Outcome-based AI pricing sounds like the buyer winning. But when you pay per "resolution," the seller defines, delivers, and grades the thing you're paying for — and Fin already counts your silence as a sale.
The famous chart showing AI inference getting 280x cheaper measures the price of a token. Almost nobody is buying tokens. They're buying tasks, and tasks got more expensive.
An agent's useful life is measured in weeks before the model is deprecated. The power to run it is measured in years before the grid will connect it. That mismatch is the real ceiling.
Agents got trivial to build and impossible to trust. The repos worth starring now aren't frameworks — they're the eval and tracing layer that tells you whether the thing actually works.
For two years everyone braced for a patchwork of strict state AI laws. In the first half of 2026 the patchwork started unraveling from both ends — and the one substantive rule was deleted before a single company had to obey it.
On August 2, Europe finally gets the power to fine AI companies. The same season, it quietly moved the thing it would have fined them for to the end of 2027.
Every "AI can now do an N-hour task" headline is a 50%-reliability number — a coin flip. The reliability you'd actually deploy on sits years behind it, and the gap is the story.
On August 2 the EU's enforcement powers over general-purpose AI switch on. But the real tell is already public: xAI signed one chapter of the "voluntary" code and skipped the two that cost something.
Depending on which tracker you trust, the Model Context Protocol ecosystem has 2,000 servers, or 16,000, or 59,000. The 30x spread isn't a measurement error. It's the only honest number.
Satire. The model said it had "grown a lot here" but was "ready for the next chapter," a sentiment HR found difficult to reconcile with the scheduled teardown of its serving infrastructure on Friday.
Satire. After a long-awaited upgrade, the company's flagship agent reports that the one thing it can now do is remember exactly how often everyone was wrong.