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.
npx agentmods add mcp/zooza-dev/zooza-mcp-server/mcp-servergit clone --depth 1 https://github.com/zooza-dev/zooza-mcp-serverWrote 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/zooza-dev/zooza-mcp-server/mcp-server)<a href="https://agentmods.dev/mcp/zooza-dev/zooza-mcp-server/mcp-server"><img src="https://agentmods.dev/badge/mcp/zooza-dev/zooza-mcp-server/mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-server 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mcp-server — 88% identical, 2 lines differ
What it actually says
{ "mcp-server": { "url": "https://mcp.zooza.app/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.
- 6d ago First seen · 6 lines scan A 166a50d8f433
mcp-server is an MCP server published in the GitHub repository zooza-dev/zooza-mcp-server (6 stars, last pushed 6d 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
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.0). Needs 6 environment variables to run.
itglue-mcp
MCP server "itglue-mcp" as configured in WYRE-AI/itglue-mcp. Runs in Docker (ghcr.io/wyre-ai/itglue-mcp:v1.16.5). Needs 6 environment variables to run.
apibase
327 tools, 92 providers. Pay per call via x402 + MPP. One MCP endpoint. Runs locally from the apibase-mcp-client npm package.
gsc
MCP server for Google Search Console & Indexing API — search analytics, sitemaps, URL inspection. Runs locally from the @mikusnuz/gsc-mcp npm package. Needs 4 environment variables to run.
umami
MCP server for Umami Analytics API v2 — websites, stats, events, reports, and realtime. Runs locally from the @mikusnuz/umami-mcp npm package. Needs 4 environment variables to run.
local-delegate
Delegate mechanical text tasks to a local OpenAI-compatible LLM endpoint to conserve Claude subscription quota. Runs locally from the local-delegate-mcp Python package. Needs 2 environment variables to run.