MCP Goes Stateless, llms.txt Hype Cracks, Citations Favor Lists
The Model Context Protocol's biggest revision yet strips out session state and adds routable headers, reshaping how AI agents connect to business services. Meanwhile, two independent datasets puncture the idea that publishing llms.txt alone drives AI citation.
This Week's Signals
MCP's July 28 Release Candidate Strips Sessions and Adds Gateway-Ready Routing Headers
Why it matters for your score
The protocol is now fully stateless, no initialize handshake, no sticky sessions, which means businesses can put standard load balancers in front of MCP servers without custom infrastructure. New Mcp-Method and Mcp-Name headers let gateways route by operation without reading request bodies, and a new caching model (ttlMs and cacheScope) means repeated AI-agent reads of your data no longer require a fresh server hit every time. If your team is building or buying MCP server tooling, the 10-week SDK update window starts now.
What to do this week
- 1
Review whether your MCP server implementation relies on session state or sticky-session load balancing, the July 28 spec makes both obsolete. Use the /tools/ai-readiness-scan to identify integration points that need updating before the 10-week SDK window closes.
- 2
If you are not on Shopify, do not assume llms.txt is handled for you. Use the /tools/llms-txt tool to generate a properly structured file, and verify it is not an empty stub, since industry analysis shows 40% of existing files deliver no measurable benefit.
- 3
Restructure your top commercial pages to lead with the key claim in the first third of the document and include at least one numbered comparison list. Use the /tools/okf-generator to add structured data that reinforces the hierarchy AI models use when extracting citations.