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 youthtothepeople.com ready for AI agents?

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

Readiness

0/7

Verified (readable)

Custom

Platform

Not agent-ready

Mcp

Webmcp

A2a

Anp

Ucp

Ap2

Openapi

Llms Txt

Wikidata

4/20 AI crawlers reached the homepage16 blocked

Ranks above 0% of 127 sites checkedcorpus avg 24/100

Not agent-ready

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

Assessment

0 of 7 readable agent-readiness checks verified (2 could not be read: the site refused our request). 16 AI crawler(s) blocked at the edge despite robots.txt allowing them. See per-protocol drawers for evidence and fix-it files.

Per-protocol verdicts

Mcpcould not read /mcp (403) - 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/did.jsonNot found

Ucpno /.well-known/agentic-commerce.json (and platform is not a UCP-shipping host)Not found

Ap2no /.well-known/ap2.jsonNot found

Openapicould not read /openapi.json (403), /api/openapi.json (403) - the site refused our request, so this is not a findingCould not read

Llms Txtno /llms.txtNot found

Wikidatano Wikidata match for "Youth To The People - Effective Formulas For Your Healthiest Skin"Not found

.well-known files

.well-known/mcp.jsonnot found404

Mcp Well Known Altnot found404

/mcp endpointcould not read403

Ai Plugin Legacynot found404

.well-known/agent.jsonnot found404

.well-known/agent-card.jsonnot found404

Anp Didnot found404

Openapi Well Knownnot found404

Openapi Rootcould not read403

Openapi Apicould not read403

Ucp Well Knownnot found404

Ap2 Well Knownnot found404

Llms Txtnot found404

Llms Full Txtnot found404

robots.txt852 bytes200

sitemap.xmlcould not read403

AI crawler audit

4 of 20 AI user-agents reached the homepage; 16 returned an error to a request carrying their user-agent string although robots.txt allows it.

GPTBotHTTP 403Blocked

OAI-SearchBotHTTP 403Blocked

ChatGPT-UserHTTP 403Blocked

anthropic-aiHTTP 403Blocked

ClaudeBotHTTP 403Blocked

Claude-UserHTTP 403Blocked

Google-ExtendedHTTP 403Blocked

BingbotHTTP 403Blocked

What this means for youthtothepeople.com

On youthtothepeople.com (Custom), 0 of 7 readable agent standards are in place. Missing: 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.

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

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

Does youthtothepeople.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?