io.github.Syfer-web/krexel-mcp
NPM · KREXEL-MCP
Ship and edit static sites from any MCP-compatible AI. The AI is the brain; Krexel is the hands.
Available components
Last scanned (20 hours ago)
Scores higher than 58% of npm servers
Category CI/CD and DevOps
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 → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 95 dependencies flagged as unhealthy. 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 107 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 714 tokens (~79/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
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 4 Nov 2026 · Analysed npm/krexel-mcp@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
edit_file ~215
Patch a file on a live deployed site and ship a new patch deploy. The AI decides what to change; the MCP ships the patch. Returns the new deploy_id + preview_url.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Alias for value (kept for ergonomics on create). If both given, value wins. |
| deploy_id | string | yes | The BASE deploy to patch on top of. The new patch deploy will have this as its parent_deploy_id. |
| file | string | yes | Path of the file to create/replace/delete. |
| find | string | – | For replace/replace_all: the exact substring to find inside the file's current content. |
| message | string | – | Optional human-readable note stored with the patch deploy. |
| op | string | yes | create = new file (requires value/content); replace = first match (requires find + value); replace_all = every match (requires find + value); delete = remove file. |
| value | string | – | For create/replace/replace_all: the new text. |
No output schema declared.
No examples provided.
get_logs ~45
Get build logs for a deploy. In Phase 1 these are mocked from the local manifest; Phase 2 will stream from the orchestrator.
| Name | Type | Req | Description |
|---|---|---|---|
| deploy_id | string | yes | – |
No output schema declared.
No examples provided.
get_status ~21
Return current account, deploy count, platform, and state directory.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_deploys ~42
List recent deploys from the local Krexel state file. Optionally filter by domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
list_files ~54
List the files in a deployed site (paths, sizes, sha256). Returns metadata only — use read_file to fetch content.
| Name | Type | Req | Description |
|---|---|---|---|
| deploy_id | string | yes | The deploy_id returned from ship_site (or any patch deploy). |
No output schema declared.
No examples provided.
read_file ~83
Read a single file's contents from a deployed site. Path is relative to the site root (e.g. 'index.html', 'assets/logo.svg').
| Name | Type | Req | Description |
|---|---|---|---|
| deploy_id | string | yes | The deploy_id that contains the file. |
| path | string | yes | Path inside the deploy. No leading slash, no '..'. Examples: 'index.html', 'css/main.css'. |
No output schema declared.
No examples provided.
rollback ~58
Mark a previous deploy as the current 'last_good' for a domain. Phase 2 will actually push the rollback; Phase 1 just records intent.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| to | string | yes | deploy_id to roll back to |
No output schema declared.
No examples provided.
set_env ~66
Encrypt and persist an environment variable for a domain. Stored at $KREXEL_HOME/env/<domain>.enc with AES-256-GCM using KREXEL_MASTER_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| key | string | yes | – |
| value | string | yes | – |
No output schema declared.
No examples provided.
ship_site ~130
Upload a built site folder to Krexel. Zips the folder, stages it locally, and POSTs to the Krexel orchestrator API. Returns a deploy_id (always) and preview_url. If the orchestrator is unreachable the response carries an `api_ok: false` flag with the upstream error — never fakes success.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Custom domain to attach (e.g. shop.example.com). |
| folder | string | yes | Absolute or ~-relative path to the built site directory. |
| framework | string | – | Build framework hint. Default 'auto' detects from package.json. |
No output schema declared.
No examples provided.
How do I install the io.github.Syfer-web/krexel-mcp server?
io.github.Syfer-web/krexel-mcp runs locally as an npm package, launched with npx -y krexel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · krexel-mcp
claude mcp add syfer-web-krexel-mcp -- npx -y krexel-mcp
What is the io.github.Syfer-web/krexel-mcp server?
io.github.Syfer-web/krexel-mcp is listed in the public MCP registry as io.github.Syfer-web/krexel-mcp. Ship and edit static sites from any MCP-compatible AI. The AI is the brain; Krexel is the hands. This page covers its npm package (krexel-mcp).
Is the io.github.Syfer-web/krexel-mcp server safe to use?
io.github.Syfer-web/krexel-mcp scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Syfer-web/krexel-mcp server expose?
io.github.Syfer-web/krexel-mcp exposes 9 tools: ship_site, list_deploys, get_logs, rollback, set_env, and 4 more. Their descriptions and schemas cost roughly 714 tokens of context every time the server is loaded.
Is the io.github.Syfer-web/krexel-mcp server still maintained?
io.github.Syfer-web/krexel-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Syfer-web/krexel-mcp server under?
io.github.Syfer-web/krexel-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.