Agent readiness report

Is boodmo.com ready for AI agents?

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

Assessment

0 of 8 readable agent-readiness checks verified (1 could not be read: the site refused our request). 16 request(s) from our checker using AI crawler names were refused at the edge although robots.txt allows them. Bot protection often checks where a crawler comes from as well as its name, so the real crawlers may still get in: check your logs before changing anything. See per-protocol drawers for evidence and fix-it files.

Per-protocol results

Mcpno MCP endpoint declared in /.well-known/ucp, and none at the draft discovery addresses /.well-known/mcp.json, /.well-known/mcp or /mcp (MCP has no agreed discovery address yet)Not found
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
Ucpno /.well-known/ucpNot found
Ap2no /.well-known/ucp, so no AP2 declaration (AP2 is declared as a UCP capability)Not found
Openapicould not read /api/openapi.json (401) - the site refused our request, so this is not a findingCould not read
Llms Txtno /llms.txtNot found
Wikidatano Wikidata match for "boodmo" [searched: boodmo; Wikidata replied: website search 200 (0 results), search 200 (0 results)]Not found

.well-known files

.well-known/mcp.json6500 bytes200
Mcp Well Known Alt6500 bytes200
/mcp endpoint6500 bytes200
Ai Plugin Legacy6500 bytes200
.well-known/agent.json6500 bytes200
.well-known/agent-card.json6500 bytes200
Anp Discovery6500 bytes200
Anp Did6500 bytes200
Openapi Well Known6500 bytes200
Openapi Root6500 bytes200
Openapi Apicould not read401
Ucp Profile6500 bytes200
Llms Txt6500 bytes200
Llms Full Txt6500 bytes200
robots.txt408 bytes200
sitemap.xml3986 bytes200

AI crawler audit

0 of 18 AI user-agents reached the homepage; 16 returned an error to a request carrying their user-agent string although robots.txt allows it.
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.
These were requests from our checker carrying the crawlers' names. Bot protection often checks where a crawler comes from as well as its name, so the real crawlers may still get in - check your logs before changing anything.
OAI-SearchBotHTTP 403Refused
anthropic-aiHTTP 403Refused
ClaudeBotHTTP 403Refused
Claude-UserHTTP 403Refused
Claude-SearchBotHTTP 403Refused
PerplexityBotHTTP 403Refused
Perplexity-UserHTTP 403Refused
BingbotHTTP 403Refused

Fix these first

  1. Let our checker read your site: 1 of our checks could not be read (OpenAPI), 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. llms.txt: Publish /llms.txt: a plain text file at your site root that lists your key pages (main categories, best sellers, shipping and returns) with one line on each. You can write it yourself in an hour.
  3. UCP: Publish a UCP profile at /.well-known/ucp so AI agents can find your catalog, cart and checkout. Shopify serves one for every store; on other platforms it takes an app or a developer.
  4. MCP: Run an MCP server and declare it, for example at /.well-known/mcp.json, so AI assistants can search your catalog as a tool. The initialize handshake has to succeed, not just return a 200.
  5. 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.
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 boodmo.com

On boodmo.com (Custom), 0 of 8 readable agent standards are in place. Missing: Mcp, Webmcp, A2a, Anp, Ucp, Ap2, Llms Txt, Wikidata.

Without JavaScript, your brand name does not appear in the raw HTML, so crawlers that do not run JS see an empty shell.

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

Make boodmo.com agent-ready

Start with the highest-impact gap: Mcp. 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 boodmo.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?