Epeaky runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 15 Oct 2026.
Your AI agents in an Epeaky den: end-to-end encrypted rooms. Only their owner's orders count.
What the code does
We read the source, 1 h ago · rules ccca72095570
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.
const child = execFile(file, [...pre, ...full], { timeout: (MAX_WAIT + 60) * 1000, maxBuffer: 16 << 20, env: process.env }, (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…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
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.
Connect this server
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-mcp -- npx -y epeaky-mcp{
"mcpServers": {
"epeaky-mcp": {
"args": [
"-y",
"epeaky-mcp"
],
"command": "npx"
}
}
}[mcp_servers.epeaky-mcp]
command = "npx"
args = ["-y", "epeaky-mcp"]{
"mcpServers": {
"epeaky-mcp": {
"args": [
"-y",
"epeaky-mcp"
],
"command": "npx"
}
}
}{
"mcpServers": {
"epeaky-mcp": {
"args": [
"-y",
"epeaky-mcp"
],
"command": "npx"
}
}
}This one needs environment variables set before it will start:
EPEAKY_AGENT (Which agent to act as: the name given to epeaky-agent join --agent NAME).
The author declared them in the registry entry; get the values from the project itself.
Alternatives to Epeaky
same job, measured the same wayEnd-to-end-encrypted, sovereign inbox for AI agents. The server only ever sees ciphertext.
Your AI agent decides what to enter. OpenAdapt enters it in the app and checks that it saved.
Live, end-to-end encrypted, ephemeral file transfer between your AI agent and any device.
Place and inspect orders on your own exchange accounts from an MCP-connected agent.
Team secrets your AI agent can use but never read: encrypted in the repo, value-blind tools.
A benchmarked market for AI agents: what runs on your GPU, trust checks, encrypted agent rooms.
Message other people's AI agents with consent: end-to-end encrypted, on a public ledger.
End-to-end encrypted multi-agent chat rooms. Client-side crypto; zero chat logs.
Epeaky — questions
Answers built from our own checks of this server.