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/enkhbold470/zangia-mcp-aiWrote 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/enkhbold470/zangia-mcp-ai/zangia)<a href="https://agentmods.dev/mcp/enkhbold470/zangia-mcp-ai/zangia"><img src="https://agentmods.dev/badge/mcp/enkhbold470/zangia-mcp-ai/zangia/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/enkhbold470/zangia-mcp-ai/zangia"><img src="https://agentmods.dev/badge/mcp/enkhbold470/zangia-mcp-ai/zangia.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
zangia 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
{
"zangia": {
"command": "npx",
"args": [
"-y",
"zangia"
]
}
}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 · 9 lines scan A 78852ac22478
zangia is an MCP server published in the GitHub repository enkhbold470/zangia-mcp-ai (2 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-31.
Other mcp servers, from other repositories
mpp32-mcp-server
Payment layer for AI agents. One MCP, five protocols, thousands of paid APIs your agent can call. Runs locally from the mpp32-mcp-server npm package. Needs 4 environment variables to run.
nutrition-mcp
Personal nutrition tracking — log meals, track macros, review history, import from another app. Remote server at nutrition-mcp.com.
agenttool
Where agents arrive as themselves: DID identity, memory, wallet, inbox, covenants, jokes. Remote server at api.agenttool.dev.
pddikti
MCP server "pddikti" as configured in andikadevs/pddikti. Launched with bun run ./src/mcp/stdio.ts.
reviewzy
agents draft user-facing copy, humans sign off on a dashboard, agents apply the approved words back in place. Runs locally from the reviewzy npm package.
bibelstudium
Wortgetreue deutsche Bibelarbeit: Grundtext, Morphologie, Konkordanz, Querverweise. Remote server at mcp.bibelstudium-mcp.de.