Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/zoom/mcp-registryWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/zoom/mcp-registry/zoom-whiteboard)<a href="https://agentmods.dev/mcp/zoom/mcp-registry/zoom-whiteboard"><img src="https://agentmods.dev/badge/mcp/zoom/mcp-registry/zoom-whiteboard/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/zoom/mcp-registry/zoom-whiteboard"><img src="https://agentmods.dev/badge/mcp/zoom/mcp-registry/zoom-whiteboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
zoom-whiteboard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"zoom-whiteboard": {
"url": "https://mcp.zoom.us/mcp/whiteboard/streamable",
"type": "streamable-http"
}
}What else server.json configures
This page is one entry in a file that holds 7. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 6 lines scan A db5562d298c3
zoom-whiteboard is an MCP server published in the GitHub repository zoom/mcp-registry (3 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
drawio
MCP server for Next AI Draw.io - AI-powered diagram generation with real-time browser preview. Runs locally from the @next-ai-drawio/mcp-server npm package.
best-cad-mcp
MCP server "best-cad-mcp" as configured in LokmenoWer/best-cad-mcp. Runs ${CLAUDE_PROJECT_DIR:-.}/src/server.py with python. Needs 3 environment variables to run.
sse-email-mcp-server
A local MCP email server that can send and receive mail through SMTP, IMAP, or POP3. It supports common providers such as Gmail and Outlook, attachments, HTML or plain text, and changing authentication details.
slack-mcp-server
A Model Context Protocol (MCP) server for Slack workspace integration using FastMCP with robust authentication and caching. Runs locally from the slack-mcp-server Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.