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/metravod/zymi-coreWrote 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/metravod/zymi-core/zymi-release)<a href="https://agentmods.dev/mcp/metravod/zymi-core/zymi-release"><img src="https://agentmods.dev/badge/mcp/metravod/zymi-core/zymi-release/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/metravod/zymi-core/zymi-release"><img src="https://agentmods.dev/badge/mcp/metravod/zymi-core/zymi-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
zymi-release 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
{
"zymi-release": {
"command": "../target/debug/zymi",
"args": [
"mcp",
"serve",
"--dir",
".",
"--expose-observability"
]
}
}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 · 12 lines scan A 15c0a281df42
zymi-release is an MCP server published in the GitHub repository metravod/zymi-core (9 stars, last pushed yesterday), 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
stripe
Stripe's hosted MCP server: lets the agent work with customers, products, prices and payment links. Remote server at mcp.stripe.com.
django-stateless-mcp-example
MCP server "django-stateless-mcp-example", hosted remotely at 127.0.0.1, as configured in Streamlined-Analytics/django-stateless-mcp.
swiss-academic-libraries-mcp
MCP Server für Schweizer Wissenschaftsbibliotheken: swisscovery (SRU), e-rara/e-periodica/e-manuscripta (OAI-PMH) und Open-Access-Rechtsliteratur (sui generis, ex/ante, Repositorium.ch). Kein API-Key erforderlich. Runs locally from the swiss-academic-libraries-mcp Python package.
swiss-cultural-heritage
MCP server "swiss-cultural-heritage" as configured in malkreide/swiss-cultural-heritage-mcp. Runs swiss_cultural_heritage_mcp.server with python.
nexus-browser-mcp
A local browser-control MCP server built with Playwright and an accessibility tree. Playwright is software for controlling web browsers, while an accessibility tree describes page elements in a way automation tools can inspect.
lobbywatch
MCP server for the Lobbywatch.ch lobby database — conflicts of interest of Swiss parliamentarians. Runs locally from the lobbywatch-mcp Python package. Needs 1 environment variable to run.