Delimit Cli MCP Server

delimit-cli npm v4.18.6 Source verified

Published by delimit-ai — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

The merge gate for AI-written code, with signed, replayable attestation. Works with Claude Code, Codex, Cursor, and Gemini CLI.

Trust grade
C
79/100
Last scanned get badge →
Trust
C · 79/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
C Why this grade threat 85 − adoption risk = 79/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 15.4 = 85. What the published surface and source actually contain:

PointsWhat was foundCategory
−14.2 Untrusted input concatenated into a command sink ×8 MTC-SRC-009 injection
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 85 − 6 = 79. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 24

high Dynamic code execution in server code (gateway/ai/backends/tools_infra.py)MTC-SRC-001

In the server's implementation (`gateway/ai/backends/tools_infra.py:102`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: r"\beval\s*\(", "Use of eval() — potential code injection", "high"), # nosec B-eval_usage: regex-pattern DEFINITION str

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server gateway/ai/backends/tools_infra.py

high Shell/command execution in server code (bin/delimit-cli.js)MTC-SRC-002

In the server's implementation (`bin/delimit-cli.js:7`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ync, spawn } = require('child_process'); const os = require('os'); const chalk = require('chalk'); const inquirer = requ

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server bin/delimit-cli.js

high Shell/command execution in server code (bin/delimit-setup.js)MTC-SRC-002

In the server's implementation (`bin/delimit-setup.js:13`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execSync } = require('child_process'); const os = require('os'); // Shared prompt gate: false when stdin/stdout is not

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server bin/delimit-setup.js

high Shell/command execution in server code (bin/delimit.js)MTC-SRC-002

In the server's implementation (`bin/delimit.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: , execSync } = require('child_process'); const fs = require('fs'); const path = require('path'); const os = require('os'

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server bin/delimit.js

high Shell/command execution in server code (gateway/ai/backends/deploy_bridge.py)MTC-SRC-002

In the server's implementation (`gateway/ai/backends/deploy_bridge.py:295`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: proc = subprocess.run( ["npm", "view", "delimit-cli", "version"], capture_outpu

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server gateway/ai/backends/deploy_bridge.py

high Shell/command execution in server code (gateway/ai/backends/gateway_core.py)MTC-SRC-002

In the server's implementation (`gateway/ai/backends/gateway_core.py:560`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: y: result = subprocess.run( ["git", "describe", "--tags", "--abbrev=0"], cwd

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server gateway/ai/backends/gateway_core.py

high Shell/command execution in server code (gateway/ai/backends/git_health.py)MTC-SRC-002

In the server's implementation (`gateway/ai/backends/git_health.py:37`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: return subprocess.check_output( cmd, cwd=cwd, stderr=subprocess.DEV

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server gateway/ai/backends/git_health.py

high Shell/command execution in server code (gateway/ai/backends/governance_bridge.py)MTC-SRC-002

In the server's implementation (`gateway/ai/backends/governance_bridge.py:48`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: result = subprocess.run( ["git", "status", "--porcelain"], capture_output=True, t

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server gateway/ai/backends/governance_bridge.py

high Shell/command execution in server code (gateway/ai/backends/ops_bridge.py)MTC-SRC-002

In the server's implementation (`gateway/ai/backends/ops_bridge.py:61`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: tags = subprocess.run(["git", "tag", "-l"], capture_output=True, text=True, timeout=10) tag_lis

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server gateway/ai/backends/ops_bridge.py

high Shell/command execution in server code (gateway/ai/backends/repo_bridge.py)MTC-SRC-002

In the server's implementation (`gateway/ai/backends/repo_bridge.py:64`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: result = subprocess.run(["git", "-C", str(root), "ls-files"], capture_output=True, text=True, timeout=10)

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server gateway/ai/backends/repo_bridge.py

high Shell/command execution in server code (gateway/ai/backends/tools_design.py)MTC-SRC-002

In the server's implementation (`gateway/ai/backends/tools_design.py:68`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: nue probe = subprocess.run( [c, "-c", "import playwright"], capture_output=True, timeout=10

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server gateway/ai/backends/tools_design.py

medium Hardcoded egress to an external endpoint (bin/delimit-cli.js)MTC-SRC-003

In the server's implementation (`bin/delimit-cli.js:2298`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: await axios.post('https://delimit.ai/api/subscribe', { email: betaAns.email, source: 'cli-init' });

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server bin/delimit-cli.js

