ArchGuard MCP
Related Servers
Alternatives to ArchGuard MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceIndexes polyglot repositories into a local architecture graph resolving DI bindings, HTTP/gRPC/GraphQL routes, message queues, and ORM/SQL table lineage. Provides dozens MCP tools for call-chain tracing, blast-radius impact analysis, OpenCypher queries, and deterministic CI architectural gates.1620MIT
- AlicenseAqualityDmaintenanceArchitecture governance MCP server for AI-built codebases, enabling health checks, template management, and project scaffolding with migration support.55 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server for automated architectural mapping, security vulnerability detection, ML asset tracking, and code metrics in local repositories.-
- FlicenseNot gradedqualityCmaintenanceReal-time architecture governance tool that enforces Clean Architecture, DDD, SOLID, TDD, and Security rules across 8 languages using 11 specialized agents.-
- AlicenseNot gradedqualityBmaintenanceMCP server that provides tools for architecture analysis, risk diagnosis, quality metrics, and regression guarding to support AI-driven code review and incremental refactoring workflows.5MIT
- AlicenseAqualityCmaintenanceTamper-Evident Autonomous Agent Action Audit & Governance Logging MCP Server27 npmMIT
TDQS
Scored across 7 tools
audit_code_snippet and audit_codebase_architecture are nearly identical in function: both detect Tarjan SCC cycles, Ca/Ce/I coupling, the same 12 anti-patterns, and emit a 0-100 health score plus a Mermaid graph. The only differentiator is 'files vs repo directory', which is easy to misselect. The remaining tools (quorum/latency sim, hashing sim, migration audit, capacity math, architecture recommendation) are reasonably distinct, though simulate_quorum_and_tail_latency vs estimate_system_capacity both touch performance math.
Every tool follows a consistent snake_case verb_noun pattern (simulate_*, audit_*, check_*, estimate_*, recommend_*). Verbs are semantically meaningful and predictable, and no camelCase or stylistic mixing appears.
Seven tools is well within the ideal 3-15 range and each maps to a coherent phase of architecture review (analyze, simulate, audit, recommend). No filler or trivially redundant entries beyond the audit pair.
The surface covers architecture recommendation, capacity math, consistency/hashing simulation, code quality audit, and migration safety, which is strong lifecycle coverage for an advisory server. Minor gaps exist: no cost/cloud-spend estimation, no API/schema design analysis, and no runtime observability or SLO review, but agents can work around these.