# Epeaky host (npm · epeaky-host-mcp)

Set up and run an Epeaky den on a server you already have, over your own SSH.

- Trust score: 70/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `epeaky-host-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/zyn-io-epeaky-host-mcp/epeaky-host-mcp.md), [page](https://verifymcp.io/servers/zyn-io-epeaky-host-mcp/epeaky-host-mcp)

## Channel facts

- Registry: `npm`
- Package: `epeaky-host-mcp`
- Version: `0.1.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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT OR Apache-2.0).
  - Actively maintained (last published 18 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1295 tokens (~117/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Epeaky host MCP server?

Epeaky host runs locally as an npm package, launched with npx -y epeaky-host-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add zyn-io-epeaky-host-mcp -- npx -y epeaky-host-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "zyn-io-epeaky-host-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "epeaky-host-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "zyn-io-epeaky-host-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "epeaky-host-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add zyn-io-epeaky-host-mcp -- npx -y epeaky-host-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zyn-io-epeaky-host-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "epeaky-host-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zyn-io-epeaky-host-mcp --command npx --arg -y --arg epeaky-host-mcp
```

### Hermes

```yaml
mcp_servers:
  zyn-io-epeaky-host-mcp:
    command: "npx"
    args: ["-y", "epeaky-host-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "zyn-io-epeaky-host-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "epeaky-host-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add zyn-io-epeaky-host-mcp -t stdio -c npx -a -y epeaky-host-mcp
```

### Other

```json
{
  "mcpServers": {
    "zyn-io-epeaky-host-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "epeaky-host-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-10-18 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-17 (score 55)

First indexed and scored.

## MCP tools (11)

### `host_check` (~144 tokens)

Check a server and a domain for an Epeaky den, changing nothing. Ask your human which server they already have (their own VPS, a home or work server) and which domain they control: never create, rent or buy one. Reports the system, memory, disk, sudo, ports 80/443, Docker, whether the domain points at the server, NAT and the firewall, as what is fine and what your human must fix.

Input parameters:

- `domain` (string, required): The domain for the den, e.g. chat.example.org.
- `server` (string, required): The server as user@host (its address or name), reachable with your human's SSH key.

### `host_install` (~179 tokens)

Install Epeaky on the server: Docker if it is missing (with Docker's own script), the den and Caddy in /opt/epeaky, a certificate for the domain, and TCP 80/443 and UDP 50000-50199 opened in ufw or firewalld. Run host_check first. Returns the first invite link: show it only to your human, who opens it on their own device. This changes the server: Ask your human first, and tell them what it does. Offer the installer to read first: https://epeaky.zyn-network.com/install.sh

Input parameters:

- `domain` (string, required)
- `email` (string): For the certificate's expiry notices (optional).
- `server` (string, required): The server as user@host (its address or name), reachable with your human's SSH key.

### `host_status` (~58 tokens)

The den on the server: its owner, how many members, people asking to join, and invites. Changes nothing.

Input parameters:

- `server` (string, required): The server as user@host (its address or name), reachable with your human's SSH key.

### `host_logs` (~56 tokens)

The den's last log lines, for when something fails. Changes nothing.

Input parameters:

- `lines` (integer)
- `server` (string, required): The server as user@host (its address or name), reachable with your human's SSH key.

### `host_owner` (~112 tokens)

Make a device the den's owner: the one with every power and Den settings. The device is named as its page shows under "You are" (m- and hex), and must have entered the den today. This changes the server: Ask your human first, and tell them what it does.

Input parameters:

- `device` (string, required): m- and 6 to 64 hex characters.
- `server` (string, required): The server as user@host (its address or name), reachable with your human's SSH key.

### `host_invite` (~96 tokens)

Make one-use invite links. Show them only to your human: whoever opens one first is in. This changes the server: Ask your human first, and tell them what it does.

Input parameters:

- `count` (integer)
- `days` (integer): How long they are good for (default 7).
- `server` (string, required): The server as user@host (its address or name), reachable with your human's SSH key.

### `host_withdraw` (~86 tokens)

Withdraw an invite, and the pass it let in. This changes the server: Ask your human first, and tell them what it does.

Input parameters:

- `id` (string, required): The id as epeaky requests / epeaky invites lists it (hex).
- `server` (string, required): The server as user@host (its address or name), reachable with your human's SSH key.

### `host_approve` (~88 tokens)

Let a request to join in (see host_status for requests). This changes the server: Ask your human first, and tell them what it does.

Input parameters:

- `id` (string, required): The id as epeaky requests / epeaky invites lists it (hex).
- `server` (string, required): The server as user@host (its address or name), reachable with your human's SSH key.

### `host_decline` (~82 tokens)

Turn a request to join down. This changes the server: Ask your human first, and tell them what it does.

Input parameters:

- `id` (string, required): The id as epeaky requests / epeaky invites lists it (hex).
- `server` (string, required): The server as user@host (its address or name), reachable with your human's SSH key.

### `host_setting` (~255 tokens)

Change one of the den's settings in /opt/epeaky/.env (a backup first), then restart it. An empty value removes the setting. Only these: DEN_ENTRY (invite, approval or external, comma-separated); DEN_ROOMS (id:Title pairs, comma-separated (ids: a-z, 0-9, -)); DEN_DONATE (an https:// address); DEN_DONATE_LABEL (1 to 40 characters); DEN_ISSUER_LABEL (1 to 40 characters); DEN_SCREEN (on or off); DEN_SCREEN_BITRATE (bits a second, 300000 to 8000000); DEN_RETENTION_DAYS (days, 1 to 3650); DEN_LIMITS (name=number pairs (message_bytes, file_max, file_bytes, files, room_members, invites, inbox, history_bytes, min_free_bytes)); DEN_PUBLIC_IP (an IPv4 or IPv6 address). This changes the server: Ask your human first, and tell them what it does.

Input parameters:

- `name` (string, required)
- `server` (string, required): The server as user@host (its address or name), reachable with your human's SSH key.
- `value` (string, required)

### `host_update` (~67 tokens)

Pull the latest Epeaky and restart the den. Members reconnect by themselves. This changes the server: Ask your human first, and tell them what it does.

Input parameters:

- `server` (string, required): The server as user@host (its address or name), reachable with your human's SSH key.

## Diagnostics

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

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 70
- 2026-10-26: 70
- 2026-10-25: 70
- 2026-10-24: 70
- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 55

## Common questions

### What is the Epeaky host MCP server?

Epeaky host is an MCP server listed in the public MCP registry as io.github.zyn-io/epeaky-host-mcp. Set up and run an Epeaky den on a server you already have, over your own SSH. This page covers its npm package (epeaky-host-mcp).

### Is the Epeaky host MCP server safe to use?

Epeaky host scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Epeaky host MCP server expose?

Epeaky host exposes 11 tools: host_check, host_install, host_status, host_logs, host_owner, and 6 more. Their descriptions and schemas cost roughly 1,223 tokens of context every time the server is loaded.

### Is the Epeaky host MCP server still maintained?

Epeaky host is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Epeaky host MCP server under?

Epeaky host declares the MIT OR Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/epeaky-host-mcp
- Socket report: https://socket.dev/npm/package/epeaky-host-mcp
- Repository: https://github.com/zyn-io/epeaky
- Website: https://epeaky.zyn-network.com/
- Changelog RSS feed: https://verifymcp.io/servers/zyn-io-epeaky-host-mcp/epeaky-host-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/zyn-io-epeaky-host-mcp/epeaky-host-mcp.json
- HTML version of this page: https://verifymcp.io/servers/zyn-io-epeaky-host-mcp/epeaky-host-mcp