No user-submitted related servers found.
Scored across 24 tools
Most tools have clearly distinct purposes across graph discovery, diagnostics, incident lifecycle, and topology writes. A few read-only graph tools such as get_blast_radius, trace_dependency_path, and recent_changes are related but distinguishable by their descriptions.
The set is predominantly consistent snake_case with verb_noun names such as get_logs, open_incident, resolve_incident, and rollback_service. Minor deviations like recent_changes and map_overview are still readable and fit the domain.
At 24 tools, the surface is heavy for an incident-response server and borders on being difficult to scan. Each tool has a role, but the count could likely be reduced by combining some graph-reading operations.
The server covers the core lifecycle well: discovery, diagnosis, incident opening/resolution, ownership, runbooks, change tracking, flags, and recovery actions. Minor gaps exist around deleting or updating certain entities such as dependencies and runbooks, though query_graph provides an escape hatch for reads.