Can agents find your site and its capabilities?
The site registers callable WebMCP tools with the browser at runtime, so an AI agent can operate the page through them.
Found a parseable Agent Skills index at https://agentchecker.ai/.well-known/agent-skills/index.json.
Found a Markdown guide at /AGENTS.md.
/.ai.txt found and parseable.
Found a parseable Linkset at https://agentchecker.ai/.well-known/api-catalog.
Found https://agentchecker.ai/llms.txt.
Found at least one "[name](url)" markdown link.
Found a "> summary" blockquote.
First line is a top-level "# Title" heading.
Crawled 12 of 12 discovered pages beyond the homepage.
Could not identify a known website platform (custom stack or unrecognised).
Can agents understand your content?
Homepage returns text/markdown when requested.
Homepage server response contains 787 words of visible text — content is reachable without executing JavaScript.
Homepage contains ~403 elements.
9 headings, no level skips.
Language declared as "en".
34 internal links found.
All four landmark elements present (main, header, footer, nav).
Exactly one <h1> on the homepage.
All 12 reachable key pages have both a <title> and <h1>.
All 12 pages return ≥80 words of visible text without JavaScript.
Can agents actually operate the page?
All 9 agent-critical accessibility audits passed — an agent can perceive and operate the page through its accessibility tree.
`[aria-*]` attributes match their roles passed.
`[aria-hidden="true"]` is not present on the document `<body>` passed.
`[role]`s have all required `[aria-*]` attributes passed.
`[role]` values are valid passed.
`[aria-*]` attributes are valid and not misspelled passed.
`[aria-*]` attributes have valid values passed.
Buttons have an accessible name passed.
Document has a `<title>` element passed.
Links have a discernible name passed.
Lighthouse accessibility score: 97/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.
2 of 2 visible interactive form fields have labels.
0.100 (field data from CrUX, for this page). Good.
379ms (field data from CrUX, for this page). Good.
3 tool(s) registered via the WebMCP browser API (navigator.modelContext).
All 3 registered tool(s) declare a name, description, and an object inputSchema.
2 tool(s) published at /.well-known/webmcp.json (spec webmcp/0.1). The catalog is a community convention signpost, not part of the WebMCP standard.
2: read_llms_txt, read_page_as_markdown
All 2 tool(s) declare a name and description.
3: start_agent_readiness_check, list_supported_standards, get_pricing
Can agents safely transact?
Certificate expires in 27 days (Oct 1 23:17:10 2026 GMT).
Fix: Renew within the week — automated renewal (Let's Encrypt + cron / certbot) avoids manual outages.
/.well-known/oauth-authorization-server returns parseable JSON.
/.well-known/oauth-protected-resource returns parseable JSON.
Signature / Signature-Input headers detected.
x-vercel-id: lhr1::mt6p8-1788531073447-9bca948a06f3 (Vercel)
CSP header present.
max-age=63072000, includeSubDomains=true, preload=true.
Homepage scheme is https:.
http://agentchecker.ai → https://agentchecker.ai/ (1 hop).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Referrer-Policy: strict-origin-when-cross-origin.
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.
X-Frame-Options: SAMEORIGIN.