Syke
Wraps static dependency analysis and git history mining into eight MCP tools that catch cascading breakage before your AI agent ships code. The core workflow is simple: your agent edits files freely, then calls gate_build before committing to get a PASS/WARN/FAIL verdict based on SCC condensation, PageRank importance scoring, and historical change coupling. Pro tier adds ai_analyze for semantic impact analysis using your own Gemini, OpenAI, or Anthropic key. Supports TypeScript, Python, Go, Rust, Java, C++, Ruby, and Dart out of the box with zero config. Spins up a localhost dashboard showing the full dependency graph with risk indicators and cascade depth. Best for codebases where foundation files have high fan-in and circular dependencies make manual impact assessment unreliable.
- GitHub stars
- 2
- tools
- 8
- auth
- Secret needed
- transport
- STDIO
- env vars
- 2
- last updated
- Feb 26, 2026
Tools
8 toolsPublic tool metadata for what this MCP can expose to an agent.
gate_buildMandatory pre-build check. Returns PASS/WARN/FAIL verdict before any build or deploy.
Mandatory pre-build check. Returns PASS/WARN/FAIL verdict before any build or deploy.
No parameter schema in public metadata yet.
check_safeQuick one-line safety verdict: HIGH/MEDIUM/LOW/NONE risk.
Quick one-line safety verdict: HIGH/MEDIUM/LOW/NONE risk.
No parameter schema in public metadata yet.
get_dependenciesLists internal imports (forward dependencies) of a file.
Lists internal imports (forward dependencies) of a file.
No parameter schema in public metadata yet.
analyze_impactFull impact analysis with SCC, risk scoring, and git coupling.
Full impact analysis with SCC, risk scoring, and git coupling.
No parameter schema in public metadata yet.
get_hub_filesRanks files by PageRank importance score.
Ranks files by PageRank importance score.
No parameter schema in public metadata yet.
refresh_graphRe-scans all source files and rebuilds the dependency graph.
Re-scans all source files and rebuilds the dependency graph.
No parameter schema in public metadata yet.
ai_analyzeAI semantic analysis (Gemini/OpenAI/Claude) of a file and its dependents.
AI semantic analysis (Gemini/OpenAI/Claude) of a file and its dependents.
No parameter schema in public metadata yet.
check_warningsReal-time monitoring alerts for file changes that may break dependents.
Real-time monitoring alerts for file changes that may break dependents.
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageConfiguration
SYKE_LICENSE_KEYsecretSYKE Pro license key (optional — Free tier works without it)
GEMINI_KEYsecretGoogle Gemini API key for AI semantic analysis (optional, Pro only)
Readme
SYKE — Your Codebase Has a Pulse
AI code impact analysis MCP server. SYKE monitors every file your AI touches, maps dependency graphs, detects cascading breakage, and gates builds before damage spreads.
Works with Claude Code, Cursor, Windsurf, and any MCP-compatible AI coding agent.
How It Works
- On startup, SYKE scans your source directory and builds a complete dependency graph using static import analysis.
- Your AI agent modifies files freely — no interruptions during normal work.
- Before build/deploy, the AI calls
gate_buildto check if all changes are safe. - If dependencies break, SYKE detects cascading failures and blocks the build with a
FAILverdict. - The dashboard shows a real-time visualization of your dependency graph with risk indicators.
SYKE is a safety net, not a gatekeeper. It doesn't block your AI while working — it catches what your AI missed before you ship.
Quick Start
Details
- Repository
- github.com/khalomsky/syke
- Package
@syke1/mcp-server- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active