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/PaddleHQ/paddle-agent-skillsWrote 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/paddlehq/paddle-agent-skills/plugin-paddle-live)<a href="https://agentmods.dev/mcp/paddlehq/paddle-agent-skills/plugin-paddle-live"><img src="https://agentmods.dev/badge/mcp/paddlehq/paddle-agent-skills/plugin-paddle-live.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
paddle-live 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 8d 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
{
"paddle-live": {
"type": "http",
"url": "https://mcp.paddle.com/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 8d ago First seen · 6 lines scan A df9a2fdeaedb
paddle-live is an MCP server published in the GitHub repository PaddleHQ/paddle-agent-skills (6 stars, last pushed 29d 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
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.
mcp-epayco
MCP server for ePayco — Colombian gateway: cards, PSE, Daviplata and cash networks. Runs locally from the @codespar/mcp-epayco npm package. Needs 3 environment variables to run.
mcp-flow-cl
MCP server for Flow.cl — Chilean PSP: hosted payment orders, Webpay, refunds, HMAC-signed API. Runs locally from the @codespar/mcp-flow-cl npm package. Needs 3 environment variables to run.
mcp-bold-co
MCP server for Bold — Colombian acquirer: payment links for cards, PSE and Nequi. Runs locally from the @codespar/mcp-bold-co npm package. Needs 2 environment variables to run.
mcp-braspag
MCP server for Braspag — Cielo orchestration, token vault (Cartão Protegido), recurrence, split. Runs locally from the @codespar/mcp-braspag npm package. Needs 3 environment variables to run.
mcp-picpay
MCP server for PicPay Business — BR digital wallet (60M+ users): checkout, Pix QR, subscriptions. Runs locally from the @codespar/mcp-picpay npm package. Needs 3 environment variables to run.