5dive-pluginsBLOCK
Multi-harness plugin marketplace maintained by 5dive — Telegram bridge and related agent-channel integrations.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Claude Code plugin marketplace maintained by 5dive.
The telegram plugin pairs an agent CLI with a Telegram bot — DM the bot, the agent answers. The original targets Claude Code; the runtime forks below bring the same bridge to other agent CLIs that lack Claude Code's channel push protocol.
The remaining poll-based forks share one codebase shape and move in lockstep, checked by test/parity.test.ts and the generator/ (DIVE-9) — a new poll-based runtime is a config block, not a hand-fork. telegram-codex now has an app-server dispatcher in addition to its generated fallback; telegram-opencode is a deliberate exception: opencode's headless server makes a relay simpler than an MCP fork (see its README + the spike).
The other 5dive plugins
Not every 5dive plugin is a Telegram fork. These live here too, and this
daedc1ca785dOBSERVED · 2026-10-11Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add telegram-plugin --env BUZZ_PRIVATE_KEY=${BUZZ_PRIVATE_KEY} --env CONNECTORD_TOKEN=${CONNECTORD_TOKEN} --env OPENCODE_SERVER_PASSWORD=${OPENCODE_SERVER_PASSWORD} --env TELEGRAM_BOT_TOKEN=${TELEGRAM_BOT_TOKEN} -- npx -y @5dive/telegram-plugin{
"mcpServers": {
"telegram-plugin": {
"command": "npx",
"args": [
"-y",
"@5dive/telegram-plugin"
],
"env": {
"BUZZ_PRIVATE_KEY": "${BUZZ_PRIVATE_KEY}",
"CONNECTORD_TOKEN": "${CONNECTORD_TOKEN}",
"OPENCODE_SERVER_PASSWORD": "${OPENCODE_SERVER_PASSWORD}",
"TELEGRAM_BOT_TOKEN": "${TELEGRAM_BOT_TOKEN}"
}
}
}
}Exposed tools (34)
21 read · 12 write · 1 destructive. Blast radius: 1 tool can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
account | read | Pick auth account |
agents | read | Team |
buzz_post | write | Post a message to a Buzz channel (Nostr). This is the ONLY way outbound text reaches the relay — your transcript output does not. Omit reply_to to post straight in the channel (the default); pass an inbound message_id as reply_to only when a thread was explicitly requested. |
buzz_react | write | Add an emoji reaction to a Buzz message. |
buzz_read | read | Read recent messages from a Buzz channel. Use to recover context — Buzz exposes no in-session history, so this is the pull. Returns normalized events as JSON. |
checkpoint | write | Save session to resume later |
clear | destructive | Clear context (same session) |
context | read | Context usage + carry-over nudges |
digest | read | Daily standup digest on/off/at |
download_attachment | read | Download a file attachment from a Telegram message to the local inbox. Use when |
edit_message | write | Edit a message the bot previously sent. Useful for interim progress updates that don |
effort | read | Pick reasoning effort |
gate | read | File a 5dive human gate on a row (5dive task need). |
goal | read | Self-paced goal |
heartbeat | write | Heartbeat schedule |
help | read | Show commands |
inbox | read | Pending human gates awaiting you |
login | read | Authenticate your coding-CLI |
model | read | Pick model + effort |
org | read | Show the agent org chart |
react | write | Add an emoji reaction to a Telegram message. Telegram only accepts a fixed whitelist |
recent_messages | write | Recover recent Telegram context after a restart or a new session. Telegram\ |
reply | read | Reply in the 5dive dashboard chat. Pass chat_id from the inbound message (normally |
restart | write | New session — full restart |
resume | read | Resume the saved session |
start | write | Pair this chat |
status | read | Pairing, usage, model |
stop | write | Interrupt task |
task | write | Run a 5dive task verb (show, ls, done, deliver, reject, assign, set-body). |
tasks | read | List open tasks |
team | read | Team (alias for /agents) |
update | write | Refresh plugins, then restart |
usage | read | 5h/1w limit usage |
wait_for_message | read | Block until the user sends a Telegram message, then return it. |
Trust audit
BLOCKgrade F · trust 36/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | FAIL |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | FAIL |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (8 observation(s))
- Network
- declared (9 observation(s))
- Shell
- declared (5 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (25)
payload.ts
const { stdout } = await exec(bin, args, {const { stdout } = await exec(const DENY_BASENAME_RE = /(^\.env($|\.)|^\.claude\.json$|secret|token|credential|password|^id_(ed25519|rsa|ecdsa)|\.pem$|\.key$|\.p12$|\.pfx$|^\.netrc$|^\.pgpass$|^authorized_keys$|^known_hosts$)/i
const DENY_BASENAME_RE = /(^\.env($|\.)|^\.claude\.json$|secret|token|credential|password|^id_(ed25519|rsa|ecdsa)|\.pem$|\.key$|\.p12$|\.pfx$|^\.netrc$|^\.pgpass$|^authorized_keys$|^known_hosts$)/i
3. Read existing `.env` if present; update/add the `TELEGRAM_BOT_TOKEN=` line,
botguard.ts
CONNECT_SHELLD_URL=http://127.0.0.1:3101
const TOKEN = 'AbCdEfGhIjKlMnOpQrSt_-' // 22 chars of base64url, as the API mints
const d2 = stateDir({ token: 'ZZZZZZZZZZZZZZZZZZZZZZ', text: 'newer' })expect(sanitizeLabel('Check sk_live_abcdefghijklmnopqrstuvwxyz123')).toBe('Check')clear
const fn = new Function(
const o = await exec(FIVE, ['agent', 'rotation', 'set', 'me', '--enabled=true']).then(() => 'ok', (e: { stdout?: string }) => String(e.stdout))return new Function(`${body}; return isVoiceCaptionNoise`)()const stateFile = join(tmpdir(), `5dive-ctx-nudge-${createHash('sha1').update(sessionKey).digest('hex')}.txt`)const lockKey = createHash('sha1').update(transcriptPath).digest('hex')touch(P('id_ed25519'))expect(plan(`${P('id_ed25519')}`).attach).toEqual([])expect(labelFor('Bash', { command: 'cat ~/.ssh/id_ed25519' }, TG)).toBe('Running a command')expect(readFirstReply(stateDir({ token: '../../etc', text: 'x' }))).toBeNull()expect(safe('../../etc/passwd')).toBe('.._.._etc_passwd')expect(chatLogFile(dir, '../../etc/passwd')).toBe(join(dir, 'unknown.jsonl'))
- A relay URL to point at. For the Phase-1 spike: `http://178.104.35.140:3000`
"relay_url": "http://178.104.35.140:3000",
Gates applied: no_behavioural_pass.
daedc1ca785dfull audit observations/trust-audit/mcp-server/5dive-ai__5dive-plugins.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-11 | daedc1ca785d | BLOCK | F | 36 | first audit |
Questions
What is the 5dive-plugins MCP server?
Multi-harness plugin marketplace maintained by 5dive — Telegram bridge and related agent-channel integrations.
What tools does 5dive-plugins expose?
34 in total: 21 read-only, 12 that write, and 1 that can delete or overwrite (clear). Every one is listed on this page with its risk.
Is 5dive-plugins safe to connect to an agent?
No — not without reading the findings first. The audit graded it F (36/100) and found 6 critical or high issues in the source. Each one is listed on this page with the file and line it is on. Separately from the audit: 1 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does 5dive-plugins need?
It reads BUZZ_PRIVATE_KEY, CONNECTORD_TOKEN, OPENCODE_SERVER_PASSWORD and TELEGRAM_BOT_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does 5dive-plugins run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @5dive/telegram-plugin.
How current is this page?
The grade is for one exact copy of the source (daedc1ca785d), read on 2026-10-11. The repository is watched and re-audited when it changes.