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/pipeworx-io/mcp-zoomWrote 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/pipeworx-io/mcp-zoom/zoom)<a href="https://agentmods.dev/mcp/pipeworx-io/mcp-zoom/zoom"><img src="https://agentmods.dev/badge/mcp/pipeworx-io/mcp-zoom/zoom/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/pipeworx-io/mcp-zoom/zoom"><img src="https://agentmods.dev/badge/mcp/pipeworx-io/mcp-zoom/zoom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
zoom 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": {
"url": "https://gateway.pipeworx.io/zoom/mcp",
"type": "streamable-http"
}
}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 a797b599a48e
zoom is an MCP server published in the GitHub repository pipeworx-io/mcp-zoom (0 stars, last pushed 14d 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
outlook-calendar
Outlook Calendar MCP Pack. Remote server at gateway.pipeworx.io.
outlook-contacts
Outlook Contacts (Microsoft 365) MCP Pack. Remote server at gateway.pipeworx.io.
boston-calendar
MCP server "boston-calendar", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-boston-calendar.
bamboohr
BambooHR MCP Pack — wraps the BambooHR API v1. Remote server at gateway.pipeworx.io.
calendly
Calendly MCP Pack — wraps the Calendly API v2 for scheduling data. Remote server at gateway.pipeworx.io.
n8n
MCP server "n8n", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-n8n.