No user-submitted related servers found.
Scored across 85 tools
Many tools overlap heavily: get_user_by_id, get_user_by_username, get_user_by_short_uuid, find_user, and resolve_user all retrieve the same resource, and the stats surface (get_stats, get_stats_digest, get_bandwidth_stats, get_nodes_statistics, get_nodes_metrics, get_recap, get_node_usage, get_stats_nodes_usage, get_stats_nodes_users_usage, get_stats_node_users_usage, get_internal_squad_usage, get_internal_squad_user_usage) is a wall of near-identical names. Some descriptions (e.g. panel_overview, user_report, find_user) explicitly steer away from duplication, but the boundaries are still unclear for many pairs.
Virtually all names are snake_case and the vast majority are get_<resource> reflecting the underlying REST endpoints, so the pattern is predictable. A handful of verb variants (find_user, resolve_user, geocheck_node, panel_overview, user_report, sharing_suspects, node_connections) break the get_ prefix but remain consistent in style.
85 tools is far beyond a well-scoped set and essentially exposes the entire REST API one-to-one, including near-duplicate stats and lookup endpoints. Agents must choose among dozens of highly similar reads, which is the extreme end of tool-count mismatch.
The surface is almost entirely read-only ([READ] endpoints); there are no create/update/delete operations for users, nodes, squads, hosts, or config profiles, so a management workflow dead-ends as soon as a mutation is needed. The read/reporting coverage is broad, but lifecycle coverage for the domain is severely lacking.
