MCP Radar
MCP Server

Conta Bemol MCP

io.github.mcp-dir/contabemol-mcp
Finance & Investing Payments & Fintech Public & reachable MCP 2025-11-25

What this MCP does

Provides access to Conta Bemol account data through Brazilian Open Finance, including balances, transactions, cards, bills, loans, and investments.

Capabilities

Tools

25 tools
authenticate
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'token': {'type': 'string'}}}
connect
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
marketplace
The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
Open world
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'number', 'default': 10}, 'query': {'type': 'string', 'default': ''}, 'action': {'enum': ['search', 'describe', 'install', 'uninstall', 'subscribe', 'cancel', 'resume', 'report_bug', 'request_mcp', 'list_tools', 'invoke', 'search_prompts', 'get_prompt', 'publish_prompt'], 'type': 'string', 'default': 'search'}, 'mcp_id': {'type': 'string', 'default': ''}, 'message': {'type': 'string', 'default': ''}, 'tool_id': {'type': 'string', 'default': ''}, 'arguments': {'type': 'string', 'default': '{}'}, 'immediate': {'type': 'boolean', 'default': False}, 'tier_slug': {'type': 'string', 'default': ''}, 'prompt_body': {'type': 'string', 'default': ''}, 'prompt_slug': {'type': 'string', 'default': ''}, 'prompt_tool': {'type': 'string', 'default': ''}, 'prompt_vars': {'type': 'string', 'default': '{}'}, 'conversation': {'type': 'string', 'default': '[]'}, 'prompt_title': {'type': 'string', 'default': ''}, 'request_name': {'type': 'string', 'default': ''}, 'cancel_reason': {'enum': ['too_expensive', 'missing_features', 'switched_service', 'unused', 'customer_service', 'too_complex', 'low_quality', 'other'], 'type': 'string'}, 'cancel_comment': {'type': 'string', 'default': ''}, 'prompt_targets': {'type': 'array', 'items': {'enum': ['claude', 'chatgpt', 'cursor', 'lovable'], 'type': 'string'}, 'default': []}, 'report_context': {'type': 'string', 'default': ''}, 'prompt_category': {'type': 'string', 'default': ''}, 'request_details': {'type': 'string', 'default': ''}, 'prompt_description': {'type': 'string', 'default': ''}}}
openfinance_disconnect_bank
Revokes the Open Finance consent for a specific bank and deletes the connection data. The bank's data will no longer be available. Returns an add_connection_url to re-connect if needed.
Destructive
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['item'], 'properties': {'item': {'type': 'string'}}}
openfinance_force_sync
Forces the bank to re-sync one or more connections NOW and WAITS for it to finish (PATCH /items/:id, then polls until the item stops updating, up to ~60s). Use this when a balance or transaction list looks stale: a connection can read UPDATED yet be hours old, and this pulls fresh data WITHOUT disconnecting/reconnecting. Pass `items` as an array of selectors (item_id, connector_id, connector_name, or the user-set custom_label nickname); OMIT `items` to sync ALL linked banks. Returns `{ results, errors }`; each result has the final `status`, `executionStatus`, `lastUpdatedAt` (advances when data is refreshed), and `synced` (true = fresh data is ready). `needs_action` (e.g. MFA_REINTERACTION / LOGIN_ERROR / WAITING_USER_INPUT) means the user must re-authenticate — those results include a `reconnect_url` that opens the widget in UPDATE mode for that exact connection (user enters credentials / MFA token, data refreshes in place, no slot consumed, no disconnect needed). `timed_out: true` means the sync is still running — re-check with openfinance_get_item_status. Set `wait: false` for fire-and-forget (returns immediately while UPDATING).
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'wait': {'type': 'boolean'}, 'items': {'type': 'array', 'items': {'type': 'string'}}}}
openfinance_get_account_balance
Returns the latest available balance per account id (GET /accounts/:id/balance). This is the freshest balance the provider can serve, but it is a SNAPSHOT anchored to the connection's last upstream sync: the `updateDateTime`/`updatedAt` in each row is that sync instant, NOT a to-the-second live read. If a movement that just happened is not reflected yet, or the balance disagrees with the sum of openfinance_list_transactions, run openfinance_force_sync to pull fresh data and then re-read. Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR (provider could not fetch it) or BALANCE_CONSENT_ERROR (the institution refused it because the consent lacks the balance permission — reconnecting the bank restores it) — those rows include a structured `warning` instead of throwing. When the financial institution is temporarily unavailable upstream (5xx) or the connector is not Open Finance, the row DEGRADES to the last-synced balance with `realtime: false`, `updatedAt` and a `warning` instead of an error. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['account_ids'], 'properties': {'account_ids': {'type': 'array', 'items': {'type': 'string'}}}}
openfinance_get_accounts_detail
Returns full account objects including extended creditData (additional cards, limits) per id (GET /accounts/:id). Pass `account_ids` as an array (1–50). `{ results, errors }` batch shape. May include a `provider_incident` block when the Open Finance provider has an OPEN incident affecting a connected bank: credit limits and balances may be unreliable (e.g. a limit near 1,00) until the provider recovers. Do not present those values as real.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['account_ids'], 'properties': {'account_ids': {'type': 'array', 'items': {'type': 'string'}}}}
openfinance_get_credit_card_bill
Returns bill-level detail for one or more credit card bills by id (GET /bills/:id): `dueDate`, `billClosingDate` (when the cycle closed — the boundary that defines which purchases belong to this bill), `totalAmount`, financeCharges and payments[] (id, paymentDate, amount, valueType, paymentMode). ITEMIZED PURCHASES (OPT-IN): the bank's bill payload has no transactions in it — they live on the card ACCOUNT. Pass `include_transactions:true` (plus `account_id` of the credit card, since the bill itself carries no account reference) and each row also gets `transactions[]`, `transactions_count`, `transactions_sum` and `reconciles_with_total`, already matched to that bill. Always check `transactions_basis`: `bill_id` = exact (the bank tagged each transaction with this bill — the normal case for CLOSED bills), `date_window` = ESTIMATE (`confidence:'low'`, window echoed in `transactions_window`) used when the connector tags no billId or the bill is still open (PENDING lines get no billId until the cycle closes), `unavailable` = no link possible. Opt-in because it costs an extra full transaction scan of the account. Whatever the basis, the bill's own `totalAmount` is authoritative — do NOT rebuild it by summing transactions. Without the opt-in the response carries a `transactions_hint`; you can also fetch them yourself via openfinance_list_transactions with the credit card account_id and a from/to range ending at `billClosingDate`. Pass `bill_ids` as an array — use openfinance_list_credit_card_bills first to discover ids. `{ results, errors }` batch shape. NOTE: Pluggy does NOT return a paid/status field. In Brazilian Open Finance, `payments[]` reflects payments registered during THIS bill's billing cycle — typically the payment of the PREVIOUS bill (do NOT assume this bill was paid just because `payments[]` is non-empty). To check paid status, prefer `openfinance_list_credit_card_bills` which derives `payment_status` via cross-bill match.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['bill_ids'], 'properties': {'bill_ids': {'type': 'array', 'items': {'type': 'string'}}, 'account_id': {'type': 'string'}, 'transactions_detail': {'enum': ['compact', 'rich', 'raw'], 'type': 'string'}, 'include_transactions': {'type': 'boolean'}}}
openfinance_get_item_status
Returns the current status of a bank connection (UPDATED, UPDATING, LOGIN_ERROR, etc.), its executionStatus, connector metadata, and a reconnect_url that reopens the widget in UPDATE mode for that connection (re-authenticate / enter MFA token in place, without disconnecting and without consuming a connection slot). Omit `item` to get the status of ALL linked banks at once (returns `{ count, items }`); pass `item` for a single bank. Bulk support: accepts item_ids for batched execution.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'item': {'type': 'string'}, 'item_id': {'type': 'string'}, 'item_ids': {'type': 'array', 'items': {'type': 'string'}}}}
openfinance_get_loan_detail
Returns full loan contract detail by id (GET /loans/:loanId): interestRates[] (taxType, ratePercentage, indexer), contractedFinanceCharges[], balloonPayments[], warranties[], installments schedule (installmentsCount, paidInstallments, numberOfInstallmentsRemaining, installmentFrequency), amortizationScheduled, CET, ipocCode and dates. Use after openfinance_list_loans to deep-dive on a specific contract. Pass `loan_ids` as an array (1-50). `{ results, errors }` batch shape.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['loan_ids'], 'properties': {'loan_ids': {'type': 'array', 'items': {'type': 'string'}}}}
openfinance_list_accounts
Returns accounts for a bank connection: BANK (checking/savings) and CREDIT (credit card) with balance, number, type, subtype, bankData, and creditData. Also returns `bank` (the brand/connector name like 'Nubank Empresas' — same shown in the dashboard UI) and `connector_id`. Note: each account's `name` is the legal entity that issues the account (e.g. 'Nu Pagamentos S.A. - Instituição de Pagamento'), which is not the same as the brand — when referring to the bank in user-facing text, use `bank`. OMIT `item` to list accounts across ALL linked banks at once — the response aggregates every connection's accounts into `results`, each row tagged with its own `bank`/`connector_id`/`item_id` (use this when the user asks for 'my accounts/cards' without naming a bank). Pass `item` to target a single bank (response carries `bank`/`connector_id`/`item_id` at the root). CREDIT (credit card) `balance`: its meaning is CONNECTOR-DEPENDENT — some banks report the current open-bill partial, others the full revolving/installment debt — so do NOT treat `balance` as 'this month's bill'. The open billing cycle is defined by `creditData.balanceCloseDate` (when it closes) / `balanceDueDate` (when it's due). For a standardized open-bill amount and total debt that mean the same across connectors, use openfinance_list_credit_card_bills (`open_bill` + `total_pending_debt`, derived from PENDING transactions); closed bills come from that same tool's `results`. A CREDIT row may carry `creditData.usedAmount` (how much of THIS card's limit the bank reports as consumed) and a `balance_notice`. `balance_notice` means `balance` came back 0,00 while the bank's own payload indicates an outstanding amount — some issuers never fill the card's consolidated balance field. When it is present, do NOT tell the user the card has nothing to pay: read the amount from openfinance_list_credit_card_bills instead. `bankData.closingBalance` and `automaticallyInvestedBalance` are provider-reported extras that can LAG right after a connection is first created: the bank may publish the connection as UPDATED before those derived fields converge, so they can briefly carry a stale/phantom value that a force sync (openfinance_force_sync) reconciles. The account's own `balance` is authoritative — treat those two as hints until they agree with it. May include a `provider_incident` block when the Open Finance provider has an OPEN incident affecting a bank in this response: balances and credit limits may be unreliable (incomplete or wrong, e.g. a credit limit near 1,00) even with the connection UPDATED, until the provider recovers. Do not present those values as real. May include an `identity_notice` when the SAME account (same number) arrives via two connections stamped with DIFFERENT owner/taxNumber: in Open Finance those fields reflect each connection's CONSENT HOLDER (e.g. a joint account consented by both holders), so dedupe by account number before summing balances and do not attribute ownership by owner/taxNumber for those accounts. Bulk support: accepts item_ids for batched execution.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'item': {'type': 'string'}, 'type': {'enum': ['BANK', 'CREDIT'], 'type': 'string'}, 'item_id': {'type': 'string'}, 'item_ids': {'type': 'array', 'items': {'type': 'string'}}}}
openfinance_list_categories
Returns Pluggy's transaction category taxonomy (GET /categories), cached for the adapter session. Each entry has `id` (the categoryId used by openfinance_update_transaction_category), `description` (English), `descriptionTranslated` (Portuguese — prefer this for pt-BR users), `parentId` and `parentDescription` (the tree parent). Single aggregated response — no batch ids.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
openfinance_list_connections
Returns the saved bank connections for this install: connector_id, item_id, bank name, a per-connection reconnect_url, and an add_connection_url to link additional banks via the Open Finance widget. The reconnect_url reopens the widget in UPDATE mode for that EXISTING connection (user re-enters credentials / MFA token and the data refreshes in place) — use it when a connection needs re-authentication (MFA connectors, LOGIN_ERROR, stale non-Open-Finance data). It does NOT consume a connection slot and does NOT require disconnecting first.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
openfinance_list_credit_card_bills
Returns CLOSED credit card bills for a CREDIT-type account: dueDate, totalAmount, minimumPaymentAmount, allowsInstallments, plus `payments[]` (id, paymentDate, amount, valueType, paymentMode), `payments_count`, `payments_total`, finance charges aggregates, and a derived `payment_status` per bill. IMPORTANT — Brazilian Open Finance semantics: Pluggy does NOT return a `paid`/`status` field. The payment goes into the `payments[]` of the bill whose CYCLE contains the paymentDate (closing ≈ dueDate − 7d): pre-payment before close stays on the bill being paid; payment between close and due, or after due, lands on the NEXT bill. So `payments[]` on a bill commonly carries the previous bill's payment, NOT the current one's — do NOT assume this bill was paid just because `payments[]` is non-empty. Use the derived `payment_status` (`PAID` | `OPEN` | `PAST_DUE_UNCONFIRMED` | `PAST_DUE_UNPAID`): a bill is `PAID` when its OWN `payments[]` (early pre-payment) or ANY newer bill in the payload contains a payment with amount ≈ this bill's `totalAmount` (±R$0.50). The MOST RECENT bill that's past-due, with no own pre-payment match, cannot be confirmed via cross-bill (the next cycle hasn't closed yet) — it returns `PAST_DUE_UNCONFIRMED`. NEVER call such a bill 'vencida' categorically; flag that the payment may have been made between close and due and not yet reflected upstream. The full `payment_status_legend` is returned alongside the results. OPEN BILL & TOTAL DEBT (standardized, derived — OPT-IN): pass `include_open_bill:true` to ALSO get `open_bill` (the current not-yet-closed bill, próxima a vencer) and `total_pending_debt` (saldo devedor total = all pending installments), BOTH derived from PENDING transactions so they mean the same thing across connectors — use these instead of the CREDIT account's `balance`, whose meaning VARIES by connector (some report the open-bill partial, others the full installment debt). `open_bill` = { available, method (`cycle_dates` = real close/due dates | `calendar_month_fallback` = estimated, `confidence:'low'`), close_date, due_date, total_amount (net charges − credits), transaction_count }; plus a `future_bills[]` breakdown per month — LOW-confidence forward projections of PENDING installments (`confidence:'low'`, `basis`), NOT authoritative bills (for closed months trust the `results` `totalAmount`). CONNECTOR ASYMMETRY: where the bank does NOT expose the open bill before closing (only closed bills, no reliable cycle dates), `open_bill.available` is `false` with a `reason` (`connector_exposes_no_pending` or `open_bill_not_published`) — that bill isn't retrievable by any endpoint until it closes (upstream limit of the institution's Open Finance feed, not our filter); check the bank app for the current open bill. When per-transaction billId grouping does not reconcile with the bills' totals, a `bill_grouping_reliability` warning is attached (trust `totalAmount`, do not sum by billId). Default `false` (the projection runs an extra accounts+transactions scan, so it's opt-in). The response opens with an `account` echo block ({ account_id, bank, name, number, type, item_id }) identifying WHICH card/bank these bills belong to. When more than one bank is connected, ALWAYS cross-check the echo against the card you intended to query and name the bank when presenting results — never attribute one bank's bills to another. This tool's `results` are bill-level summaries — NOT individual transactions, and each bill's `totalAmount` (from the bank) is the AUTHORITATIVE amount. To see itemized purchases/charges, use openfinance_list_transactions with the CREDIT account_id — but note `creditCardMetadata.billId` is a per-connector hint that can be sparse/inconsistent (e.g. Nubank), so do NOT reconstruct a bill total by summing transactions by billId. Returns a warning instead of failing if the CREDIT_CARDS product is not enabled. Bulk support: accepts account_ids for batched execution.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['account_id'], 'properties': {'page': {'type': 'number'}, 'page_size': {'type': 'number'}, 'account_id': {'type': 'string'}, 'account_ids': {'type': 'array', 'items': {'type': 'string'}}, 'include_open_bill': {'type': 'boolean'}}}
openfinance_list_investments
Returns the investment portfolio for a connection (broker or bank with INVESTMENTS product enabled): FIIs, stocks, ETFs, fixed income (CDB/LCI/LCA/Tesouro), mutual funds, retirement (previdência) and COE. Each row carries balance, amount, amountOriginal, amountProfit, lastMonthRate / annualRate / lastTwelveMonthsRate (when available), dueDate, issuer, ISIN, etc. Returns { total:0, results:[], warning } instead of throwing when INVESTMENTS isn't enabled (403) or other upstream errors. DATA INTEGRITY: when MULTIPLE positions come back as TOTAL_WITHDRAWAL with balance/quantity 0 at once (mass zeroing), the tool cross-checks each position's own transaction history upstream; if the zeroing is contradicted (BUY with no sale/redemption/transfer) the response carries `data_integrity_warning` and the affected rows are flagged `integrity:'suspect_zeroed'` — treat those balances as UNAVAILABLE (likely a temporary connector failure publishing zeros), never as real R$0, and do NOT sum them into the portfolio. Bulk support: accepts item_ids for batched execution.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'item': {'type': 'string'}, 'page': {'type': 'number'}, 'type': {'enum': ['COE', 'EQUITY', 'ETF', 'FIXED_INCOME', 'MUTUAL_FUND', 'SECURITY', 'OTHER'], 'type': 'string'}, 'item_id': {'type': 'string'}, 'item_ids': {'type': 'array', 'items': {'type': 'string'}}, 'page_size': {'type': 'number'}}}
openfinance_list_investment_transactions
Returns the movement history for a specific investment position: BUY / SELL / TAX / INTEREST / AMORTIZATION / TRANSFER. Each row carries quantity, value, amount, netAmount, agreedRate (treasury), brokerageNumber, and itemized `expenses` (brokerageFee, incomeTax, settlementFee, custodyFee, stockExchangeFee, etc.). Use after openfinance_list_investments to get the investment_id. Bulk support: accepts investment_ids for batched execution.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['investment_id'], 'properties': {'page': {'type': 'number'}, 'page_size': {'type': 'number'}, 'investment_id': {'type': 'string'}, 'investment_ids': {'type': 'array', 'items': {'type': 'string'}}}}
openfinance_list_loans
Lists loan contracts per bank connection (GET /loans). Pass `items` as an array of connection selectors (item_id uuid, connector_id, or connector_name) — one entry per connection to fetch; multiple connections are queried sequentially with rate-limit spacing. OMIT `items` to list loans across ALL linked banks. Returns `{ results, errors }` per connection.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'items': {'type': 'array', 'items': {'type': 'string'}}}}
openfinance_list_transactions
Returns transactions for a bank account (BANK or CREDIT type). For CREDIT (credit card) accounts, this is the ONLY way to get itemized transactions (purchases, subscriptions, etc.). Each credit card transaction MAY carry `creditCardMetadata.billId` pointing at a bill from openfinance_list_credit_card_bills, but this is a per-connector HINT, not authoritative: some connectors (e.g. Nubank) populate it sparsely (many transactions and installments arrive with no billId) or inconsistently (the same payment tagged to more than one bill). Do NOT reconstruct a bill's total by summing transactions by billId — the bill's own `totalAmount` from openfinance_list_credit_card_bills is the source of truth. CREDIT PENDING vs POSTED varies by connector: where the bank exposes future-dated `status:'PENDING'` installments, those represent the OPEN bill plus future bills (future months); where it does NOT, only the last closed bill's POSTED items appear until ~closing. Same query, different coverage per bank (upstream). To get a standardized open-bill total / total debt regardless, use openfinance_list_credit_card_bills (`open_bill` / `total_pending_debt`). SCHEDULED (future-dated) ROWS: results are ordered by date DESCENDING, and on a card with long installment plans the TOP of the list is the FUTURE — rows dated months ahead are scheduled installments of purchases already made, not new purchases. Every such row is flagged `scheduled:true`, the response carries `scheduled_count` and a `notice` naming the most recent row that actually happened. NEVER read the first row as 'the latest purchase' without checking `scheduled`. To list only what already happened, pass `to` = today. Supports from/to date filters (ISO YYYY-MM-DD) and an optional keyword filter via `search_queries` (case- and accent-insensitive substring match against description and merchant name, OR semantics across multiple terms). When `search_queries` is set the tool aggregates up to 5000 transactions within from/to before filtering — narrow from/to if `truncated:true` is returned. PAGINATION: OMIT both `page` and `page_size` (the default) to get ALL transactions in the from/to range in one call — the tool auto-paginates the upstream and returns them under a single logical page (`page:1`, `totalPages:1`), up to a 5000 ceiling (`truncated:true` + warning if exceeded, then narrow from/to). Passing `page` and/or `page_size` switches to MANUAL pagination: you get one page (`page_size` items, default 50, max 500; `page` defaults to 1) with the REAL `total`/`totalPages`, so `page_size:5` alone returns the first 5 with `totalPages` telling you how many pages remain. On upstream errors, returns { total:0, results:[], warning, error } instead of throwing. `detail` controls how much per-row data you get (default `'compact'` = slim, cheap). Use `detail:'rich'` to enrich each row (when the bank connector provides it) with `merchantInfo` (estabelecimento: businessName/razão social, cnpj, cnae, category — useful for auto-classifying spending) and extra `creditCardMetadata` fields: `billId` (a per-connector HINT toward the transaction's bill — sparse/inconsistent on some connectors like Nubank, so do NOT sum by it to get a bill total; use the bill's `totalAmount` instead), `billForecastDate`, `cardNumber`, `purchaseDate`, `payeeMCC`, `feeType`/`feeTypeAdditionalInfo`, `otherCreditsType`/`otherCreditsAdditionalInfo`. `billForecastDate` ("YYYY-MM") is the counterpart of `billId` for the OPEN cycle: PENDING transactions have NO billId (the bank only mints it once the bill closes), so this is the only field telling you which bill a pending purchase will land in — its month OFFSET is per-connector (some banks month+1, others month+0), so surface it as-is and do not derive a due date from it. `cardNumber` (last 4 digits) separates the primary cardholder's charges from an additional card's when several cards share one account_id. Use `detail:'raw'` to get the FULL untouched Pluggy transaction object (everything Pluggy returns, un-normalized — heaviest, for when you need a field we don't project). 'rich'/'raw' add tokens per row and coverage varies by bank/Open Finance, so keep the default for normal listings. For the card's statement closing/due dates use openfinance_list_accounts (`creditData.balanceCloseDate` / `balanceDueDate`). The response opens with an `account` echo block ({ account_id, bank, name, number, type, item_id }) identifying WHICH account/bank these transactions belong to. When more than one bank is connected, ALWAYS cross-check the echo against the account you intended to query and name the bank when presenting results — never attribute one bank's transactions to another. If total is 0 for a CREDIT account, check the connection health via openfinance_get_item_status — `statusDetail.creditCards.isUpdated: false` means the credit card sync failed and a force sync (openfinance_force_sync) or reconnection may be needed. May include a `provider_incident` block when the Open Finance provider has an OPEN incident affecting a connected bank: transactions may come back incomplete or wrong until the provider recovers, and reconnecting does not fix it. Bulk support: accepts account_ids for batched execution.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['account_id'], 'properties': {'to': {'type': 'string'}, 'from': {'type': 'string'}, 'page': {'type': 'number'}, 'detail': {'enum': ['compact', 'rich', 'raw'], 'type': 'string'}, 'page_size': {'type': 'number'}, 'account_id': {'type': 'string'}, 'account_ids': {'type': 'array', 'items': {'type': 'string'}}, 'search_queries': {'type': 'array', 'items': {'type': 'string'}}}}
openfinance_list_transactions_by_item
Consolidated cash-flow analysis for a whole bank CONNECTION over a period, in ONE call. Resolves the connection's accounts internally and fans out their transactions, so you do NOT need to call openfinance_list_accounts first nor carry account_id uuids between calls. Pass `item` (connector_id, connector_name or item_id) to target one bank, or OMIT it to analyze ALL linked banks at once. `from`/`to` are ISO dates (YYYY-MM-DD). Default `granularity:'monthly'` returns a COMPACT summary (no raw rows): total entradas, saídas, saldo_liquido, monthly evolution (`por_mes`), and `top_despesas`/`top_recebimentos` (largest N each), plus a per-account breakdown (`by_account`). Use this for 'análise anual/mensal', 'fluxo de caixa', 'entradas e saídas', 'maiores gastos/recebimentos'. Set `granularity:'raw'` to ALSO get every consolidated transaction (heavier — only when itemized rows are needed); combine with `detail:'rich'` to enrich those rows with merchantInfo (cnpj/cnae/businessName/category) + extra creditCardMetadata (billId, purchaseDate, fees), or `detail:'raw'` for the full untouched Pluggy object per row, when the connector provides them. `type` filters BANK or CREDIT accounts. On a connection with many transactions the scan caps at 5000/account and flags `truncated:true`. May include a `provider_incident` block when the Open Finance provider has an OPEN incident affecting a connected bank: the totals/rows may be incomplete or wrong until the provider recovers, and reconnecting does not fix it. Bulk support: accepts item_ids for batched execution.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'to': {'type': 'string'}, 'from': {'type': 'string'}, 'item': {'type': 'string'}, 'type': {'enum': ['BANK', 'CREDIT'], 'type': 'string'}, 'top_n': {'type': 'number'}, 'detail': {'enum': ['compact', 'rich', 'raw'], 'type': 'string'}, 'item_id': {'type': 'string'}, 'item_ids': {'type': 'array', 'items': {'type': 'string'}}, 'granularity': {'enum': ['monthly', 'raw'], 'type': 'string'}}}
openfinance_provider_status
Checks the LIVE operational status of the Open Finance provider (its public status page) — this is the PROVIDER's health, separate from your own connection's `openfinance_get_item_status`. Use it whenever data looks incomplete or stale even though a connection shows UPDATED (accounts/transactions/balances missing, a bank not returning everything): it reveals an upstream outage or a known incident on a specific bank/connector, so you can tell a provider-side problem apart from a connection that just needs reconnecting. Returns the global indicator (none/minor/major/critical), degraded components, open incidents, and — when you have banks connected — flags the incidents that affect YOUR connected banks in `your_banks_affected`.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
openfinance_search_bank_connectors
Searches the available bank connectors by name (pass keywords[], e.g. ['nubank','btg']) and returns, per match: the connector id, whether it's Open Finance or API (`access`), PF/PJ (`audience`), the user's already-linked connections (and accounts when include_accounts=true), and a ready `connect_url` with the bank pre-selected. Some non-Open-Finance credential connectors carry a `caveat` warning that they don't auto-update (needs periodic manual reconnection) — surface it so the user can prefer the institution's Open Finance connector for automation. Honors the user's plan (a PF plan hides PJ banks; a PJ plan covers BOTH — PF and PJ banks connect and count under the same plan). Call this BEFORE connecting to hand the user a one-click link to the right bank. keywords[] is REQUIRED — without it returns a hint (never dumps the whole catalog).
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'keywords': {'type': 'array', 'items': {'type': 'string'}}, 'include_accounts': {'type': 'boolean'}}}
openfinance_update_transaction_category
Corrects the category of one or more transactions (PATCH /transactions/:id). Pass `items` as an array of { transaction_id, category_id } — `transaction_id` comes from openfinance_list_transactions, `category_id` from openfinance_list_categories. This overrides Pluggy's automatic categorization AND teaches Pluggy: recategorizing a transaction automatically creates a Category Rule for this client (case-insensitive exact match on the transaction's data), so FUTURE similar transactions are categorized the same way — use this to fix miscategorized transactions and improve categorization accuracy going forward. Batch shape: returns `{ updated, results: [{ transaction_id, category, categoryId }], errors: [{ id, status, message }] }` — per-item errors do not fail the whole batch.
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['items'], 'properties': {'items': {'type': 'array', 'items': {'type': 'object', 'required': ['transaction_id', 'category_id'], 'properties': {'category_id': {'type': 'string'}, 'transaction_id': {'type': 'string'}}}}}}
report_bug
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['message'], 'properties': {'context': {'type': 'string', 'default': ''}, 'message': {'type': 'string'}, 'conversation': {'type': 'string', 'default': '[]'}}}
show_version
Show the current MCP platform and adapter versions.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
toolkit_info
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Read only Idempotent
Input schema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
History

