Five verified moves this week, and a team of one can act on each before the weekend. The biggest Model Context Protocol revision since the standard launched finalizes today. Europe's AI-Act enforcement powers switch on in five days, with real fines behind them. A chip startup that only runs transformers doubled its valuation to $10.3B. And two open models — Kimi K3 and a stable DeepSeek V4 — quietly moved the floor on what it costs to run an agent. Every item below is dated and sourced, and each carries the one line that changes what you do next.
1. MCP's stateless spec finalizes today — audit three deprecations, then go stateless on the stable SDK#
The 2026-07-28 Model Context Protocol revision — described by its maintainers as the largest since launch — reaches final publication today, on schedule from the release candidate that was locked in May (MCP blog). Three things change that matter to a server author:
- The core goes stateless. The
initialize/initializedhandshake and theMcp-Session-Idheader are gone. Any request is self-contained, so any instance can serve it — no sticky routing, no shared session store at the protocol layer. - Roots, Sampling, and Logging are deprecated to annotation-only. They still work this release, but they're on the clock. We walked through what each did and what replaces it.
- A formal Extensions framework ships, with two official extensions: MCP Apps for server-rendered UIs and Tasks for long-running work.
What it means: This is a migration event, not a fire drill — existing servers keep working and clients fall back (spec status). The part most coverage misses: you don't need the beta v2 SDK to adopt the stateless architecture. The stable SDK already runs stateless with a one-line change — we wrote the exact how-to — so the real work is moving state out of the transport, not chasing a pre-release. Start there; migrate the auth model and Tasks when the stable v2 SDKs land.
2. The EU AI Act's enforcement clock starts August 2 — five days to confirm you're not a "provider" by accident#
From August 2, 2026, the European Commission's enforcement powers over general-purpose-AI (GPAI) providers take effect. The obligations applied a year ago; the teeth arrive now, and they're sharp: fines up to €15M or 3% of global annual turnover, whichever is higher (European Commission).
What it means: The trap is the word provider. It isn't only the lab that trained the base model — fine-tuning or redistributing a GPAI model into the EU market can pull you into provider obligations around transparency and copyright documentation. If you ship into the EU, do three things this week: confirm whether you count as a provider, check whether your upstream model signed the GPAI Code of Practice (which grants a presumption of conformity), and get your documentation in order. We kept a running founder-compliance checklist for the August 2 deadline — this is the week to close it out.
3. Etched raises a reported $300M at $10.3B — the inference-cost war moves to silicon#
Etched, the startup building Sohu — a chip that runs only transformer models — closed a reported $300M Series C at a $10.3B valuation, roughly double its ~$5B mark from December, led by Sequoia with participation from a16z, SK Hynix, and Jane Street (TechCrunch). The bet: specialization beats the general-purpose GPU on inference cost and throughput.
What it means: For most solo founders this is a signal, not a to-do — but it's a useful one. Dedicated transformer silicon aiming to undercut Nvidia at the inference layer, arriving alongside open-weight frontier models you can host yourself, points one direction: the per-token cost of running an agent keeps falling. Don't bake today's GPU inference pricing into a 12–18 month unit-economics model as if it were fixed.
4. Kimi K3's open weights change the self-host math — benchmark before you renew#
Moonshot AI published the full weights of Kimi K3, a 2.8-trillion-parameter mixture-of-experts model (~104B active per token) under a modified-MIT license that permits commercial use, with day-0 hosting on Together AI and Modal (Interconnects). We covered the release itself yesterday; the founder action is the cost math.
What it means: A commercially-licensed, near-frontier open coding model you can rent or self-host is real leverage against a closed-model API bill — especially for code-generation products where output volume is the cost. But run the comparison honestly: rent K3 on Together or Modal, put it head-to-head with your current default on your own coding evals, and compare cost per completed task, not per token. See Kimi K3 vs. Opus 5 for where each one wins.
5. DeepSeek V4 goes stable — migrate off the retired endpoints#
DeepSeek's V4 moved from preview to a stable production build this week, and the older deepseek-chat and deepseek-reasoner endpoints are being retired on July 24.
What it means: If you pinned the legacy endpoints, this is a forced migration — update your model IDs before the retirement bites. And since you're touching the integration anyway, re-benchmark V4 stable against your current default; the day-0 serving recipe has the setup. The through-line across items 3, 4, and 5 is the same: cheaper silicon, cheaper open weights, cheaper stable builds. The cost of running an agent dropped again this week — the founders who re-price now capture it.