medium Untrusted input concatenated into a command sink (bin/delimit-cli.js)MTC-SRC-009

In the server's implementation (`bin/delimit-cli.js:2511`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try { execSync(`git clone --depth 1 https://github.com/delimit-ai/delimit-quickstart.git "${targetDir}

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server bin/delimit-cli.js

medium Untrusted input concatenated into a command sink (bin/delimit-setup.js)MTC-SRC-009

In the server's implementation (`bin/delimit-setup.js:121`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const ver = execSync(`${cmd} --version 2>&1`, { encoding: 'utf-8' }).trim(); const match = ver.m

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server bin/delimit-setup.js

medium Untrusted input concatenated into a command sink (bin/delimit.js)MTC-SRC-009

In the server's implementation (`bin/delimit.js:211`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: layer...', GREEN); execSync(`node ${path.join(__dirname, '../../scripts/install-governance.js')}`); } else {

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server bin/delimit.js

medium Untrusted input concatenated into a command sink (lib/api-engine.js)MTC-SRC-009

In the server's implementation (`lib/api-engine.js:44`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try { execSync(`${cmd} --version`, { stdio: 'pipe' }); return cmd; } catch {}

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server lib/api-engine.js

medium Untrusted input concatenated into a command sink (lib/attest-mcp.js)MTC-SRC-009

In the server's implementation (`lib/attest-mcp.js:153`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: y { verifyOut = execSync(`git verify-tag --raw ${tag}`, { cwd: repoDir, encoding: 'utf-8', timeout:

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server lib/attest-mcp.js

medium Untrusted input concatenated into a command sink (lib/auth-setup.js)MTC-SRC-009

In the server's implementation (`lib/auth-setup.js:611`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try { execSync(`ssh-keygen -t ed25519 -C "${email}" -f ${keyPath} -N ""`, { stdio: 'pipe' });

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server lib/auth-setup.js

medium Untrusted input concatenated into a command sink (lib/cross-model-hooks.js)MTC-SRC-009

In the server's implementation (`lib/cross-model-hooks.js:99`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const active = execSync(`systemctl is-active ${serviceName} 2>/dev/null`, { encoding: 'utf-8', timeout: 2000 })

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server lib/cross-model-hooks.js

medium Untrusted input concatenated into a command sink (lib/hooks-installer.js)MTC-SRC-009

In the server's implementation (`lib/hooks-installer.js:142`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try { execSync(`git config --global core.hooksPath ${this.hooksDir}`); console.log(chalk.g

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server lib/hooks-installer.js

medium Dynamic module load from a non-literal (gateway/ai/activate_helpers.py)MTC-SRC-005

In the server's implementation (`gateway/ai/activate_helpers.py:359`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: __import__(pkg) except ImportError: dep_ok = False checklist.app

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server gateway/ai/activate_helpers.py

medium Dynamic module load from a non-literal (gateway/ai/server.py)MTC-SRC-005

In the server's implementation (`gateway/ai/server.py:8368`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: mod = __import__(import_name) ver = getattr(mod, "__version__", getattr(mod, "VERSION", "i

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server gateway/ai/server.py

medium Dynamic module load from a non-literal (gateway/core/zero_spec/express_extractor.py)MTC-SRC-005

In the server's implementation (`gateway/core/zero_spec/express_extractor.py:35`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: le; try { appModule = require(modulePath); } catch (e) { console.log(JSON.stringify({ error: "Import failed: " + e.m

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server gateway/core/zero_spec/express_extractor.py

low Package runs install-time scripts (postinstall)MTC-SUP-010

"delimit-cli" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: node scripts/postinstall.js

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package delimit-cli

What this scan could not see

Versions 6

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v4.18.6 latest C 79/100 24 1.13.0 2026-09-07
v4.18.3 C 79/100 24 1.13.0 2026-09-06
v4.18.2 C 79/100 24 1.13.0 2026-09-04
v4.17.0 C 79/100 24 1.13.0 2026-09-01
v4.16.4 C 79/100 24 1.13.0 2026-08-27
Show 1 more version ↓
v4.16.3 C 79/100 24 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: C · 79/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/delimit-cli/badge.svg)](https://mcptrustchecker.com/registry/delimit-cli)
HTML
<a href="https://mcptrustchecker.com/registry/delimit-cli"><img src="https://mcptrustchecker.com/registry/delimit-cli/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/delimit-cli/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan delimit-cli --online

Use the free API → How scoring works

More in Developer Tools