What does the agent readiness check test?

Real protocol probes of .well-known files (openapi.json, mcp.json, ai-plugin.json, security.txt), a live MCP initialize handshake, A2A agent-card validation, a 20-user-agent crawler audit, and a JS-parity check.

Is church-footwear.com ready for AI agents?

AI agent readiness report · platform: Custom · checked 2026-10-31 · log in to re-run

11%

Readiness

1/9

Verified

Custom

Platform

Not agent-ready

Mcp

Webmcp

A2a

Anp

Ucp

Ap2

Openapi

Llms Txt

Wikidata

3/18 AI crawlers reached the homepage15 blocked

Ranks above 15% of 220 sites checkedcorpus avg 25/100

Not agent-ready

church-footwear.com has 1 of 9 readable agent standards in place; missing Mcp, Webmcp, A2a, Anp, Ucp, Ap2, Openapi, Llms Txt.

Assessment

1 of 9 readable agent-readiness checks verified. 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

Openapino /openapi.json, /api/openapi.json, or /.well-known/openapi.jsonNot found

Llms Txtno /llms.txtNot found

WikidataWikidata entity Q2967663 (Church's)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 Discoverynot found404

Anp Didnot found404

Openapi Well Knownnot found404

Openapi Rootnot found404

Openapi Apinot found410

Ucp Profilenot found404

Llms Txtnot found404

Llms Full Txtnot found404

robots.txt891 bytes200

sitemap.xml997 bytes200

AI crawler audit

3 of 18 AI user-agents reached the homepage.

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.

What this means for church-footwear.com

On church-footwear.com (Custom), 1 of 9 readable agent standards are in place: Wikidata. Missing: Mcp, Webmcp, A2a, Anp, Ucp, Ap2, Openapi, Llms Txt.

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

church-footwear.com scores higher than 15% of the 220 sites checked here so far; the average readiness score is 25/100.

Make church-footwear.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 church-footwear.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 71 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?