No user-submitted related servers found.
Scored across 5 tools
The five tools have mostly distinct roles: an aggregate audit (check), a focused robots.txt line matcher (robots_test), an llms.txt validator, an llms.txt generator, and a static crawler registry. The only real overlap is that `check` subsumes some robots.txt and llms.txt inspection that robots_test and llms_validate perform in depth, but the descriptions make the aggregate-vs-deep-dive boundary clear.
Three tools follow a clear noun_verb pattern (robots_test, llms_validate, llms_generate), but `check` is a bare verb and `crawlers` a bare noun, so the pattern is not predictable across the set. Readable, but an agent cannot infer a name from a new operation.
Five tools is well matched to a narrow AI-readiness auditing domain, with each tool covering a distinct artifact (robots.txt, llms.txt validation, llms.txt generation, crawler list, full audit). Nothing appears redundant or padded.
The surface covers the core lifecycle: enumerate crawlers, test robots rules, validate and generate llms.txt, and run a combined audit. Minor gaps exist in that structured-data and sitemap analysis are only reachable through the aggregate `check`, with no dedicated or configurable operation for them.