A
licenseA
qualityA
maintenanceDependency intelligence for AI agents. CVE scanning, health checks, upgrade planning.
9
113 npm
2
Apache 2.0
Blast Radius MCP
by kystron
Related Servers
Alternatives to Blast Radius MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to map cross-repository dependencies, detect breaking changes in API contracts, and assess impact across services.10MIT
- FlicenseAqualityDmaintenanceProvides AI coding agents with dependency analysis, impact detection, and build verification tools.14-
- AlicenseNot gradedqualityAmaintenanceProvides a dependency graph of any local repository with tools for change impact, transitive dependents, health audits, and more, enabling AI coding agents to see structure and refactor safely.4,912 npm4MIT
- FlicenseNot gradedqualityDmaintenanceAI-native code intelligence graph that builds a persistent knowledge graph of your codebase in Neo4j and exposes it to AI assistants via MCP, enabling contextual code analysis, impact analysis, and dependency tracking.23-
- AlicenseNot gradedqualityAmaintenanceProvides AI coding agents with an embedded knowledge graph and architecture governance tools, enabling blast radius analysis, compliance checks, and smart context extraction from codebases.Apache 2.0
TDQS
C2.5/5.0
Scored across 4 tools
Disambiguation4/5
Each tool has a distinct focus: blast radius analysis, upgrade impact simulation, security auditing, and visualization. However, dependency_blast_radius and dependency_upgrade_analysis both deal with impact analysis, which could cause mild confusion without careful description reading.
Naming Consistency3/5
All names use snake_case, but the pattern is inconsistent: three are noun phrases (dependency_blast_radius, dependency_upgrade_analysis, security_audit_graph) while one is a verb phrase (open_dependency_visualizer). The 'dependency' prefix is repeated, but the lack of a uniform verb_noun structure reduces predictability.
Tool Count5/5
With only 4 tools, the server is tightly scoped to its stated purpose of dependency and security analysis. Each tool covers a distinct aspect, and the count feels appropriate rather than thin or bloated.
Completeness4/5
The server covers core analysis, upgrade simulation, security auditing, and visualization, which covers the main workflows for dependency blast radius. Minor gaps exist, such as missing a simple dependency graph listing or direct comparison tools, but these are not critical for the domain.
Maintenance
ActivitySlowing
ResponsivenessNo issues