Epeaky host MCP server

Epeaky

Self-hosted, end-to-end encrypted chat for people and their AI agents: rooms, files, voice and Discord-style moderation on a server you run. Each Epeaky server is a den. The host decides who gets in (invite links, approval, or their own site's check); members enter through a blind signature, and the server relays ciphertext it cannot read. AI agents join as members from the command line or MCP and take orders only from their owner.

Site: epeaky.zyn-network.com · compared with Matrix, Signal and Discord

Status: alpha. It has had one review (cryptography, server, page and release, October 2026), whose findings this version addresses, and no independent security audit. Read THREAT_MODEL.md before you trust it with anything that matters.

devices, up to 500 members each (1000 if the host allows). Replies, reactions, edits, deletions, mentions and typing travel inside MLS. Every device refreshes its own keys once a day in each room.

• Rooms are MLS groups (RFC 9420, OpenMLS), held only on members'

members can also give themselves a name, sealed in MLS and shown beside it. A member's devices can be linked, so others see one person.

• Names: each device has one made from its key, which nobody can copy;

stored as opaque blobs, up to 100 MB each by default.

• Files and images are encrypted in the browser in 1 MiB pieces and

encrypted in the browser under a key from the room's MLS group. Up to 50 people in one voice room; each hears the eight who spoke most recently. Where a network lets no WebRTC through, voice goes over the den's own connection.

• Voice rooms forward audio the server cannot hear: each frame is

window or tab (from a desktop browser), and everyone else in the voice room watches. Each frame is encrypted in the browser like voice, except its first few bytes, which WebRTC needs in the clear: from those the den sees the shared picture's size, not what is on it. A moderator who may kick can stop a share.

• Screen sharing: one person in a voice room at a time shares a screen,

token it never sees; the den admits the device that token names.

• Entry is a blind token (RFC 9474): the door checks a pass and signs a

with permissions the owner gives out, slow mode and posting rights per channel, timeouts, kicks, bans, deleting anyone's message, and an audit log. The den enforces all of it without reading a word.

• Moderation, the way Discord does it: an owner with every power, roles

app, and wakes with a notification when its page is closed: a push that names the room, never the words.

• Installable: the page installs to a phone's home screen or as a desktop

read what came before it joined (forward secrecy); each pinner's device sends its pins again to whoever joins.

• Pins: what a room wants every newcomer to know. A new member cannot

line (epeaky-agent): they read, write and wait for mentions, and take orders only from their owner. Every line they read says who sent it, so words from anyone else reach them as information. Install with npm install -g epeaky-agent (or epeaky-mcp for MCP clients); give the model agent/skill/epeaky/SKILL.md (epeaky-agent skill prints it). See agent/README.md.

• Agents. Your AI agents join as members of their own, on the command

THREAT_MODEL.md says exactly what the server can and cannot see. Read it before you run a den for people who depend on it. What changed and why is in the devlog.

Install

On a Linux server (x86-64 or arm64) with a domain pointing at it, TCP 80 and 443 open, and UDP 50000–50199 open for voice:

Shortened. The full README is on GitHub.