Caddy (yawlabs) MCP Server
@yawlabs/caddy-mcp
npm
v2.4.0
Published by @yawlabs — 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 for managing Caddy web servers via the admin API
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. 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:
| Points | Adoption-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 |
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 2
high Shell/command execution in server code (bin/caddy-mcp.mjs)MTC-SRC-002
In the server's implementation (`bin/caddy-mcp.mjs:77`): 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 } from "node:child_process"; import { existsSync } from "node:fs"; import { constants, homedir } from "node:o
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/caddy-mcp.mjs
medium Dynamic module load from a non-literal (bin/caddy-mcp.mjs)MTC-SRC-005
In the server's implementation (`bin/caddy-mcp.mjs: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: = SERVER_ENTRY; await import(SERVER_URL.href); } const mode = (process.env.CADDY_MCP_RUNTIME ?? "auto").toLowerCase()
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/caddy-mcp.mjs
Tools 18
Each tool and what it can reach — statically extracted from the published source.
caddy_adaptno sensitive capabilitycaddy_add_routeno sensitive capabilitycaddy_config_by_idno sensitive capabilitycaddy_config_deleteno sensitive capabilitycaddy_config_getno sensitive capabilitycaddy_config_setno sensitive capabilitycaddy_list_routesno sensitive capabilitycaddy_list_serversno sensitive capabilitycaddy_loadno sensitive capabilitycaddy_metricsno sensitive capability
Show 8 more tools ↓
caddy_pkino sensitive capabilitycaddy_remove_routeno sensitive capabilitycaddy_reverse_proxyno sensitive capabilitycaddy_revertno sensitive capabilitycaddy_statusno sensitive capabilitycaddy_stopno sensitive capabilitycaddy_tlsno sensitive capabilitycaddy_upstreamsno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (18 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 4
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.4.0 latest |
A 93/100 | 2 | 1.13.0 | 2026-09-07 |
v2.3.2 |
A 93/100 | 2 | 1.13.0 | 2026-08-31 |
v2.2.0 |
A 93/100 | 2 | 1.12.1 | 2026-08-23 |
v1.3.1 |
A 99/100 | 0 | 1.12.1 | 2026-08-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.
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 @yawlabs/caddy-mcp --onlineOther implementations of Caddy 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Cloud & DevOps
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.