Allegro · Agent Readiness

Discoverability

Can agents find your site and its capabilities?

failWebMCP / agent-protocol tools discoveredAgent manifests

The page registers no tools via the WebMCP browser API (navigator.modelContext).

Fix: Expose your actions to AI agents with the WebMCP browser API: register tools via navigator.modelContext.registerTool. Optionally also publish a /.well-known/webmcp.json tool catalog as a discovery signpost.

pass/llms.txt guide for AI agentsAgent manifests

Found https://allegro.pl/llms.txt.

pass/llms.txt lists key pages as markdown linksAgent manifests

Found at least one "[name](url)" markdown link.

pass/llms.txt has a summary blockquoteAgent manifests

Found a "> summary" blockquote.

pass/llms.txt opens with an H1 titleAgent manifests

First line is a top-level "# Title" heading.

Understanding

Can agents understand your content?

warnMarkdown content negotiationOpen agent protocols

Homepage returned 403 for Accept: text/markdown.

Operability

Can agents actually operate the page?

failWebMCP tools registered with the browserWebMCP tools

The page registers no tools via the navigator.modelContext browser API, so an AI agent has no structured way to operate it.

Fix: Expose your site’s actions to AI agents with the WebMCP browser API: call navigator.modelContext.registerTool({ name, description, inputSchema, execute }) from your page so an agent can invoke them. Implement it directly, or with a library like the @mcp-b polyfill (https://mcp-b.ai). Spec: https://github.com/webmachinelearning/webmcp.

passAccessibility tree is agent-navigableAccessibility

All 3 agent-critical accessibility audits passed — an agent can perceive and operate the page through its accessibility tree.

pass`[aria-hidden="true"]` is not present on the document `<body>`Accessibility

`[aria-hidden="true"]` is not present on the document `<body>` passed.

passDocument has a `<title>` elementAccessibility

Document has a `<title>` element passed.

pass`<frame>` or `<iframe>` elements have a titleAccessibility

`<frame>` or `<iframe>` elements have a title passed.

passOverall accessibility scoreAccessibility

Lighthouse accessibility score: 94/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.

passCumulative Layout ShiftPerformance

0.020 (field data from CrUX) — good.

passTime to First BytePerformance

482ms (field data from CrUX) — good.

infoTool catalog signpost publishedWebMCP tools

No tool catalog was found at /.well-known/webmcp.json (or /.well-known/webmcp). The catalog is a community convention, not part of the WebMCP standard, so this does not affect WebMCP presence.

Fix: Consider also publishing a tool catalog at /.well-known/webmcp.json: a JSON document with a "spec" of "webmcp/0.1" and a "tools" array, where each tool declares a name and a clear description. It is a community convention (optional, not part of the WebMCP standard) that lets crawlers and agents discover your tools without executing JavaScript.

Trust & Security

Can agents safely transact?

failagent-protocols.web-bot-auth (uncaught error)Open agent protocols

Checker threw: (r.errorCode ?? "").startsWith is not a function

warnOAuth protected-resource metadataOpen agent protocols

/.well-known/oauth-protected-resource returned 404.

Fix: Publish /.well-known/oauth-protected-resource so AI agents discovering your OAuth setup can negotiate flows automatically. Required if your site offers an authenticated API.

passOAuth authorization server metadataOpen agent protocols

/.well-known/oauth-authorization-server returns parseable JSON.