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/edsonvmendes/miniframe-tools-mcp/miniframe-toolsgit clone --depth 1 https://github.com/edsonvmendes/miniframe-tools-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/edsonvmendes/miniframe-tools-mcp/miniframe-tools)<a href="https://agentmods.dev/mcp/edsonvmendes/miniframe-tools-mcp/miniframe-tools"><img src="https://agentmods.dev/badge/mcp/edsonvmendes/miniframe-tools-mcp/miniframe-tools.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
miniframe-tools 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.
What it actually says
{
"miniframe-tools": {
"command": "npx",
"args": [
"-y",
"miniframe-tools-mcp"
],
"env": {
"EVM_PRIVATE_KEY": "",
"MINIFRAME_API_URL": ""
}
}
}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 · 13 lines scan A 31727e05b051
miniframe-tools is an MCP server published in the GitHub repository edsonvmendes/miniframe-tools-mcp (1 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
banco-mcp
Brazilian Open Finance MCP — 30+ banks (Itaú, Nubank, etc.) to Claude/Cursor. Read-only. Remote server at api.mcp.ai.
china-bank-offers-facts
MCP server "china-bank-offers-facts", hosted remotely at agent-offers-api-replitzip.replit.app, as configured in badDevBuild/china-bank-offers-facts.
mcp-itau
MCP server for Itaú Unibanco — Pix, Cobrança (boleto), Arrecadação, Extrato (OAuth2 + mTLS). Runs locally from the @codespar/mcp-itau npm package. Needs 5 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.
mcp-bradesco
MCP server for Bradesco — Pix, Cobrança (boleto), Arrecadação, Extrato (OAuth2 + mTLS). Runs locally from the @codespar/mcp-bradesco npm package. Needs 5 environment variables to run.
mcp-caixa
MCP server for Caixa Econômica Federal — Pix, Cobrança (SICOB boleto), Extrato (OAuth2 + mTLS). Runs locally from the @codespar/mcp-caixa npm package. Needs 5 environment variables to run.