Seo Ai Visibility

Three near-identical routers (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) collide, with the beta explicitly described as acting identically to the stable one, and the research entry points (ask_pipeworx, deep_research, compare_entities, entity_profile, recent_changes, validate_claim, bet_research) form a dense cluster of 'query the data' tools whose boundaries require careful reading. The polymarket family and memory trio are reasonably distinct, but the routing/ask cluster creates real misselection risk.

All names are consistently snake_case with no camelCase or style mixing. The verb_noun pattern holds for many (ai_visibility_check, bet_research, compare_entities, polymarket_fill_risk) but several are bare verbs or nouns (recall, remember, forget, subscribe, entity_profile), a minor deviation rather than a break.

32 tools is well above the comfortable 3-15 range and exceeds the 25+ threshold for 'too many.' While a multi-domain data gateway can justify breadth, the count is inflated by near-duplicate routers and a sprawling mix of domains that do not belong to the server's stated SEO/AI-visibility purpose.

The SEO/AI-visibility core is reasonably covered (visibility probing, competitor comparison, LLM-answer inspection, llms.txt generation) and the broader Pipeworx surface adds enormous reach with memory, subscription, and entity-resolution lifecycles intact. Minor gaps exist (no explicit visibility time-series tracking), but core workflows are covered.