No user-submitted related servers found.
Scored across 10 tools
check_identity is effectively a superset that internally reports robots.txt crawler policy (check_ai_access), identity files (check_identity_files), and Organization schema (check_page_signals), so an agent faces four overlapping readings of the same site and must infer granularity versus composite. The analyze_site/get_analysis and visibility_fixes trio is better separated, and descriptions do explain the differences, but the overlap between the local checks and check_identity is real.
All snake_case and readable, but verb conventions are mixed: check_* for four tools, then analyze_site, get_analysis (which does not match its partner's noun), visibility_fixes (noun-only), compare_sites, and inite_connect. Predictable in the check_* family but not across the set.
Ten tools is a sensible scope for an AI-visibility auditing service. However, check_ai_access, check_identity_files, and check_page_signals feel like decompositions of check_identity, so the count is slightly inflated by near-redundant granular tools.
Coverage is strong: crawler policy, identity files, page health, full audit, run retrieval, fixes, comparison, and history all exist for the stated domain. The main gap is that get_analysis needs a known run_id with no tool to list prior audits or runs, and there is no cancel/delete for an in-flight audit.