mcp-zoomSAFE
Zoom MCP Pack
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Zoom MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.
Tools
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"zoom": {
"url": "https://gateway.pipeworx.io/zoom/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/zoom/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for
0670a75aa139OBSERVED · 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.
claude mcp add mcp-zoom -- npx -y @pipeworx/[email protected]
{
"mcpServers": {
"mcp-zoom": {
"command": "npx",
"args": [
"-y",
"@pipeworx/[email protected]"
]
}
}
}Exposed tools (4)
4 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
zoom_get_meeting | read | Get the full details of a single Zoom meeting by its meeting ID, including topic, start time, duration, timezone, agenda, join URL, status, and key video/security settings (host video, participant video, waiting room). Use after zoom_list_meetings to inspect a specific video call. |
zoom_get_user | read | Get the signed-in Zoom user\ |
zoom_list_meetings | read | List Zoom meetings for the signed-in user (upcoming, scheduled, or currently live video calls). Returns compact meeting summaries (id, topic, start time, duration, join URL, timezone). Use to browse a user\ |
zoom_list_recordings | read | List the signed-in user\ |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (1)
@modelcontextprotocol/sdk, tsx, typescript, @cloudflare/workers-types
Gates applied: no_behavioural_pass.
0670a75aa139full audit observations/trust-audit/mcp-server/pipeworx-io__mcp-zoom.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 | 0670a75aa139 | SAFE | B | 89 | first audit |
Questions
What is the mcp-zoom MCP server?
Zoom MCP Pack
What tools does mcp-zoom expose?
4 in total: 4 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is mcp-zoom safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does mcp-zoom need?
No credential environment variables were found in its source, so it appears to need none.
How does mcp-zoom run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as @pipeworx/mcp-zoom at 0.1.3.
How current is this page?
The grade is for one exact copy of the source (0670a75aa139), read on 2026-10-11. The repository is watched and re-audited when it changes.