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/krystiangw/zen-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/krystiangw/zen-mcp/zen)<a href="https://agentmods.dev/mcp/krystiangw/zen-mcp/zen"><img src="https://agentmods.dev/badge/mcp/krystiangw/zen-mcp/zen.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
zen 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 7d 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
{
"zen": {
"command": "npx",
"args": [
"-y",
"@krystiangw/zen-mcp"
],
"env": {
"ZEN_API_KEY": "",
"ZEN_PAYWALL_SECRET": "",
"ZEN_IPN_SECRET": "",
"ZEN_ENV": ""
}
}
}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.
- 7d ago First seen · 15 lines scan A 48c8a0acd02f
zen is an MCP server published in the GitHub repository krystiangw/zen-mcp (0 stars, last pushed 21d 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
payhere-mcp
Model Context Protocol server for PayHere — Sri Lanka's payment gateway. Lets developers retrieve payments, issue refunds, generate checkout payloads, and compute PayHere signatures from any MCP-aware client (Claude Code, etc). Runs locally from the @lk-pay/payhere-mcp npm package.
unified-pay-cli
Unified Payment Gateway CLI & MCP Bridge for Stripe, Razorpay and more. Runs locally from the unified-pay-cli npm package.
stripe-mcp-server
MCP server for Stripe API — customers, charges, payments, subscriptions, products, and invoices. Runs locally from the stripe-mcp-server npm package.
mcp-rinne
Brazilian card acquiring API — merchants, cards-on-file, 3DS, PIX, banking, pricing. Runs locally from the @codespar/mcp-rinne npm package. Needs 5 environment variables to run.
mcp-adyen
MCP server for Adyen Checkout API v71 — enterprise payments (iFood, Uber, Spotify in LatAm). Runs locally from the @codespar/mcp-adyen npm package. Needs 4 environment variables to run.
mcp-banco-do-brasil
MCP server for Banco do Brasil — Pix, Cobrança (boleto), Conta-Corrente, Arrecadação (OAuth2 + mTLS). Runs locally from the @codespar/mcp-banco-do-brasil npm package. Needs 6 environment variables to run.