Most of what SYKE knows is a single graph of what imports what, and the tools are different questions asked of it — check_safe for a one-line verdict, analyze_impact for the dependent list, get_hub_files for the files everything leans on, get_dependencies for the imports a file makes. That graph is a snapshot, which makes refresh_graph part of the routine after adding or removing files rather than a repair. The [CORTEX] tools leave the graph entirely: ai_analyze and scan_project read source through an external model, and scan_project says outright that you bring the key. Worth knowing before you plan around it — analyze_impact, get_hub_files, refresh_graph and check_warnings carry a [PRO] tag, so the dependent list sits behind that tag while check_safe's one-line verdict does not.
A dependency-graph server over your source tree that scores the blast radius of a file change, gates builds on that score, and can hand a file plus its dependents to an LLM for a semantic read.
- A verdict you call before a build: gate_build takes the changed files and returns PASS, WARN or FAIL with the reasons behind it, and its description marks it as the final check before any compilation or deployment.
- Blast radius on a named file: analyze_impact returns direct and transitive dependents with a risk level, and check_safe compresses the same question into a one-line HIGH, MEDIUM, LOW or NONE verdict carrying the count of impacted files.
- The graph read in the forward direction: get_dependencies lists the internal files a given file imports.
- Ranking by how much leans on a file: get_hub_files applies PageRank across the graph and returns the top_n files that the most other files depend on.
- A semantic read instead of a graph read: ai_analyze sends a file's source and its dependents to Gemini, OpenAI or Claude and explains what might break and how to change it safely.
- An onboarding document for a codebase you did not write: scan_project walks the whole project and reports architecture, key files, dependencies and patterns.
- Follow-up after the edit: check_warnings returns unresolved warnings from SYKE's real-time monitoring about changes that may have broken dependents, and clears them when acknowledge is set.
- refresh_graph re-scans the source files and rebuilds the dependency graph after files are added or removed.
The source tree itself, and an AI API key of your own for the [CORTEX] tools — scan_project states that it needs one (BYOK), and ai_analyze reads through Gemini, OpenAI or Claude. No environment credentials are configured. analyze_impact, get_hub_files, refresh_graph and check_warnings carry a [PRO] tag.
One command — npx @syke1/mcp-server@latest