Agent readiness report

Is tacobell.com ready for AI agents?

AI agent readiness report · platform: Custom · checked 2026-11-21 · log in to re-run
11%
Not agent-ready
tacobell.com · 4 standards read
tacobell.com has 1 of 4 readable agent standards in place; missing Webmcp, A2a, Anp. 5 could not be read because the site refused our request (Mcp, Ucp, Ap2, Openapi, Llms Txt), so they are not counted.
Not agent-readyCustom1/4 readable verified
Agent standards verified1/4
Mcp
Webmcp
A2a
Anp
Ucp
Ap2
Openapi
Llms Txt
Wikidata
0/18 AI crawlers reached the homepage (18 blocked)0%
Ranks above 56% of 285 sites checked (corpus avg 21/100)56%

Assessment

1 of 4 readable agent-readiness checks verified (5 could not be read: the site refused our request). Our request with an ordinary browser user-agent was refused too, so the crawler results describe our checker being blocked, not rules about AI crawlers. See per-protocol drawers for evidence and fix-it files.

Per-protocol results

Mcpcould not read /.well-known/ucp (no response) - the site refused our request, so this is not a findingCould not read
Webmcpno navigator.modelContext.register, <script type="webmcp">, or <link rel="modelcontext"> in HTMLNot found
A2ano /.well-known/agent.json or /.well-known/agent-card.jsonNot found
Anpno /.well-known/agent-descriptions and no did:wba identity at /.well-known/did.jsonNot found
Ucpcould not read /.well-known/ucp (no response) - the site refused our request, so this is not a findingCould not read
Ap2could not read /.well-known/ucp (no response) - the site refused our request, so this is not a findingCould not read
Openapicould not read /.well-known/openapi.json (no response), /openapi.json (no response), /api/openapi.json (no response) - the site refused our request, so this is not a findingCould not read
Llms Txtcould not read /llms.txt (no response) - the site refused our request, so this is not a findingCould not read
WikidataWikidata entity Q752941 (Taco Bell)Verified

.well-known files

.well-known/mcp.json138709 bytes200
Mcp Well Known Alt138709 bytes200
/mcp endpoint138709 bytes200
Ai Plugin Legacy138709 bytes200
.well-known/agent.json138709 bytes200
.well-known/agent-card.json138709 bytes200
Anp Discovery138709 bytes200
Anp Did138709 bytes200
Openapi Well Knowncould not read404
Openapi Rootcould not read404
Openapi Apicould not read404
Ucp Profilecould not read404
Llms Txtcould not read404
Llms Full Txtcould not read404
robots.txtcould not read404
sitemap.xmlcould not read404

AI crawler audit

0 of 18 AI user-agents reached the homepage.
Our request with an ordinary browser user-agent was refused as well (HTTP 0 before, 0 after). This site was blocking our checker, so read these counts as "could not check", not as rules about AI crawlers.
9 of 18 were tested with the operator's published user-agent string and the rest with the bare token, since no published string was found. A request that only names a user-agent does not prove the real crawler would be treated the same.

Fix these first

  1. Let our checker read your site: 5 of our checks could not be read (MCP, UCP, AP2, OpenAPI, llms.txt), so they are left out of your score. Serve /.well-known/*, /llms.txt and /robots.txt to automated requests without a block or a redirect, then run the check again.
  2. WebMCP: Register WebMCP tools on your storefront so AI built into the browser can search your catalog and add to cart on the page itself.
  3. A2A: Publish an A2A agent card at /.well-known/agent.json if you run an agent that other agents can hand tasks to.
  4. ANP: ANP lets agents prove who they are. It is the least used standard we check; leave it until the others are in place.
Run it again for today's result, then sign up free for one fix file per gap. Not yours? Put your own store in.

What this means for tacobell.com

On tacobell.com (Custom), 1 of 4 readable agent standards are in place: Wikidata. Missing: Webmcp, A2a, Anp.

Without JavaScript, your brand name still appears in the raw HTML, so crawlers that do not run JS can read it.

tacobell.com scores higher than 56% of the 285 sites checked here so far; the average readiness score is 21/100.

Make tacobell.com agent-ready

Start with the highest-impact gap: Webmcp. Publish a working MCP endpoint at /.well-known/mcp.json (the initialize handshake must succeed, not just return 200), add an A2A agent card, and keep the crawler path clean.

Frequently asked questions

Are these real probes or AI guesses?

Real probes. We fetch the actual files, run a real MCP initialize handshake, and validate A2A cards against their schema. No model decides the result.

Does tacobell.com need every standard to pass?

No. Start with the highest-impact gap above, then add the rest. Most sites win the most by shipping a working MCP endpoint and keeping the crawler path clean.

Check your own site free

Run the same protocol probes on any URL, then sign up free for the copy-paste fix-it files and the full 20-crawler audit.

Run a free check

Agent readiness on Custom

We have checked 123 other sites on Custom. The Custom hub aggregates protocol verification rates and average readiness scores across every Custom site checked here.

Is Custom ready for AI agents?