Epeaky host
NPM · EPEAKY-HOST-MCP
Set up and run an Epeaky den on a server you already have, over your own SSH.
Available components
Last scanned (19 hours ago)
Scores higher than 39% of npm servers
Category Cloud Infrastructure
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT OR Apache-2.0).Pass
- Actively maintained (last published 17 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 55
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 Nov 2026 · Analysed npm/epeaky-host-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
host_approve ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id as epeaky requests / epeaky invites lists it (hex). |
| server | string | yes | The server as user@host (its address or name), reachable with your human's SSH key. |
No output schema declared.
No examples provided.
host_check ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain for the den, e.g. chat.example.org. |
| server | string | yes | The server as user@host (its address or name), reachable with your human's SSH key. |
No output schema declared.
No examples provided.
host_decline ~82
Turn a request to join down. This changes the server: Ask your human first, and tell them what it does.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id as epeaky requests / epeaky invites lists it (hex). |
| server | string | yes | The server as user@host (its address or name), reachable with your human's SSH key. |
No output schema declared.
No examples provided.
host_install ~179
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
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| string | – | For the certificate's expiry notices (optional). | |
| server | string | yes | The server as user@host (its address or name), reachable with your human's SSH key. |
No output schema declared.
No examples provided.
host_invite ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| days | integer | – | How long they are good for (default 7). |
| server | string | yes | The server as user@host (its address or name), reachable with your human's SSH key. |
No output schema declared.
No examples provided.
host_logs ~56
The den's last log lines, for when something fails. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| lines | integer | – | – |
| server | string | yes | The server as user@host (its address or name), reachable with your human's SSH key. |
No output schema declared.
No examples provided.
host_owner ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | m- and 6 to 64 hex characters. |
| server | string | yes | The server as user@host (its address or name), reachable with your human's SSH key. |
No output schema declared.
No examples provided.
host_setting ~255
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| server | string | yes | The server as user@host (its address or name), reachable with your human's SSH key. |
| value | string | yes | – |
No output schema declared.
No examples provided.
host_status ~58
The den on the server: its owner, how many members, people asking to join, and invites. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | The server as user@host (its address or name), reachable with your human's SSH key. |
No output schema declared.
No examples provided.
host_update ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | The server as user@host (its address or name), reachable with your human's SSH key. |
No output schema declared.
No examples provided.
host_withdraw ~86
Withdraw an invite, and the pass it let in. This changes the server: Ask your human first, and tell them what it does.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id as epeaky requests / epeaky invites lists it (hex). |
| server | string | yes | The server as user@host (its address or name), reachable with your human's SSH key. |
No output schema declared.
No examples provided.
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.
npm · epeaky-host-mcp
claude mcp add zyn-io-epeaky-host-mcp -- npx -y epeaky-host-mcp
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 4 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 4 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.