Scan at scaleSites with a misconfigured agent-ready signal
Sites with a misconfigured agent-ready signal
A site-wide report: one row per host, over the access rows the crawl emitted.
What this report returns
Every agent-ready site-wide signal the crawled site publishes but got wrong, one row per signal per host: access policies, sitemaps, the llms.txt index, the MCP server card, MCP authorization, OpenAPI, NLWeb, UCP, Web Bot Auth, the A2A agent card. Signal Defects names each check that failed and Signal Findings says what was found and what to change, so this is the triage screen: it tells you which of a host's signals need work without opening each signal's report in turn.
How to fix it. Work through Signal Findings row by row, then open the report named in the Signal column, where each defect is a filterable column with its own spec citation and a worked example (this table deliberately cites no single specification, because it spans ten of them). Signal Assessment says whether the verdict covers the whole signal: on a "partial" row a defect we found is still real, but the parts a budget or read cap stopped us reading were not judged.
Signals a site never adopted don't appear here at all, because absence is not a failure.
The columns it shows
Every defect this technology can carry is a column in the grid, worst first, so nothing is hidden behind a filter you have to know to apply.
- Host
host - Signal
signal - Signal Defects
signalDefects - Signal Findings
signalFindings - Signal Assessment
signalAssessment - Signal Valid
signalValid
Running it
This report ships in the Lumar agent-readiness container and appears on any project it is linked to, on every crawl. See the whole set, or check a single URL with the scanner on this site, which runs the same code with no account.