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/zapier/zapier-mcpWrote 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/zapier/zapier-mcp/zapier-zapier)<a href="https://agentmods.dev/mcp/zapier/zapier-mcp/zapier-zapier"><img src="https://agentmods.dev/badge/mcp/zapier/zapier-mcp/zapier-zapier/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/zapier/zapier-mcp/zapier-zapier"><img src="https://agentmods.dev/badge/mcp/zapier/zapier-mcp/zapier-zapier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
zapier 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 12d 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
{
"zapier": {
"type": "http",
"url": "https://mcp.zapier.com/api/v1/connect"
}
}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.
- 12d ago First seen · 6 lines scan A 4e5a3fc94317
zapier is an MCP server published in the GitHub repository zapier/zapier-mcp (406 stars, last pushed 1mo 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-30.
Other mcp servers, from other repositories
wavedash
MCP server "wavedash", hosted remotely at mcp.wavedash.com, as configured in wvdsh/ai.
guarded-notes-mcp
MCP server "guarded-notes-mcp" as configured in nextgencods/guarded-notes-mcp. Runs ./server.mjs with node.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
yonsei-bridge
MCP server "yonsei-bridge" as configured in mrcha033/yonsei-skills. Runs ./runtime/yonsei_bridge/mcp_server.py with python3.
atlassian
MCP server "atlassian", hosted remotely at mcp.atlassian.com, as configured in alphaaiservice/cortex.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.