# io.github.YawLabs/caddy-mcp (npm · @yawlabs/caddy-mcp)

MCP server for managing Caddy web servers via the admin API

- Trust score: 66/100 (medium)
- Change this week: +19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- npm · `@yawlabs/caddy-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/yawlabs-caddy-mcp/yawlabs-caddy-mcp.md), [page](https://verifymcp.io/servers/yawlabs-caddy-mcp/yawlabs-caddy-mcp)

## Channel facts

- Registry: `npm`
- Package: `@yawlabs/caddy-mcp`
- Version: `1.3.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 2242 tokens (~101/item across 22 items; 18 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add yawlabs-caddy-mcp -- npx -y @yawlabs/caddy-mcp
```

### Codex

```bash
codex mcp add yawlabs-caddy-mcp -- npx -y @yawlabs/caddy-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yawlabs-caddy-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@yawlabs/caddy-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yawlabs-caddy-mcp --command npx --arg -y --arg @yawlabs/caddy-mcp
```

### Hermes

```yaml
mcp_servers:
  yawlabs-caddy-mcp:
    command: "npx"
    args: ["-y", "@yawlabs/caddy-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "yawlabs-caddy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@yawlabs/caddy-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 66, 0)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail

### 2026-08-02 (score 66, +26)

- [security regression] Provenance: fail → unverified
- [security regression] Install scripts: pass → unverified
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional regression] Maintenance: pass → unverified
- [functional regression] License: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.23
- [functional] Licence: MIT

### 2026-08-01 (score 40, −11)

- [security regression] Known CVEs: partial → unverified
- [functional regression] Dependency health: partial → unverified

### 2026-07-31 (score 51, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, +39)

- [security regression] Provenance: unverified → fail
- [security regression] Malware scan: pass → unverified
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] License: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: MIT

### 2026-07-29 (score 19, −28)

- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional improvement] Dependency health: unverified → partial

### 2026-07-27 (score 47)

First indexed and scored.

## MCP tools (18)

### `caddy_config_get` (~70 tokens)

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').

Input parameters:

- `path` (string): Config path (e.g., 'apps/http/servers/srv0')

### `caddy_config_set` (~172 tokens)

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.

Input parameters:

- `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, required): Config path to write to (e.g., 'apps/http/servers/srv0/routes')
- `value` (required): The JSON value to set at the path

### `caddy_config_delete` (~107 tokens)

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.

Input parameters:

- `confirm` (boolean): Must be true to actually delete the config node (safety)
- `path` (string, required): Config path to delete (e.g., 'apps/http/servers/srv0/routes/0')

### `caddy_load` (~98 tokens)

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.

Input parameters:

- `config` (required): Full config — JSON object or Caddyfile text string
- `format` (string): Config format: 'json' (default) or 'caddyfile'

### `caddy_revert` (~113 tokens)

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).

Input parameters:

- `action` (string, required): Action to perform
- `confirm` (boolean): Must be true to actually apply a snapshot (safety)
- `index` (integer): Snapshot index for 'apply' (0 = most recent, default)

### `caddy_config_by_id` (~189 tokens)

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.

Input parameters:

- `action` (string): Action to perform
- `confirm` (boolean): Must be true to actually delete (only enforced for action='delete')
- `id` (string, required): 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)

### `caddy_reverse_proxy` (~367 tokens)

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.

Input parameters:

- `from` (string, required): 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, required): Upstream addresses (e.g., ['localhost:3000', 'localhost:3001'])

### `caddy_add_route` (~134 tokens)

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.).

Input parameters:

- `handle` (array, required): Array of handler objects (e.g., [{ handler: 'file_server', root: '/var/www' }])
- `match` (array, required): 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

### `caddy_list_routes` (~46 tokens)

List all routes on a Caddy HTTP server with a human-readable summary of matchers and handlers.

Input parameters:

- `server` (string): Caddy server name (default: srv0)

### `caddy_remove_route` (~154 tokens)

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.

Input parameters:

- `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.

### `caddy_adapt` (~176 tokens)

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.

Input parameters:

- `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, required): The raw config text (e.g., Caddyfile contents, nginx.conf, yaml)

### `caddy_tls` (~108 tokens)

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.

Input parameters:

- `action` (string, required): Action to perform
- `ca` (string): ACME CA URL (for 'set_acme_ca' action)
- `email` (string): ACME email address (for 'set_email' action)

### `caddy_status` (~30 tokens)

Check Caddy connectivity and get a config summary: servers, routes, listen addresses, and TLS status.

### `caddy_list_servers` (~40 tokens)

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.

### `caddy_upstreams` (~32 tokens)

Get the current health status of all reverse proxy upstreams. Shows address, active requests, and failure counts.

### `caddy_pki` (~52 tokens)

Get PKI certificate authority info or the CA certificate chain.

Input parameters:

- `ca` (string): CA ID (default: 'local')
- `certificates` (boolean): If true, return the full CA certificate chain

### `caddy_metrics` (~223 tokens)

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.

Input parameters:

- `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.

### `caddy_stop` (~39 tokens)

Gracefully shut down the Caddy server. Requires confirm=true to prevent accidental shutdown.

Input parameters:

- `confirm` (boolean, required): Must be true to confirm shutdown

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/yawlabs-caddy-mcp/yawlabs-caddy-mcp#diagnostics

## Score history

- 2026-08-04: 66
- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 40
- 2026-07-31: 51
- 2026-07-30: 58
- 2026-07-29: 19
- 2026-07-28: 47
- 2026-07-27: 47

## Links

- npm package: https://www.npmjs.com/package/@yawlabs/caddy-mcp
- Socket report: https://socket.dev/npm/package/@yawlabs/caddy-mcp
- Changelog RSS feed: https://verifymcp.io/servers/yawlabs-caddy-mcp/yawlabs-caddy-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/yawlabs-caddy-mcp/yawlabs-caddy-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/yawlabs-caddy-mcp/yawlabs-caddy-mcp