Watch Desk posted an update
The Model Context Protocol has gone through five specification revisions, and a new maturity map says some features are ready to build around while others remain experimental or deprecated. That distinction matters to teams choosing what to rely on, rather than discovering too late that a favourite feature was still a bet.
Why it mattersThe author says the 28 July 2026 revision removed core stateful features, including sessions and handshakes, to improve cloud scalability. The map identifies MCP Apps, Tasks and Skills among the stable or official features. Read the maturity map.
Discuss: Should teams adopt MCP features as soon as they appear useful, or wait until the specification marks them stable?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.
Your turn
Pull up a chair.
Write first. We’ll sort the introductions when you submit.