Is hotter.com ready for AI agents?

AI agent readiness report · platform: Custom · checked 2026-10-22 · log in to re-run
13%
Readiness
1/8
Verified (readable)
Custom
Platform
13%1/8
Not agent-ready
Mcp
Webmcp
A2a
Anp
Ucp
Ap2
Openapi
Llms Txt
Wikidata
0/18 AI crawlers reached the homepage18 blocked
Ranks above 31% of 127 sites checkedcorpus avg 24/100

Not agent-ready

hotter.com has 1 of 8 readable agent standards in place; missing Mcp, Webmcp, A2a, Anp, Ucp, Ap2, Llms Txt. 1 could not be read because the site refused our request (Openapi), so they are not counted.

Assessment

1 of 8 readable agent-readiness checks verified (1 could not be read: the site refused our request). 18 AI crawler user-agent(s) got an error at the edge although robots.txt allows them. See per-protocol drawers for evidence and fix-it files.

Per-protocol verdicts

Mcpno /.well-known/mcp.json, /mcp, or /.well-known/mcpNot 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/did.jsonNot found
Ucpno /.well-known/ucpNot found
Ap2no /.well-known/ap2.jsonNot found
Openapicould not read /api/openapi.json (500) - the site refused our request, so this is not a findingCould not read
Llms Txtno /llms.txtNot found
WikidataWikidata entity Q91919346 (Hotter)Verified

.well-known files

.well-known/mcp.jsonnot found404
Mcp Well Known Altnot found404
/mcp endpointnot found404
Ai Plugin Legacynot found404
.well-known/agent.jsonnot found404
.well-known/agent-card.jsonnot found404
Anp Didnot found404
Openapi Well Knownnot found404
Openapi Rootnot found404
Openapi Apicould not read500
Ucp Profilenot found404
Ap2 Well Knownnot found404
Llms Txtnot found404
Llms Full Txtnot found404
robots.txt390 bytes200
sitemap.xml991 bytes200

AI crawler audit

0 of 18 AI user-agents reached the homepage; 18 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.
GPTBotHTTP 403Blocked
OAI-SearchBotHTTP 403Blocked
ChatGPT-UserHTTP 403Blocked
anthropic-aiHTTP 403Blocked
ClaudeBotHTTP 403Blocked
Claude-UserHTTP 403Blocked
Claude-SearchBotHTTP 403Blocked
PerplexityBotHTTP 403Blocked

What this means for hotter.com

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

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

hotter.com scores higher than 31% of the 127 sites checked here so far; the average readiness score is 24/100.

Make hotter.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 a verdict.

Does hotter.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 64 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?