ArchGuard MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Use ArchGuard tools before finalizing architecture designs, database migrations, or capacity math. Never guess QPS/storage/quorum math when deterministic calculators are available.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_codebase_architectureA | Scan a local repository directory on disk to detect circular module dependencies (Tarjan SCC), coupling/instability hotspots (Ca/Ce/I), layer boundary violations, and 12 production reliability/security/SOLID anti-patterns (N+1 queries in loops, missing HTTP timeouts, unbounded caches, check-then-act races, SQL/command injection, God modules). Outputs a 0-100 health score and Mermaid dependency graph. |
| audit_code_snippetA | Analyze one or more source files for circular module dependencies (Tarjan SCC), coupling/instability metrics (Ca/Ce/I), and 12 production reliability/security/SOLID anti-patterns (N+1 loops, missing HTTP timeouts, unbounded caches, check-then-act races, missing idempotency keys, SQL/command injection, God classes). Returns a 0-100 health score, prioritized findings, and Mermaid dependency graph. |
| check_migration_safetyB | Audit a SQL migration (PostgreSQL, MySQL, or SQLite) for production table locks, rolling-deployment breaking changes (DROP/RENAME COLUMN, blocking CREATE INDEX, ADD COLUMN NOT NULL without DEFAULT, ALTER COLUMN TYPE rewrite, unvalidated constraints, missing lock_timeout), and auto-generate a safe 3-phase Expand-Contract deployment plan. |
| estimate_system_capacityA | Compute exact back-of-the-envelope distributed systems capacity math: avg & peak Write/Read QPS, cache-adjusted DB QPS, N-year raw & replicated storage, peak ingress/egress Gbps, Redis RAM sizing, primary shard count + dominant bottleneck, and Little’s Law peak concurrency. Supports Big Tech presets (tinyurl, twitter, whatsapp, uber, youtube, stripe) or custom numbers. |
| simulate_quorum_and_tail_latencyA | Verify Dynamo quorum consistency (W + R > N, split-brain write safety W > N/2), Raft consensus fault tolerance, and Jeff Dean tail-latency amplification (1 - (1 - p)^K) across parallel microservice fanout calls with hedged-request comparison. |
| simulate_consistent_hashingA | Run a deterministic FNV-1a 32-bit consistent hashing ring simulation to measure exact shard load skew (min/max/std-dev) and key remapping percentage when scaling out by 1 node compared against naive modulo hashing. |
| recommend_architectureB | Generate a Staff-level distributed system architecture blueprint (primary database, caching & stampede control, contention strategy, messaging/CDC, real-time transport, reliability guardrails, and matching Big Tech In-The-Wild case studies) from concrete workload traits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| staff-architecture-review | Perform a rigorous Staff Engineer architecture & production reliability review of a repository or module. |
| zero-downtime-migration-plan | Audit a SQL migration for lock/rolling-deploy hazards and produce a safe 3-phase Expand-Contract plan. |
| system-design-interview-sim | Run a calibrated 45-minute Big Tech HLD/LLD mock interview backed by deterministic capacity & quorum calculations. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Jeff Dean Latency Numbers & Powers of 2 | |
| 6 Core System Design Patterns Matrix | |
| Zero-Downtime Database Migration Playbook (Expand-Contract) | |
| Big Tech Staff/Senior System Design Rubrics (Microsoft, Google, Amazon, Meta) |
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.