Copiloto Financeiro MCP Server (Botelho31/copiloto-financeiro) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 47 tools. No publisher has claimed this listing.

C
Emerging
74/100
2 months ago

Copiloto Financeiro MCP Server

Enables AI agents to manage personal finances for Brazilian users through MCP tools, including categorizing transactions, reconciling debts, checking cash-flow projections, and adjusting budgets, with integration to Open Finance Brasil via Pluggy.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Botelho31

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 2 credentials: PLUGGY_CLIENT_SECRET, PUSHOVER_APP_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCRON_SCHEDULE(default 0 6 ) — when the daily sync runs.
configDB_PATHPORT (default 3000) / (default ./data/budget.sqlite).
configLARGE_TRANSACTION_THRESHOLD(default 500) — notification rule: flag any newly
configMIN_BUFFER(default 0) — balance floor below which a projected month is
configPLUGGY_CLIENT_ID/ PLUGGY_CLIENT_SECRET / PLUGGY_ITEM_IDS are a one-time
🔐 secretPLUGGY_CLIENT_SECRETPLUGGY_CLIENT_ID / / PLUGGY_ITEM_IDS are a one-time
configPLUGGY_ITEM_IDSPLUGGY_CLIENT_ID / PLUGGY_CLIENT_SECRET / are a one-time
🔐 secretPUSHOVER_APP_TOKEN/ SMTP_HOST + friends — only needed if you want push
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deploySMTP_FROM
deploySMTP_HOST
deploySMTP_PASS
deploySMTP_PORT
deploySMTP_USER
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

47/47 tools missing one or more hints — list_users (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_user (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_user (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +44 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

37/47 tool handlers declare input schemas (79%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 17/47 tool handlers wrap calls in try/catch (36%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 1/47 tools referenced in tests (2%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

4 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/botelho31/copiloto-financeiro)](https://m8ven.ai/mcp/botelho31/copiloto-financeiro)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 25fb382fa35631dc4aa1754a470bf87c1e961c73
code hash: 00f437660a54b552c2d1c70173c71c8b73d41c115a4875135567f8b9d913c0c1
verified: 7/14/2026, 8:29:18 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client