Recent tool changes

Added
authenticate
Sept. 17, 2026, 12:43 p.m.
Added
marketplace
Sept. 17, 2026, 12:43 p.m.
Added
toolkit_info
Sept. 17, 2026, 12:43 p.m.
Added
connect
Sept. 17, 2026, 12:43 p.m.
Added
report_bug
Sept. 17, 2026, 12:43 p.m.
Added
show_version
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_disconnect_bank
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_update_transaction_category
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_list_categories
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_get_credit_card_bill
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_get_accounts_detail
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_get_account_balance
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_force_sync
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_get_loan_detail
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_list_loans
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_list_investment_transactions
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_list_investments
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_list_credit_card_bills
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_list_transactions_by_item
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_list_transactions
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_list_accounts
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_provider_status
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_get_item_status
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_list_connections
Sept. 17, 2026, 12:43 p.m.
Added
openfinance_search_bank_connectors
Sept. 17, 2026, 12:43 p.m.
Discover

Similar MCP servers

Lovie Company Formation

co.lovie/company-formation

Supports company formation and business administration with bank accounts, cards, invoicing, bookkeeping, accounting periods, and…

FortFi Treasury MCP

io.github.rebelArtists/fortfi-treasury-mcp

Provides policy-controlled crypto treasury operations across chains, including wallets, payments, token discovery, swaps, bridges…

AINumbers Fintech Intelligence Suite

co.ainumbers/tools

Provides deterministic fintech, payment-policy, financial analysis, regulatory compliance, credential integrity, and audit-trail …

Contazz AutoPilot

io.github.MarcioKorpHub/contazz-autopilot

Automates Brazilian accounting and tax operations including invoicing, collections, Pix charges, reconciliation, financial report…

Conta Azul MCP

io.github.douglac/contaazul-mcp

Connects to Conta Azul ERP for managing customers, sales, budgets, contracts, financial accounts, receivables, invoices, settleme…

Gate DEX MCP

io.github.gateio-dev/gate-dex

Supports wallet authentication, blockchain RPC access, token and market data, transaction construction, transfers, swaps, approva…

blindoracle

io.github.craigmbrown/blindoracle

Offers paid, verifiable research and data services alongside agent trust checks, settlement attestations, crypto market analysis,…

Fintech Intel

io.github.pipeworx-io/fintech-intel

Produces fintech and banking analyses using financial statements, market data, FDIC information, consumer complaints, and regulat…