io.github.khalomsky/syke
NPM · @SYKE1/MCP-SERVER · SCANNED AUG 3
AI code impact analysis — dependency graphs, cascade detection, and build gates for AI agents
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (97 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (97 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 155 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability49
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 460 tokens (~57/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @syke1/mcp-server
claude mcp add khalomsky-syke -- npx -y @syke1/mcp-server
codex mcp add khalomsky-syke -- npx -y @syke1/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"khalomsky-syke": {
"type": "local",
"command": [
"npx",
"-y",
"@syke1/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add khalomsky-syke --command npx --arg -y --arg @syke1/mcp-server
mcp_servers:
khalomsky-syke:
command: "npx"
args: ["-y", "@syke1/mcp-server"] {
"mcpServers": {
"khalomsky-syke": {
"command": "npx",
"args": [
"-y",
"@syke1/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +42
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 2 Aug 26 −9
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 +48
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: fair functional
- First check of Schema quality: fail functional
- Licence: MIT functional
- 26 Jul 26 25
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/@syke1/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 97 packages
97 packages in the resolved dependency tree · 97 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
ai_analyze ~68
[PRO] Use AI (Gemini/OpenAI/Claude) to perform semantic analysis on a file. Reads the file's source code and its dependents to explain what might break when modified and how to safely make changes.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Source file path to analyze with AI |
No output schema declared.
No examples provided.
analyze_impact ~62
[PRO] Analyze which files are impacted when a given file is modified. Returns direct and transitive dependents with risk level.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Source file path (absolute or relative to source directory). Example: "features/auth/data/auth_repository.dart" |
No output schema declared.
No examples provided.
check_safe ~48
Quick safety check for modifying a file. Returns a one-line verdict: HIGH/MEDIUM/LOW/NONE risk with impacted file count.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Source file path to check |
No output schema declared.
No examples provided.
check_warnings ~86
[PRO] Check for unresolved warnings from SYKE's real-time monitoring. Returns warnings about file changes that may have broken dependents. Use this AFTER modifying files to see if SYKE caught any issues you may have missed. Pass acknowledge=true to clear warnings after reading them.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge | boolean | — | If true, mark all warnings as acknowledged after returning them (default: false) |
No output schema declared.
No examples provided.
gate_build ~81
MANDATORY: Call this BEFORE any build, deploy, or test command. Returns PASS, WARN, or FAIL verdict with detailed reasons. If FAIL, do NOT proceed with build — fix issues first. Always call this as the final check before any compilation or deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | — | Optional list of modified files (absolute or relative to source directory) |
No output schema declared.
No examples provided.
get_dependencies ~31
List the internal files that a given file imports (forward dependencies).
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Source file path |
No output schema declared.
No examples provided.
get_hub_files ~54
[PRO] Rank files by how many other files depend on them (PageRank). High-hub files are risky to modify.
| Name | Type | Req | Description |
|---|---|---|---|
| top_n | number | — | Number of top files to return (default 10) |
No output schema declared.
No examples provided.
refresh_graph ~30
[PRO] Re-scan all source files and rebuild the dependency graph. Use after adding/removing files.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.