Zoom
NPM · @PIPEWORX/MCP-ZOOM · 2 COMPONENTS
Zoom MCP Pack
Available components
Last scanned (6 hours ago)
Scores higher than 87% of npm servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-zoom). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 438 tokens (~109/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +2
- Stability: unverified → 0.13 ▲ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 82
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-zoom@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-zoom |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-zoom/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3561243451 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1730145b2e9dae48641006c070e5c64ae1891c9b5d5d19014d4ad00e3ac0c1291b37e2b77113a5fc1421aef81c0cb3b2845536fcb85e4fed510b66b1c |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
zoom_get_meeting ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| meeting_id | string | yes | The ID of the Zoom meeting to retrieve (from zoom_list_meetings). |
No output schema declared.
No examples provided.
zoom_get_user ~51
Get the signed-in Zoom user's profile: id, email, first/last name, account type, account id, timezone, and personal meeting id (PMI). Use to identify whose Zoom account is connected.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zoom_list_meetings ~113
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's Zoom meetings.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | number | – | Maximum number of meetings to return (default 30, max 100). |
| type | string | – | Which set of Zoom meetings to list: "scheduled", "live" (currently in progress), or "upcoming" (default). |
No output schema declared.
No examples provided.
zoom_list_recordings ~130
List the signed-in user's Zoom cloud recordings of past meetings and video calls. Returns each recording's id, topic, start time, duration, total size, recording count, and downloadable/playable files (video, audio, transcript). Supports an optional date range. Use to find and access Zoom recordings.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date for the recording search, in YYYY-MM-DD format. |
| page_size | number | – | Maximum number of recordings to return (default 30, max 100). |
| to | string | – | End date for the recording search, in YYYY-MM-DD format. |
No output schema declared.
No examples provided.
How do I install the Zoom MCP server?
Zoom runs locally as an npm package, launched with npx -y @pipeworx/mcp-zoom. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-zoom
claude mcp add pipeworx-io-zoom -- npx -y @pipeworx/mcp-zoom
What is the Zoom MCP server?
Zoom is an MCP server listed in the public MCP registry as io.github.pipeworx-io/zoom. Zoom MCP Pack. This page covers its npm package (@pipeworx/mcp-zoom).
Is the Zoom MCP server safe to use?
Zoom scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Zoom MCP server expose?
Zoom exposes 4 tools: zoom_list_meetings, zoom_get_meeting, zoom_list_recordings, zoom_get_user. Their descriptions and schemas cost roughly 387 tokens of context every time the server is loaded.
Is the Zoom MCP server still maintained?
Zoom is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Zoom MCP server under?
Zoom declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.