Is the Zoom Meetings MCP Server safe?

anlyon.dev has not been able to list its tools, so it has no classes or findings for it yet. It asks for sign-in before listing them. Paste its tools/list output into https://anlyon.dev/scan to check it yourself.

Who publishes the Zoom Meetings MCP Server?

zoom (GitHub account verified by the MCP Registry).

Zoom Meetings MCP Server

io.github.zoom/zoom-meetingszoomremotev1.0.1

Zoom Meetings server for creating, searching, and managing meetings, recordings, and assets.

No tools shown: it asks for sign-in first

This server lists its tools only to a signed-in client (OAuth). anlyon.dev never signs in or sends credentials, so it cannot read them, and nothing here is a judgement of the server. Already use it? Copy its tools/list from your client and check it here: the same labels, worked out in your browser.

Sign-in required, OAuth metadata published. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

anlyon.dev does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the Zoom Meetings MCP Server can do

The Zoom Meetings MCP Server is published by the GitHub account zoom. It asks for sign-in (OAuth) before it lists its tools, and anlyon.dev never signs in, so its tools are not shown.

Scan status: sign-in required

Scopes it asks for: cloud_recording:read:content, cloud_recording:read:list_user_recordings, meeting:delete:meeting, meeting:read:assets, meeting:read:search, meeting:update:in_meeting_controls, meeting:update:meeting, meeting:write:meeting

Last attempt Nov 13, 2026, 03:18 UTC.

Have its tools/list output? Check it yourself.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 13, 2026, 12:24 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable: yes
HTTP status of an anonymous initialize: 401
tools/list served without credentials: no
Tools that change things, listed without credentials: 0
Protocol version: not observed
WWW-Authenticate on 401: yes
resource_metadata in WWW-Authenticate: https://zoom.us/.well-known/oauth-protected-resource/mcp/meeting/streamable
RFC 9728 protected resource metadata: https://zoom.us/.well-known/oauth-protected-resource/mcp/meeting/streamable
Authorization servers: https://zoom.us
Legacy HTTP+SSE transport: no
Dynamic client registration: no
Client ID metadata documents: no

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http zoom-meetings https://mcp.zoom.us/mcp/meeting/streamable

claude mcp add --transport http zoom-meetings https://mcp.zoom.us/mcp/meeting/streamable

Run in a terminal.

Badge

A badge for your README that links back to this page.

Badge

[![anlyon.dev](https://anlyon.dev/badge/io.github.zoom/zoom-meetings.svg)](https://anlyon.dev/servers/io.github.zoom/zoom-meetings)

Source: MCP Registry · repository. Synced Nov 13, 2026, 03:18 UTC.