Coding Agents MCP Server

@kadreio/mcp-coding-agents npm v1.6.3

Published by @kadreio — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server with multiple AI coding agents for enhanced development workflows

Trust grade
C
71/100
Last scanned get badge →
Trust
C · 71/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 78 − adoption risk = 71/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 − 22 = 78. What the published surface and source actually contain:

PointsWhat was foundCategory
−22 Hardcoded PEM private key in server code MTC-SRC-008 exfiltration

2. Client adoption risk — 78 − 7 = 71. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

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 11

high Hardcoded PEM private key in server code (dist/utils/self-signed-cert.js)MTC-SRC-008

A hardcoded PEM private key (a live-looking credential hardcoded in shipped code) appears in `dist/utils/self-signed-cert.js:139`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: PEM private key: ----…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server dist/utils/self-signed-cert.js

high Tool "execute_command" exposes command/code executionMTC-CAP-001

Tool "execute_command" appears to run shell commands or evaluate code (keyword "execute command" in tool name, parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool execute_command

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

In the server's implementation (`dist/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: { value: true }); const child_process_1 = require("child_process"); const path_1 = __importDefault(require("path")); con

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 dist/cli.js

high Shell/command execution in server code (dist/core/mcp-server-core.js)MTC-SRC-002

In the server's implementation (`dist/core/mcp-server-core.js:39`): 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: l/sdk/types.js"); const child_process_1 = require("child_process"); const claude_1 = require("../lib/agents/claude"); co

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 dist/core/mcp-server-core.js

high Shell/command execution in server code (dist/lib/agents/claude.js)MTC-SRC-002

In the server's implementation (`dist/lib/agents/claude.js:40`): 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: equire("crypto"); const child_process_1 = require("child_process"); const util_1 = require("util"); const claude_code_1

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 dist/lib/agents/claude.js

high Shell/command execution in server code (dist/lib/agents/codex.js)MTC-SRC-002

In the server's implementation (`dist/lib/agents/codex.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: ./utils/logger"); const child_process_1 = require("child_process"); const crypto_1 = require("crypto"); /** * Type guar

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 dist/lib/agents/codex.js

high Shell/command execution in server code (dist/lib/agents/gemini.js)MTC-SRC-002

In the server's implementation (`dist/lib/agents/gemini.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: ./utils/logger"); const child_process_1 = require("child_process"); /** * Type guard to check if an object is valid Gem

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 dist/lib/agents/gemini.js

high Shell/command execution in server code (dist/mcp-server-http.js)MTC-SRC-002

In the server's implementation (`dist/mcp-server-http.js:42`): 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: l/sdk/types.js"); const child_process_1 = require("child_process"); const crypto_1 = require("crypto"); const dotenv_1 =

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 dist/mcp-server-http.js

high Shell/command execution in server code (dist/utils/self-signed-cert.js)MTC-SRC-002

In the server's implementation (`dist/utils/self-signed-cert.js: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: ignedCertificate; const child_process_1 = require("child_process"); const fs = __importStar(require("fs")); const path =

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 dist/utils/self-signed-cert.js

medium Unconstrained command parameter "command" on "execute_command"MTC-CAP-006

Tool "execute_command" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool execute_command · inputSchema.properties.command

low Mutating tool "execute_command" declares no destructiveHintMTC-CAP-005

Tool "execute_command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool execute_command

Tools 6

Each tool and what it can reach — statically extracted from the published source.

  • execute_commandruns code / shell
  • calculate_bmino sensitive capability
  • get_timestampno sensitive capability
  • Server Configurationno sensitive capability
  • stream_sse_timestampsno sensitive capability
  • System Statisticsno sensitive capability

What this scan could not see

Versions 1

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
v1.6.3 latest C 71/100 11 1.13.0 2026-09-07

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 · 71/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/kadreio-mcp-coding-agents/badge.svg)](https://mcptrustchecker.com/registry/kadreio-mcp-coding-agents)
HTML
<a href="https://mcptrustchecker.com/registry/kadreio-mcp-coding-agents"><img src="https://mcptrustchecker.com/registry/kadreio-mcp-coding-agents/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/kadreio-mcp-coding-agents/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 @kadreio/mcp-coding-agents --online

Use the free API → How scoring works

More in Developer Tools