LLMScout
Related Servers
Alternatives to LLMScout
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server exposing Generative Engine Optimization tools to any AI agent, enabling checking of llms.txt, auditing robots.txt for AI crawlers, and validating JSON-LD schema.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceMCP server for website SEO + GEO analysis. Scan any URL to get scores across 5 categories (SEO, GEO, Performance, Security, Accessibility) with actionable fix recommendations. Enables AI coding assistants to audit websites and implement fixes autonomously.-

atomno-mcp-seo-auditofficial
AlicenseAqualityBmaintenanceMCP server for technical SEO audits, powered by the detail.web engine. Run a site audit straight from your AI agent to get a health score, issues across 8 categories, and a GEO sub-score.874 PyPI1MIT- AlicenseNot gradedqualityDmaintenanceOpen-source MCP server that audits websites for AI search readiness, providing deterministic scoring (0-100) and prioritized fix lists for metrics like JSON-LD, llms.txt, heading hierarchy, and AI crawler access.1MIT
- AlicenseAqualityDmaintenanceAn MCP server that gives AI agents tools to inspect a website's visibility to AI answer engines, including crawler permissions, llms.txt, structured data, on-page signals, and a full 29-check AI-readiness audit.539 npm1MIT
- AlicenseAqualityAmaintenanceProvides on-page SEO analysis via MCP tools, including page audits, schema extraction, robots.txt checks, sitemap parsing, and link analysis. No API keys required; works with any MCP-compatible client.56 npmMIT
TDQS
Scored across 1 tool
With only one tool, there is no risk of confusing it with another tool. The description clearly separates init, check, and fleet usage, so an agent can select the right subcommand via args without ambiguity.
The lone tool is named 'run,' which is readable but very generic and does not follow a domain-specific verb_noun convention. There is no inconsistency to penalize, but the name gives little signal about LLMScout's purpose or subcommands.
A single tool is thin for a server whose described scope includes scaffolding, single-site audits, and fleet audits. The CLI-wrapper pattern can justify one entry point, but separate init/check/fleet tools would improve discoverability.
The tool exposes init, check, fleet, and help discovery, covering the core scaffold-and-audit lifecycle. Minor gaps remain around dedicated operations for inspecting or updating existing configs and listing prior reports, though these may be reachable through CLI help.