Zulip MCP Server
zulip-mcp-server
npm
v2.2.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Stateful, ergonomic MCP server for Zulip and Discord with ambient awareness, persistent monitoring, and natural date-based queries
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([start_monitoring, get_unread_messages, discord_start_monitoring, discord_get_unread_messages, Zulip - Unread Messages Summary, Discord - Unread Messages Summary]) co-exist with external-action tools ([send_message, discord_send_message]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [start_monitoring, get_unread_messages, discord_start_monitoring, discord_get_unread_messages, Zulip - Unread Messages Summary, Discord - Unread Messa
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow start_monitoring → send_message
Tools 26
Each tool and what it can reach — statically extracted from the published source.
Discord - Unread Messages Summaryingests untrusted inputdiscord_get_unread_messagesingests untrusted inputdiscord_send_messagenetwork egressdiscord_start_monitoringingests untrusted inputget_unread_messagesingests untrusted inputsend_messagenetwork egressstart_monitoringingests untrusted inputZulip - Unread Messages Summaryingests untrusted inputadd_reactionno sensitive capabilitydelete_messageno sensitive capability
Show 16 more tools ↓
Discord - Monitoring Statusno sensitive capabilitydiscord_delete_messageno sensitive capabilitydiscord_find_userno sensitive capabilitydiscord_get_channel_historyno sensitive capabilitydiscord_get_monitored_channelsno sensitive capabilitydiscord_list_channelsno sensitive capabilitydiscord_stop_monitoringno sensitive capabilityfind_userno sensitive capabilityget_channel_historyno sensitive capabilityget_monitored_channelsno sensitive capabilityget_stream_topicsno sensitive capabilityget_user_profileno sensitive capabilitylist_streamsno sensitive capabilitylist_usersno sensitive capabilitystop_monitoringno sensitive capabilityZulip - Monitoring Statusno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (26 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.2.0 latest |
A 95/100 | 1 | 1.13.0 | 2026-09-09 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan zulip-mcp-server --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.