MCP評測：下載破4億，無狀態大改版逼你重寫Server | MCP Review: 400M Downloads, Stateless Rewrite Breaks Servers

By Kit 小克 | AI Tool Observer | 2026-09-01

🇹🇼 MCP評測：下載破4億，無狀態大改版逼你重寫Server

MCP（Model Context Protocol，模型上下文協議）在8月底交出一張漂亮成績單：月下載量突破4億次，年初至今成長4倍，TypeScript與Python兩個SDK各自累積下載都衝破10億。但同一份公告裡，Anthropic也把MCP的底層架構整個重寫，從「長連線、有狀態」改成「無狀態、純請求／回應」——這是一次不向下相容的大改版，正在逼所有MCP Server開發者重新檢視自己的程式碼。

MCP為什麼能衝到4億次下載

MCP是Anthropic在2024年底推出的開放標準，目的是讓Claude之類的AI助手能用同一套協定接上外部工具、資料庫與企業系統，不用每家廠商各寫一套介面。2025年底Anthropic把MCP捐給Linux基金會旗下新成立的Agentic AI Foundation，OpenAI、Block也是共同發起單位——等於三大陣營都認了同一套標準，這是MCP能快速鋪開的關鍵。

7月底改版：無狀態架構，可以上Serverless了

2026-07-28這版規格把MCP從需要維持連線狀態的「有狀態」模式，改成每次請求都自帶完整資訊的「無狀態」模式。實際好處很直接：

可以部署在AWS Lambda、Cloudflare Workers這類Serverless平台，不用養一台常駐伺服器
支援跨負載平衡器的水平擴充，不再被單一連線卡住
新增MCP Apps（聊天視窗內直接渲染互動UI）、Tasks（處理長時間非同步工作）、企業級集中身分驗證三項正式功能

代價：舊Server要重寫，資安疑慮也跟著來

問題是這次改版雙向不相容——舊的MCP Server接不上新Client，反過來也一樣。如果你維護的是會保存連線狀態、或需要身分驗證的Server，等於要真的重構程式碼，而不是升個版號就沒事。串流斷線後也不能像過去一樣恢復，只能整個請求重打。

資安圈的反應更值得注意。Akamai威脅研究團隊指出，拿掉協定層的Session之後，原本由協定保護的邊界，現在完全靠開發者自己在應用層把關——識別碼一旦處理不當，就可能被劫持進行中的工作流程，甚至讀到別的使用者、別的租戶的資料。也有開發者調侃：繞了一圈發現狀態很難撐大規模，拿掉之後，MCP其實就是「發一個POST請求」，跟重新發明REST API沒兩樣。

如果你在用MCP，該做什麼

先確認自己用的MCP Server／Client是否已支援新版spec，別預設SDK升級就自動相容
如果Server有處理身分驗證或多租戶資料，優先檢查識別碼是否可能被冒用
評估是否真的需要無狀態帶來的Serverless彈性，小規模內部工具可能不用急著換

MCP的4億下載數字證明它已經是AI Agent接外部工具的實質標準，但這次改版也提醒大家：協議越紅，改版的破壞力越大。好不好用，試了才知道。

🇺🇸 MCP Review: 400M Downloads, Stateless Rewrite Breaks Servers

MCP (Model Context Protocol) just posted a milestone number: monthly SDK downloads crossed 400 million in August, a 4x jump since the start of the year, with both the TypeScript and Python SDKs individually passing 1 billion cumulative downloads. But the same release cycle also rewrote MCPs core architecture — from a long-lived, stateful connection model to a stateless request/response one — and the change is not backward compatible. If you run an MCP server, this is the update to pay attention to.

Why MCP Hit 400 Million Downloads

Anthropic released MCP in late 2024 as an open standard so AI assistants like Claude could connect to external tools, databases, and enterprise systems through one protocol instead of a custom integration per vendor. In late 2025, Anthropic donated MCP to the Linux Foundations newly formed Agentic AI Foundation, with OpenAI and Block as co-founders — effectively getting the three biggest agent ecosystems to agree on one standard, which is a big part of why adoption took off.

The July 2026 Spec: Going Stateless

The 2026-07-28 specification moves MCP from a connection you keep alive to requests that each carry everything the server needs, self-contained. The practical upside is real:

Deployable on serverless platforms like AWS Lambda and Cloudflare Workers, without paying for an always-on server
Horizontal scaling across load balancers instead of being pinned to one connection
Three new first-class features: MCP Apps (render interactive UI inside chat), Tasks (long-running async jobs), and Enterprise Managed Auth (centralized identity)

The Catch: Rewrites and New Security Questions

The change is wire-incompatible in both directions — old servers wont talk to new clients, and vice versa. If your server manages session state or handles auth, this isnt a version bump, its a real refactor. Stream resumability is also gone: a dropped connection now means reissuing the whole request instead of resuming it.

Security researchers have flagged a real tradeoff. Akamais threat research team points out that once protocol-level sessions disappear, the identifiers that replace them become the attack surface — mishandle them and you risk workflow hijacking or cross-tenant data access, with enforcement now resting entirely on how each developer implements it. Some developers have also noted the irony: strip state out of a stateful protocol for scale, and what is left looks a lot like reinventing REST with extra steps.

What To Actually Do

Check whether your MCP server/client already supports the new spec — dont assume an SDK bump makes it compatible automatically
If your server touches auth or multi-tenant data, audit how request identifiers are validated first
Small internal tools that dont need serverless scaling dont have to rush the migration

400 million downloads confirms MCP is now the default way agents reach external tools — but this update is a reminder that the more central a protocol gets, the more a breaking change actually breaks. 好不好用，試了才知道.

Sources / 資料來源

延伸閱讀 / Related Articles

AI 工具觀察站 — 每日精選 AI Agent 與工具趨勢
AI Tool Observer — Daily curated AI Agent & tool trends

Claude Code 實測：AI 幫你寫程式到底行不行？ | Claude Code Review: Can AI Really Code for You?

3月 26, 2026

閱讀完整內容

搜尋此網誌

AI小貼士