Scan at scaleSites with a broken NLWeb /mcp server
Sites with a broken NLWeb /mcp server
A site-wide report: one row per host, over the nlweb rows the crawl emitted.
What this report returns
NLWeb's MCP transport exposes the same natural-language querying as a standard MCP tool named ask.
A row appears here when any of these is wrong, worst first:
- DescriptionThe ask tool has no description, so an agent can't tell what it does or when to call it.Fix Give the tool a description, e.g.
"Ask a natural-language question about this site's content". - Query InputThe ask tool's
inputSchemadeclares no usable"query"property, so agents can't tell how to pass the question.Fix DeclareinputSchemawith a string"query"property (v0.55's query.text shape also counts).
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 - NLWeb MCP (/mcp) Valid
nlWebMcpValid - NLWeb MCP Findings
nlWebMcpFindings - NLWeb MCP (/mcp) Ask Tool Missing Description
nlWebMcpAskToolMissingDescription - NLWeb MCP (/mcp) Ask Tool Missing Query Input
nlWebMcpAskToolMissingInputSchema
About NLWeb endpoint
Microsoft's conversational /ask route returning schema.org answers.
Read how NLWeb endpoint is checked, including the specification it is validated against and a worked correct and broken example.
Running it
This report comes with Agentic Readiness in Lumar and appears on every crawl of any project that has it turned on. See the whole set, or check a single URL with the scanner on this site, which runs the same code with no account.