Syke: Ai Code Impact Analysis & Safety Gate

Created By
Hyun seok Yang3 months ago
An AI-powered MCP server that prevents broken builds by analyzing code impact in real-time. Syke provides a visual dependency map and a 'Safety Gate' to catch silent regressions before you commit. Essential for developers using AI coding agents like Cursor and Claude Code.
Overview

🛡️ SYKE: The Missing Map for AI Coding

AI coding agents are great, but they often lack a deep understanding of your codebase's hidden dependencies. SYKE bridges this gap by providing a real-time semantic dependency graph and a build-time safety gate.

🚀 Key Features

  • Impact Analysis: Automatically identify every file (direct or indirect) affected by a code change.
  • Safety Gate (gate_build): A final PASS/WARN/FAIL check before every build to prevent cascading failures.
  • Visual Dashboard: Access an interactive Cytoscape-powered dependency map at localhost:3333.
  • Zero Configuration: Out-of-the-box support for 8 languages including TypeScript, Go, Rust, and Python.
  • Real-time Monitoring: Instant feedback as you type—watch your dependency graph pulse in response to changes.

🛠️ Why use SYKE?

Prevent "silent regressions" where changing a utility in one file breaks a service five layers deep. SYKE empowers your AI to code with confidence by giving it the architectural context it was never born with.

🎁 Pricing & Trial

  • 3-Day Full Pro Trial: Experience all premium features (Real-time monitoring, AI semantic analysis) for 72 hours upon first launch.
  • Free Tier: Essential impact analysis tools for small projects (up to 50 files).
  • Pro Tier: Unlimited files, real-time monitoring, and Gemini-powered deep analysis for $12/mo.

🏁 Quick Start

Simply add the server configuration above to your MCP client (Cursor, Claude Desktop, etc.) and launch your environment.

Server Config

{
  "mcpServers": {
    "syke": {
      "command": "npx",
      "args": [
        "-y",
        "@syke1/mcp-server@latest"
      ],
      "env": {
        "SYKE_LICENSE_KEY": "<YOUR_LICENSE_KEY_OR_EMPTY_FOR_TRIAL>"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
Hyun seok Yang
Star
-
Language
-
License
-
Category

Recommend Servers

View All
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

21 hours ago
Meok Bs7121 Mcp

7 hours ago