Mercado Bitcoin MCP Server
mcp-mercado-bitcoin
npm
v1.1.1
Published by rodrigoflorencio86 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP Server for Mercado Bitcoin — trade, monitor and manage your crypto portfolio via any LLM or AI agent
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
medium Hardcoded egress to an external endpoint (build/auth.js)MTC-SRC-003
In the server's implementation (`build/auth.js:29`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const res = await fetch("https://api.mercadobitcoin.net/api/v4/oauth2/token", { method: "POST",
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/auth.js
Tools 31
Each tool and what it can reach — statically extracted from the published source.
mb_cancel_all_ordersno sensitive capabilitymb_cancel_orderno sensitive capabilitymb_create_accountno sensitive capabilitymb_get_asset_feesno sensitive capabilitymb_get_asset_networksno sensitive capabilitymb_get_balancesno sensitive capabilitymb_get_brl_withdraw_configno sensitive capabilitymb_get_candlesno sensitive capabilitymb_get_deposit_addressesno sensitive capabilitymb_get_orderno sensitive capability
Show 21 more tools ↓
mb_get_orderbookno sensitive capabilitymb_get_positionsno sensitive capabilitymb_get_symbolsno sensitive capabilitymb_get_tickersno sensitive capabilitymb_get_tierno sensitive capabilitymb_get_tradesno sensitive capabilitymb_get_trading_feesno sensitive capabilitymb_get_withdraw_limitsno sensitive capabilitymb_get_withdrawalno sensitive capabilitymb_internal_transferno sensitive capabilitymb_list_accountsno sensitive capabilitymb_list_all_ordersno sensitive capabilitymb_list_bank_accountsno sensitive capabilitymb_list_depositsno sensitive capabilitymb_list_fiat_depositsno sensitive capabilitymb_list_ordersno sensitive capabilitymb_list_withdraw_addressesno sensitive capabilitymb_list_withdrawalsno sensitive capabilitymb_place_orderno sensitive capabilitymb_statusno sensitive capabilitymb_withdrawno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (31 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.1.1 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-08 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-mercado-bitcoin --onlineMore in Finance & Commerce
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.