Linux Foundation Takes MCP Helm as llms.txt Reality Check Arrives
The MCP 2026-07-28 final spec is now live under the Linux Foundation's Agentic AI Foundation, reshaping how agents connect to business data. Simultaneously, fresh data from a 137,000-domain study shows that the most popular AI visibility tactic, publishing an llms.txt file, is reaching almost no AI crawlers at all.
This Week's Signals
Final MCP Spec Moves Under Linux Foundation, Deprecates Three Core Features
Why it matters for your score
The 2026-07-28 spec is now the standard all four Tier 1 SDKs ship against, meaning any business exposing tools or data through MCP needs to audit against the new spec immediately. Roots, Sampling, Logging, and legacy HTTP+SSE transport are all deprecated with a 12-month offramp; teams running older integrations have a countdown clock. Governance moving to the Linux Foundation's AAIF signals that MCP is infrastructure, not a vendor feature, which raises the stakes for getting your implementation right.
What to do this week
- 1
Check your MCP integration against the 2026-07-28 final spec, specifically whether you rely on Roots, Sampling, Logging, or legacy HTTP+SSE transport; all are now deprecated with a 12-month offramp. Use Faro's /tools/ai-readiness-scan to flag outdated connection patterns before the clock runs out.
- 2
Audit your llms.txt file against the actual spec requirements, correct H1, summary section, and organized content sections, since industry data shows more than half of published files do not meet the standard. Use Faro's /tools/llms-txt to generate or validate a spec-compliant file.
- 3
Shift AI visibility effort toward content depth and third-party citations rather than relying on llms.txt alone, given that the Ahrefs study found AI retrieval bots account for about 1.1% of llms.txt requests. Use Faro's /tools/competitor-intelligence to identify where competitors are earning citations that you are not.