Stone MCP server

by codespar·io.github.codespar/mcp-stone·v0.2.2·271 stars

No reviews yet

MCP server for Stone — open banking, payments, Pix, transfers

B82/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B82/100

full report

Adoption

Growing

271 stars

Reviews

Write one

Nobody has reviewed Stone yet.

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

Stone tools (21, 9 write)

write = sends, deletes, buys or posts

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

cancel_transactionwrite action
Cancel an authorized (not-yet-captured) transaction
create_anticipationwrite action
Anticipate future receivables (Stone's flagship 'antecipação')
create_boletowrite action
Create a boleto bancário for charging a customer
create_card_chargewrite action
Charge a credit or debit card (Stone acquiring)
create_paymentwrite action
Create a payment via Stone
create_pix_chargewrite action
Create a Pix charge (QR Code / cob) to receive a payment
create_pix_paymentwrite action
Create a Pix payment (outbound) via Stone
create_transferwrite action
Create a bank transfer (internal or external)
get_anticipation_limits
Get current anticipation limits (max / min / available) for a merchant
get_balance
Get account balance
get_payment
Get payment details by ID
get_statement
Get account statement for a period
get_terminal_status
Get current status of a specific POS terminal (online / offline / last seen)
list_payments
List payments with optional filters
list_receivables
Search receivables (future credits from card transactions)
list_terminals
List physical Stone / TON terminals for a merchant
list_transactions
List account transactions
list_webhooks
List registered webhook endpoints
refund_transactionwrite action
Refund a settled transaction (full or partial)
register_webhook
Register a webhook endpoint for Stone events
tokenize_card
Tokenize a card to PCI-safe token for later charging

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.Rubric Appeal a finding JSON

How Stone 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: 21; the typical server has 7
Tools that change things: 43%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 271; more than 95% of 28,688 servers

What its tools let an agent do: 11 read · 8 create · 1 change · 1 delete

Install Stone in Claude Code, Cursor or VS Code

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

claude mcp add mcp-stone -- npx -y @codespar/mcp-stone

Add to Cursor

What the publisher says

From the Stone 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.

Stone: common questions

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