No user-submitted related servers found.
Scored across 46 tools
Most tools have clearly distinct purposes: bing_* tools handle official Bing Webmaster API data retrieval, seo_* tools do independent page scanning, aeo_* tools handle AI/SEO analysis, and indexnow_* tools handle IndexNow notifications. A few could cause confusion (e.g., bing_get_url_traffic_info vs bing_get_url_info vs bing_get_fetched_url_details, and bing_get_page_stats vs bing_get_page_query_stats), though descriptions do clarify differences.
The tools follow a consistent verb_noun pattern with prefixes (bing_, seo_, aeo_, indexnow_) dividing responsibility domains. Within each prefix, verbs like get_, submit_, scan_, audit_, and prepare_ are used consistently. Minor deviation: verb ordering is not fully uniform (get_query_page_stats vs get_query_page_detail_stats), and bing_get_page_stats vs bing_get_page_query_stats invert the hierarchy between page and query.
At 46 tools this is on the heavy side, exceeding the 25+ threshold that signals high cognitive load. The breadth is justified by the combined scope (Bing Webmaster API, independent SEO scanning, AI visibility analysis, WordPress prep, and IndexNow), but an agent facing 46 tools with four distinct prefixes will have a large decision space. Still, the server has a genuinely broad purpose, so this is not extreme bloat.
The surface is notably comprehensive: it covers site listing, query/page/rank/crawl/keyword/link stats, sitemap management, URL submission (single, batch, sitemap, IndexNow), crawling issues, technical SEO scanning, AI-visibility analysis, and even fix preparation with WordPress integration. Minor gaps exist (e.g., no tool to remove or delete a sitemap, no tool to manage verification beyond listing, and the autofix flow depends on an externally connected WordPress MCP), but the main workflows are well covered.