Epeaky host runs on your own machine — the client starts it, so there is no endpoint to ping. 471 installs a week from npm. Last commit 20 Oct 2026.
Set up and run an Epeaky den on a server you already have, over your own SSH.
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
execFile(SSH, sshArgs(c.server, c.root ? asRoot(c.remote) : c.remote), { timeout: c.timeout * 1000, maxBuffer: 8 << 20 }, (err, stdout, stderr) => {
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
with {out, 0} <- System.cmd("df", ["-Pk", dir], stderr_to_stdout: true),
${may('timeout') ? `<form class="set-form inline" id="to-form"><label class="field">Timeout<select name="s">${TIMEOUTS.map(([v, t]) => `<option value="${v}">${t}</option>`).join('')}</select></label><label class="field grow">Reason<input name="reason" maxlength="300" placeh…
RUN curl -sSf https://sh.rustup.rs | sh -s -- -y --profile minimal --default-toolchain 1.93.1 --target wasm32-unknown-unknown
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add epeaky-host-mcp -- npx -y epeaky-host-mcp
{
"mcpServers": {
"epeaky-host-mcp": {
"command": "npx",
"args": [
"-y",
"epeaky-host-mcp"
]
}
}
}
[mcp_servers.epeaky-host-mcp]
command = "npx"
args = ["-y", "epeaky-host-mcp"]
{
"mcpServers": {
"epeaky-host-mcp": {
"command": "npx",
"args": [
"-y",
"epeaky-host-mcp"
]
}
}
}
{
"servers": {
"epeaky-host-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"epeaky-host-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
EPEAKY_HOST_SSH (Another ssh to use (default: ssh on PATH)).
An AI agent reads your server over the one SSH session you are already watching.
Deploy and run your projects on Pethost, your own hosting.
Build your own tools from chat: design, test and host them on a shareable MCP server URL.
Your AI agent deploys, migrates & upgrades self-hosted Odoo ERP on a server you own.
Run commands and read/write files on your servers over Termalin's keyless tunnels (hosted MCP).
Deploy and manage your apps on Qovery
Deploy an app onto a server in your own cloud account.
Markdown-based note-taking with a hosted MCP server. Your notes serve you and your AI.
Answers built from our own checks of this server.