io.github.YawLabs/caddy-mcp
NPM · @YAWLABS/CADDY-MCP · SCANNED AUG 4
MCP server for managing Caddy web servers via the admin API
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 Security83
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2242 tokens (~101/item across 22 items; 18 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 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 · @yawlabs/caddy-mcp
claude mcp add yawlabs-caddy-mcp -- npx -y @yawlabs/caddy-mcp
codex mcp add yawlabs-caddy-mcp -- npx -y @yawlabs/caddy-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yawlabs-caddy-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@yawlabs/caddy-mcp"
],
"enabled": true
}
}
} openclaw mcp add yawlabs-caddy-mcp --command npx --arg -y --arg @yawlabs/caddy-mcp
mcp_servers:
yawlabs-caddy-mcp:
command: "npx"
args: ["-y", "@yawlabs/caddy-mcp"] {
"mcpServers": {
"yawlabs-caddy-mcp": {
"command": "npx",
"args": [
"-y",
"@yawlabs/caddy-mcp"
]
}
}
} 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 Aug 26 0
- CVE-2026-69207 affects this package: medium ▼ security
- Known CVEs: partial → fail ▼ security
- 2 Aug 26 +26
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Maintenance: pass → unverified ▼ functional
- License: pass → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −11
- Known CVEs: partial → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- 31 Jul 26 −7
- 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 +39
- Provenance: unverified → fail ▼ security
- Malware scan: pass → unverified ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 29 Jul 26 −28
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- 27 Jul 26 47
First indexed and scored.
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 Aug 2026 · Analysed npm/@yawlabs/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-8j4g-w8fx-2239 | CVE-2026-69207 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 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.
caddy_adapt ~176
Convert a config in any registered adapter format to Caddy JSON without loading it. Useful for previewing what a Caddyfile produces, or for porting from nginx/yaml configs when Caddy is built with the matching adapter module ('caddyfile' is built-in; 'nginx', 'yaml', etc. require their adapter modules to be compiled into the Caddy binary). Returns the adapted JSON and any warnings separately.
| Name | Type | Req | Description |
|---|---|---|---|
| adapter | string | — | Config format adapter. Must match an adapter Caddy was built with. Built-in: 'caddyfile' (default). Common external adapters: 'nginx' (caddy-nginx-adapter), 'yaml' (caddy-yaml). |
| config | string | yes | The raw config text (e.g., Caddyfile contents, nginx.conf, yaml) |
No output schema declared.
No examples provided.
caddy_add_route ~134
Add a route with full control over match conditions and handlers. Supports any Caddy handler (reverse_proxy, file_server, static_response, redirect, encode, headers, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| handle | array | yes | Array of handler objects (e.g., [{ handler: 'file_server', root: '/var/www' }]) |
| match | array | yes | Array of match objects (e.g., [{ host: ['example.com'], path: ['/api/*'] }]) |
| server | string | — | Caddy server name (default: srv0) |
| terminal | boolean | — | Stop processing further routes after this one matches |
No output schema declared.
No examples provided.
caddy_config_by_id ~189
Access config by @id tag. Any config object with an '@id' field can be read, updated, or deleted by its ID instead of needing its full path. This is the recommended way to manage individual routes and config objects. The 'delete' action requires confirm=true.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | Action to perform |
| confirm | boolean | — | Must be true to actually delete (only enforced for action='delete') |
| id | string | yes | The @id value of the config object |
| mode | string | — | For 'set' action: 'overwrite' = PATCH (replace existing, default), 'append' = POST (add to arrays, create on objects), 'insert' = PUT (insert at array index) |
| subpath | string | — | Optional sub-path within the identified object |
| value | — | — | New value (required for 'set' action) |
No output schema declared.
No examples provided.
caddy_config_delete ~107
Delete config at a JSON path. Removes the config node at the specified path. Deleting a parent node also deletes every descendant -- e.g. deleting 'apps/http/servers/srv0' removes that server and all of its routes. Requires confirm=true.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | — | Must be true to actually delete the config node (safety) |
| path | string | yes | Config path to delete (e.g., 'apps/http/servers/srv0/routes/0') |
No output schema declared.
No examples provided.
caddy_config_get ~70
Read Caddy config at any JSON path. Returns the full config when path is empty, or a subtree at a specific path (e.g., 'apps/http/servers/srv0/routes').
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | — | Config path (e.g., 'apps/http/servers/srv0') |
No output schema declared.
No examples provided.
caddy_config_set ~172
Write config at a JSON path. Mode 'overwrite' (default) replaces existing values (PATCH) — safe and idempotent. Mode 'append' adds to arrays or creates keys (POST) — NOT idempotent: calling twice with the same route duplicates it. Mode 'insert' places at a specific array index (PUT) — useful for route ordering.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | — | 'overwrite' = PATCH (replace existing, default, idempotent), 'append' = POST (add to arrays / create keys, NOT idempotent), 'insert' = PUT (insert at array index) |
| path | string | yes | Config path to write to (e.g., 'apps/http/servers/srv0/routes') |
| value | — | yes | The JSON value to set at the path |
No output schema declared.
No examples provided.
caddy_list_routes ~46
List all routes on a Caddy HTTP server with a human-readable summary of matchers and handlers.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | — | Caddy server name (default: srv0) |
No output schema declared.
No examples provided.
caddy_list_servers ~40
List all configured HTTP servers with their names, listen addresses, route counts, and TLS status. Use this to discover server names before calling route tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
caddy_load ~98
Replace the entire Caddy configuration atomically. Accepts a JSON config object, or a Caddyfile string with format='caddyfile'. This is the safest way to make large config changes. Has a 60-second timeout to allow for TLS provisioning.
| Name | Type | Req | Description |
|---|---|---|---|
| config | — | yes | Full config — JSON object or Caddyfile text string |
| format | string | — | Config format: 'json' (default) or 'caddyfile' |
No output schema declared.
No examples provided.
caddy_metrics ~223
Get Prometheus metrics from Caddy. Shows request counts, durations, TLS handshake stats, active connections, and more. Output can be megabytes on busy servers -- use `filter` to keep only metrics whose name contains a substring (e.g. 'http_requests' or 'tls'); HELP/TYPE comment lines for retained metrics are kept. Filter-mode drops blank lines and free-form '# comment' lines (including '# EOF'); only '# HELP'/'# TYPE' lines for matching metrics are kept. Use `max_lines` to cap the response (default 500); a trailing comment reports how many lines were dropped.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | — | Substring to match against metric names. Keeps sample lines whose metric name contains this substring, plus their `# HELP` and `# TYPE` comment lines. Empty/absent = no filtering. Label values are NO… |
| max_lines | integer | — | Maximum number of output lines (default 500). Excess lines are dropped and a summary is appended. |
No output schema declared.
No examples provided.
caddy_pki ~52
Get PKI certificate authority info or the CA certificate chain.
| Name | Type | Req | Description |
|---|---|---|---|
| ca | string | — | CA ID (default: 'local') |
| certificates | boolean | — | If true, return the full CA certificate chain |
No output schema declared.
No examples provided.
caddy_remove_route ~154
Remove a route. Target by @id (preferred — stable across reorderings) or by array index on a specific server. Index-based removal is a two-step read-then-delete and can race against concurrent edits; prefer @id when possible.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | — | Must be true to actually remove the route (safety) |
| id | string | — | The @id of the route to remove (preferred — stable even if routes get reordered) |
| index | integer | — | Zero-based index of the route in the server's routes array (only used if id is not provided) |
| server | string | — | Caddy server name when using index (default: srv0). Ignored when id is provided. |
No output schema declared.
No examples provided.
caddy_reverse_proxy ~367
Add a reverse proxy route. The most common operation — just specify where traffic comes from and where it goes. Example: from='api.local' to=['localhost:3000']. When `id` is OMITTED the route is appended to the server's routes array — calling the tool twice with the same args produces TWO duplicate routes (non-idempotent). When `id` is SUPPLIED the route is written via PUT under that @id, so repeat calls REPLACE in place (idempotent). Strongly recommended: supply a stable `id` for any route managed from automation or production tooling. Note: @ids are config-global in Caddy (NOT route-scoped). If `id` collides with an @id used by a non-route object (TLS issuer, server, etc.) the call refuses with an error rather than clobbering it. Once an @id is registered to a route under one server, subsequent calls update that route in place regardless of the `server` argument.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Domain, path, or domain/path to match (e.g., 'api.local', '/api/*', 'app.local/ws') |
| id | string | — | Optional stable @id for the route. When set, repeat calls REPLACE the route in place (idempotent). When omitted, the route is APPENDED — calling twice with identical args creates a duplicate route. @… |
| server | string | — | Caddy server name (default: srv0) |
| to | array | yes | Upstream addresses (e.g., ['localhost:3000', 'localhost:3001']) |
No output schema declared.
No examples provided.
caddy_revert ~113
Manage config snapshots for rollback. Snapshots are auto-captured before caddy_load and kept in-memory (last 10). Actions: 'list' shows snapshots with timestamps, 'save' manually captures the current config, 'apply' restores a snapshot (requires confirm=true).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| confirm | boolean | — | Must be true to actually apply a snapshot (safety) |
| index | integer | — | Snapshot index for 'apply' (0 = most recent, default) |
No output schema declared.
No examples provided.
caddy_status ~30
Check Caddy connectivity and get a config summary: servers, routes, listen addresses, and TLS status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
caddy_stop ~39
Gracefully shut down the Caddy server. Requires confirm=true to prevent accidental shutdown.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true to confirm shutdown |
No output schema declared.
No examples provided.
caddy_tls ~108
Get or configure TLS/HTTPS settings. Actions: 'status' shows current TLS config, 'set_email' sets the ACME email, 'set_acme_ca' sets the ACME CA URL. Works on both fresh and existing Caddy instances.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| ca | string | — | ACME CA URL (for 'set_acme_ca' action) |
| string | — | ACME email address (for 'set_email' action) |
No output schema declared.
No examples provided.
caddy_upstreams ~32
Get the current health status of all reverse proxy upstreams. Shows address, active requests, and failure counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.