ArcSight MCP Server
Related Servers
Alternatives to ArcSight MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to analyze repository architecture, changed-file and diff impact, dependency and endpoint exposure, API contract compatibility, architecture boundaries, bounded capacity simulations, and security/quality evidence through MCP tools.3Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to query a locally indexed codebase graph for symbol definitions, immediate callers and callees, and multi-hop downstream dependency impact analysis through MCP tools.MIT
- AlicenseBqualityBmaintenanceEnables AI coding agents to compile repositories into high-signal, cache-pinned context and to query dependency centrality, blast radius, AST skeletons, circular dependencies, hotspots, and auto-generated agent rules through MCP tools.71MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally search, query, and understand codebases with token-efficient context, dependency graphs, history, architecture diagrams, and metrics through MCP.15 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to query a local, continuously updated symbol graph of a codebase, providing ranked search, caller/callee exploration, dependency paths, and git-diff impact analysis through MCP tools.14 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to query a codebase as a knowledge graph, providing token-budgeted context, search, and impact analysis via MCP tools.27 PyPIMIT
TDQS
Scored across 4 tools
check_file_impact and check_diff_impact both analyze impact but are distinguished by scope (single file vs. changed files), and their descriptions clarify this. plan_fix and architecture_status serve clearly different purposes, though the two impact tools could still be momentarily confused.
Three tools follow a verb_noun pattern (check_file_impact, check_diff_impact, plan_fix) in snake_case, while architecture_status is a noun phrase. This is a minor deviation but still readable and consistent in casing.
Four tools are reasonable for a focused architecture impact analysis server, covering the core read-only operations without bloat. It sits at the lower end but each tool has a distinct role.
The set covers file impact, diff impact, architecture status, and mechanical fix planning, which are the core workflows. Minor gaps exist—no tool to apply a fix or inspect a specific dependency graph—but agents can work around these for the stated advisory purpose.