not analyzable — no source code found to analyze
MCP stdio server that scans a repository once and answers architecture questions from an evidence-backed graph, so agents stop re-reading the source tree to work out what depends on what. Scans PHP, TypeScript/JavaScript, and Python out of process and exposes 25 tools for impact analysis, dependency cycles, boundary policies, and diagram export.
Drift inferred · capture-to-capture
No drift recorded — single capability capture; advisories appear once its surface changes.
tools
-
architecture_context
architecture-context
-
architecture_health
architecture-health
-
architecture_summary
architecture-summary
-
architecture_trends
architecture-trends
-
change_impact
change-impact
-
changed_files_impact
changed-files-impact
-
check_architecture
check-architecture
-
cleanup_stale_scans
cleanup-stale-scans
-
dependency_cycles
dependency-cycles
-
explain_flow
explain-flow
-
export_diagram
export-diagram
-
file_metrics
file-metrics
-
find_component
find-component
-
impact_analysis
impact-analysis
-
inspect_component
inspect-component
-
list_boundaries
list-boundaries
-
list_projects
list-projects
-
list_snapshots
list-snapshots
-
maintain_database
maintain-database
-
quality_gate
quality-gate
-
remove_project
remove-project
-
scan_project
scan
-
search_architecture
search-architecture
-
snapshot_diff
snapshot-diff
-
suggest_location
suggest-location
last analysis: no-source
No code evidence — the analyzed source reached for no tracked permissions, tools, or hooks.