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 meindl.de ready for AI agents?

AI agent readiness report · platform: WooCommerce · checked 2026-11-02 · log in to re-run

33%

Readiness

1/3

Verified (readable)

WooCommerce

Platform

Not agent-ready

Mcp

Webmcp

A2a

Anp

Ucp

Ap2

Openapi

Llms Txt

Wikidata

17/18 AI crawlers reached the homepage1 blocked

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

Not agent-ready

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

Assessment

1 of 3 readable agent-readiness checks verified (6 could not be read: the site refused our request). Detected platform: WooCommerce. See per-protocol drawers for evidence and fix-it files.

Per-protocol results

Mcpcould not read /.well-known/ucp (429) - 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

A2acould not read /.well-known/agent.json (429), /.well-known/agent-card.json (429) - the site refused our request, so this is not a findingCould not read

Anpcould not read /.well-known/agent-descriptions (429) - the site refused our request, so this is not a findingCould not read

Ucpcould not read /.well-known/ucp (429) - the site refused our request, so this is not a findingCould not read

Ap2could not read /.well-known/ucp (429) - the site refused our request, so this is not a findingCould not read

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

Llms Txtno /llms.txtNot found

WikidataWikidata entity Q2056117 (Meindl)Verified

.well-known files

.well-known/mcp.jsonnot found404

Mcp Well Known Altnot found404

/mcp endpointnot found404

Ai Plugin Legacynot found404

.well-known/agent.jsoncould not read429

.well-known/agent-card.jsoncould not read429

Anp Discoverycould not read429

Anp Didnot found404

Openapi Well Knowncould not read429

Openapi Rootcould not read429

Openapi Apicould not read429

Ucp Profilecould not read429

Llms Txtnot found404

Llms Full Txtnot found404

robots.txt6096 bytes200

sitemap.xml1999 bytes200

AI crawler audit

17 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 meindl.de

On meindl.de (WooCommerce), 1 of 3 readable agent standards are in place: Wikidata. Missing: Webmcp, Llms Txt.

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

meindl.de scores higher than 46% of the 220 sites checked here so far; the average readiness score is 25/100.

Make meindl.de agent-ready on WordPress

meindl.de runs on WordPress / WooCommerce. Add the .well-known files via a plugin or server config, stand up an MCP endpoint, and make sure caching or security plugins are not blocking AI crawlers. Start with Webmcp.

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 meindl.de 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