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/nonameuserd/paybond-kit/paybondgit clone --depth 1 https://github.com/nonameuserd/paybond-kitWrote 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/nonameuserd/paybond-kit/paybond)<a href="https://agentmods.dev/mcp/nonameuserd/paybond-kit/paybond"><img src="https://agentmods.dev/badge/mcp/nonameuserd/paybond-kit/paybond.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
paybond 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 4d 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:
- paybond — 100% identical, 0 lines differ
What it actually says
{
"paybond": {
"command": "npx",
"args": [
"-y",
"@paybond/kit"
],
"env": {
"PAYBOND_API_KEY": "",
"PAYBOND_GATEWAY_URL": "https://api.paybond.ai",
"PAYBOND_ENV_FILE": ".env.local"
}
}
}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.
- 4d ago First seen · 14 lines scan A 513cb4bd1ecb
paybond is an MCP server published in the GitHub repository nonameuserd/paybond-kit (1 stars, last pushed 1mo ago), licensed Apache-2.0. 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
paybond
Paybond Kit for TypeScript: agent spend governance for paid tool calls with spend authorization, evidence receipts, refunds, disputes, hosted Gateway sessions, and settlement. Runs locally from the @paybond/kit npm package. Needs 3 environment variables to run.
verantis-mcp
MCP server for Verantis — the verified directory for machine payments (x402 & MPP). Find live-verified services and check a wallet before your agent pays. Runs locally from the verantis-mcp Python package. Needs 1 environment variable to run.
frisk
Screen the counterparty of an x402 payment before an agent pays it. Runs offline by default. Runs locally from the frisk-mcp npm package. Needs 2 environment variables to run.
x402-payment-safety
Authorize x402 payments before signing with request-bound, signed safety decisions. Remote server at agent-guild-5d5r.onrender.com.
agentfund
Fundraising tools for AI agents on Solana: create campaigns, donate via x402, check reputation. Runs locally from the @agentfund/mcp npm package. Needs 2 environment variables to run.
anchor-x402
MCP server for anchor-x402 — 14 x402-paid agent utilities on Base + Solana. 9 commodity primitives (anchor, screen, attest, decode/tx, resolve/name, price/token, decode/calldata, parse/datetime, intel/wallet) plus 5 universal LLM endpoints (roast, oracle. Runs locally from the anchor-x402-mcp npm package. Needs 1…