kd-scout
Related Servers
Alternatives to kd-scout
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA MCP server that turns your scattered SEO and analytics data into one clear verdict per URL. Plug it into Claude, Cursor, or any MCP-aware client and ask: "Which three posts should I update this week?" - and get an answer backed by hard numbers.8103 npm2MIT
- FlicenseCqualityCmaintenanceStandalone MCP server for the Mangools API with 82 tools covering keyword research, SERP analysis, rank tracking, backlinks, competitor research, and AI search visibility. Enables natural language interaction with Mangools SEO capabilities.82-
- AlicenseBqualityDmaintenanceMCP server & CLI for keyword research, domain analytics, backlinks, traffic analysis, and competitive intelligence using Semrush API data.7737 npm39MIT
- FlicenseAqualityDmaintenanceMCP server for advanced Google Search Console analysis — keyword cannibalization detection, page-level query deep dive, and rank change tracking.3-
- AlicenseNot gradedqualityAmaintenanceAn open-source, local-first MCP server for automated Schema.org JSON-LD generation, GA4 metric validation, /llm.txt auditing, and content stickiness analytics.MIT
- AlicenseNot gradedqualityCmaintenanceModel Context Protocol server for SignalSumo that lets Claude, Cursor, and other MCP-compatible clients read SEO data, run technical audits, research keywords, and check backlink profiles through natural-language tool calls.7 npmMIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose in the keyword research workflow: difficulty estimation, opportunity scoring, and content brief generation. There is meaningful sequential dependency, but no functional overlap that would confuse an agent.
All tool names follow the same lowercase snake_case pattern and describe their output: keyword_difficulty, opportunity_score, content_brief. The naming convention is predictable and easy to extend.
Three tools is perfectly scoped for this server's narrow purpose. Each tool fills a distinct step in the pipeline without redundancy or unnecessary bloat.
The set covers the core lifecycle from raw signals through difficulty and opportunity scoring to a content brief, leaving no obvious workflow dead end. It lacks built-in SERP or volume retrieval, but those appear to be external inputs rather than gaps in the server's stated scope.