MCP.Market

Caixa MCP server

by codespar·io.github.codespar/mcp-caixa·v0.2.0-alpha.3·271 stars
No reviews yet

MCP server for Caixa Econômica Federal — Pix, Cobrança (SICOB boleto), Extrato (OAuth2 + mTLS)

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Established

271 stars18 downloads/wk

Reviews

Write one

Nobody has reviewed Caixa yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Caixa tools (23, 12 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • cancel_boletowrite action

    Cancel (baixa) an outstanding boleto before payment.

  • consult_fgts

    Query FGTS balance / extrato. Caixa is the sole operator of FGTS (Fundo de Garantia do Tempo de Serviço) and exposes worker-side and employer-side queries through dedicated product contracts.

  • create_boletowrite action

    Issue a boleto via Caixa Cobrança (SICOB). Returns nosso_numero, linha_digitável, barcode, and PDF URL.

  • create_pix_due_chargewrite action

    Create a Pix due-date charge (cobv) with mandatory payer data and due date. Supports fine, interest, discount, and abatement fields.

  • create_pix_qrwrite action

    Create a dynamic Pix charge with QR code (cob). Returns the txid, copy-paste EMV payload, and location URL.

  • delete_dict_keywrite action

    Delete (unregister) a DICT key owned by the merchant. The key must belong to a Caixa account under the merchant's contract.

  • download_boleto_pdf

    Fetch the rendered boleto PDF for an issued boleto. Returns the PDF URL (or base64 bytes) so it can be attached to an invoice or email.

  • get_account_balance

    Return the current balance for a Caixa merchant account, including available, blocked, and overdraft limit if present.

  • get_boleto

    Retrieve a boleto by its Caixa identifier (id or nosso_numero).

  • get_oauth_token

    Mint or return a cached OAuth2 client_credentials bearer token for the Caixa Developer Portal. Exposed so agents can inspect token freshness; normal tool calls obtain tokens implicitly.

  • get_pix

    Retrieve a Pix transaction by its BCB endToEndId (E<ispb><yyyymmddhhmm><sequence>).

  • get_pix_chargewrite action

    Retrieve a Pix immediate charge (cob) by its BCB txid. Returns status, QR payload, and associated received Pix (if paid).

  • get_pix_due_chargewrite action

    Retrieve a Pix due-date charge (cobv) by its BCB txid.

  • get_statement

    Retrieve account statement transactions for a given period. Paginated.

  • list_pix_charges

    List Pix immediate charges (cob) filtered by date range and optional status / CPF / CNPJ. Paginated per BACEN Pix v2.

  • list_pix_received

    List received Pix transactions (pix recebidos) by date range. Useful for reconciliation against cob/cobv charges.

  • pay_tributewrite action

    Pay a federal tribute (DARF, GPS, GRU) or other guia de arrecadação via Caixa. Input is the full 44/47-digit barcode or linha digitável plus debit account. Requires arrecadação contract.

  • refund_pixwrite action

    Refund (devolução) a previously received Pix. Must reference the original endToEndId and a merchant-side refund id.

  • register_dict_key

    Register a DICT key (CPF, CNPJ, email, phone, or EVP) to an account owned by the merchant. Subject to BACEN portability flow for keys claimed elsewhere.

  • resolve_dict_key

    Resolve a DICT key (CPF, CNPJ, email, phone, EVP) to the owner's account data before sending a Pix. Subject to BCB rate limits per consenting payer.

  • send_pixwrite action

    Initiate an outbound Pix payment from the merchant's Caixa account. Amount in BRL major units (e.g. '10.50').

  • transfer_tedwrite action

    Initiate an outbound TED transfer from a Caixa merchant account to an external bank account. Settles same-day within BACEN TED windows.

  • update_pix_chargewrite action

    Update (PATCH) a Pix immediate charge (cob) — e.g. change amount before payment, adjust expiration, or mark as REMOVIDA_PELO_USUARIO_RECEBEDOR.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 29 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Caixa compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Tools
23
the typical server has 7
Tools that change things
52%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
271
more than 95% of 28,688 servers
Downloads a week
18
more than 5% of 12,191 servers with a package

What its tools let an agent do: 10 read · 4 create · 6 change · 2 delete · 1 send or post

Install Caixa in Claude Code, Cursor or VS Code

Runs npx -y @codespar/mcp-caixa on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-caixa -- npx -y @codespar/mcp-caixa
Add to Cursor

What the publisher says

From the Caixa repository's README, as published. We do not edit it. Read it on GitHub

MCP Dev LATAM 🌎 Every commerce API your AI agent needs to run a business in Latin America. Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 · Chile 🇨🇱 · Peru 🇵🇪 · plus 4 agentic payment protocols. MCP servers for LATAM commerce · live in the official MCP Registry · MIT License Machine-readable catalog: codespar.dev/api/servers Catalog · Quick Start · Agentic Protocols · All Servers · Contribute

The Problem

AI agents can write code, analyze data, and chat. But they can't operate a business — collect payments, issue invoices, ship products, or notify customers. Especially not in Latin America, where every service has its own API, auth pattern, and quirks (mTLS for BACEN Pix v2, JWT-RSA for STP-SPEI, AFIP web services, contract-gated developer portals, and on).

Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — and none of them compose cleanly with each other or with the regional rails businesses actually run on.

MCP Dev LATAM bridges both gaps. Traditional LATAM services + the new agentic payment protocols, all accessible through a single MCP interface.

The Solution

Each MCP server in this repo wraps a real provider — payments, fiscal, logistics, messaging, banking, ERP, identity, fraud, crypto, and the agentic protocols — so your agent can operate a complete business workflow.

🛒 Customer places order
  → 💳 Agent charges via Pix (Asaas / Mercado Pago / Zoop)
  → 📄 Agent issues NFe (Nuvem Fiscal / Focus NFe / NFe.io)
  → 📦 Agent generates shipping label (Melhor Envio / Skydropx)
  → 📱 Agent sends tracking via WhatsApp (Z-API / WhatsApp Cloud)
  → 📊 Agent records in ERP (Omie / Bling / Tiny)
  → 🏦 Agent reconciles balance (Stark Bank / Itaú / BTG)

Six systems. Zero human intervention. One agent.

Agentic Payment Protocols

Four servers for the emerging agentic payment stack:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Caixa: common questions

Is Caixa MCP server safe?
Mostly: it is graded B (82/100). Read the Caixa safety report
How do I install Caixa?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Caixa need an API key?
Yes. The registry entry asks for CAIXA_CLIENT_SECRET, CAIXA_KEY_PATH.
Is Caixa maintained?
The last commit was 67 days ago (2026-08-29). The latest release is v0.2.0-alpha.3.
How does Caixa compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 23 (the typical server has 7); tools that change things 52% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from codespar →