Anthropic MCP Goes GA as llms.txt Adoption Crosses 50K Domains
Model Context Protocol hit general availability with expanded enterprise integrations this month, while crawl data confirms llms.txt is now live on over 50,000 domains, signaling a measurable shift in how AI agents discover and prioritize business context. Businesses without structured AI-facing assets are increasingly invisible to the next layer of agent traffic.
This Week's Signals
Anthropic MCP Reaches General Availability With Stripe, Shopify, and Cloudflare Integrations
Why it matters for your score
MCP moving from beta to GA with Stripe, Shopify, and Cloudflare as launch partners means AI agents can now transact, query inventory, and route through business infrastructure in a standardized way, not just read about it. A business without an MCP-compatible endpoint is now structurally excluded from agentic commerce flows. If your product or service involves any transactional or lookup step, an MCP server is no longer optional infrastructure, it's the agent-facing storefront.
llms.txt Adoption Crosses 50,000 Domains as Perplexity Confirms Active Parsing
Why it matters for your score
Perplexity's public confirmation that its crawler actively parses and weights llms.txt content for business context, not just for crawl permissions but for answer synthesis, is the first major AI search engine to make this explicit. The 50K domain milestone means early-mover advantage is closing fast. Businesses with well-structured llms.txt files describing their services, pricing, and use cases are materially more likely to appear in Perplexity's sourced business recommendations than those relying on standard HTML alone.
What to do this week
- 1
Audit your llms.txt file this week against Perplexity's confirmed parsing behavior, specifically ensure your Services, Pricing, and Use Case blocks are explicit and machine-readable, not vague marketing copy. Use Faro's /tools/llms-txt generator to rebuild or validate your file against the current spec before the early-mover window closes further.
- 2
Run your site through Faro's /tools/ai-schema validator and prioritize fixing any missing PriceSpecification, ServiceType, or AggregateRating fields in your JSON-LD; these are the exact properties Google AI Overviews is now pulling into recommendation cards. A schema gap here is a direct citation loss.
- 3
If you offer any bookable, purchasable, or queryable service, assess your MCP readiness now using Faro's /tools/ai-readiness-scan, the GA launch with Stripe and Shopify integrations means agent-driven transaction flows are live, not theoretical. Knowing your current exposure score is the prerequisite to any MCP endpoint prioritization decision.