GEO MCP by DigestSEO
Related Servers
Alternatives to GEO MCP by DigestSEO
- AlicenseAqualityAmaintenanceEnables AI coding assistants to validate HTML/CSS markup using W3C APIs, perform technical SEO audits, check broken links, and validate JSON-LD schemas directly in local workspaces.82,854 npm7MIT
- AlicenseAqualityAmaintenanceOAuth-protected Google Search Console MCP for analytics, URL inspection, sitemap management, indexing requests, and SEO diagnostics. Open-source Cloudflare Workers implementation with 17 tools.174,051 npm5MIT
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server that lets an AI agent audit a page for SEO and GEO — on-page tags, structured data, robots.txt, sitemaps, hreflang, and whether ChatGPT, Claude, Perplexity and Gemini can actually crawl and cite you. No API keys required.1733 npm1MIT

optifeed-radarofficial
AlicenseAqualityBmaintenanceOpen-source CLI + MCP server that asks real AI engines (ChatGPT, Claude, Gemini, Perplexity) real buyer questions and scores whether a brand or its products get recommended (AI visibility / GEO / AEO). Runs locally with your own API keys.547 npm5MIT
seocrawl-mcpofficial
AlicenseBqualityDmaintenanceSEO + GEO MCP server: live Google Search Console & GA4 data, keyword and page analysis, AI-visibility tracking across ChatGPT, Claude, Gemini & Perplexity, site audit and SEO task management — all from chat.382MIT- AlicenseNot gradedqualityCmaintenanceSelf-hosted Google Search Console MCP server deployable to Cloudflare Workers, allowing natural language queries of GSC data via ChatGPT, Claude, or any MCP-capable client.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA production-ready MCP server for AI agents, providing deep web research and RAG capabilities via Cloudflare Workers.-
- AlicenseAqualityDmaintenanceA self-hosted MCP server that gives AI agents deep internet research capabilities — no API keys required, powered by SearxNG, Playwright, and Docker.497 npmISC
TDQS
Scored across 12 tools
Most tools are clearly separated by resource and action, and descriptions clarify temporal or comparison scope. The main ambiguity is between generate_prompts and set_prompts, which both replace active prompts and preserve history, and check_visibility versus get_visibility_history could cause a minor misselection for current data.
All tools use a consistent snake_case verb_noun pattern such as get_, list_, set_, refresh_, track_, update_, compare_, and check_. There are no mixed naming conventions or vague verbs.
Twelve tools is within the ideal 3-15 range and matches the server's scope: brand management, prompt management, visibility retrieval, and competitor analysis. Each tool has a distinct role without feeling padded or redundant.
The server covers brand creation/update/listing, prompt listing/setting/generation, and comprehensive visibility, citation, and competitor reads. The main gap is lifecycle deletion: there is no delete_brand or remove_prompt, though set_prompts can replace prompt sets as a partial workaround.