Stone Vendas

io.github.mcp-dirPublished by GitHub account mcp-dirv0.1.1Updated Nov 2, 2026

Stone acquirer (card machine) sales via the Conciliação API, read-only. Lists transactions for a per

VerifiedStreamable HTTPWeb executableFinanceData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Read-only access to Stone acquirer (card machine) sales data: transactions, summaries, chargebacks, receivables, settlements and Pix, for a chosen period.

What you can do
  • List connected Stone establishments (StoneCodes) with id and nickname
  • List captured transactions for a period with date, gross and net amounts, payment method, brand, capture type, installments and status
  • Get consolidated totals grouped by payment method, brand, day, status, capture type or terminal
  • Retrieve cancellations, chargebacks and chargeback re-presentments, plus the receivables schedule and settlements deposited to the bank account
  • Retrieve Pix sales on the card machine, and the full one-day reconciliation file converted from XML to JSON
  • Force Stone to regenerate a period's reconciliation file, and check platform versions, connection status, toolkit state and the marketplace
When to use it
Useful when you want an assistant to answer questions about Stone card-machine sales — monthly summaries by payment method, sales by card brand, expected receivables, chargebacks or Pix volume — without exporting reports by hand. It is read-only, so it suits reporting and reconciliation rather than changing anything in the account.
Requirements
A remote MCP endpoint over HTTP; no local package is needed. Authentication uses the key the account holder creates in the Stone portal under authentication keys, and each StoneCode is a separate connection. A client that speaks MCP over HTTP (Claude, ChatGPT, Cursor, VS Code and others) is required.
Before you install
The Stone authentication key is a credential for the account's sales data. Returned data, including truncated card numbers and Pix payer details, is sent to the LLM host you choose, which the README names as a sub-processor outside the provider's control. The cache-clearing tool discards Stone's cached reconciliation report and consumes the same request quota. Pricing is documented separately; check it before relying on the service.

Installation

In SourceWeft

  1. Open Stone Vendas in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mcp-dir%2Fstone_vendas-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "stone-vendas": {
      "type": "http",
      "url": "https://api.mcp.ai/p_stone_vendas"
    }
  }
}

README

Stone Vendas

Stone Vendas for Claude, ChatGPT and AI agents

Stone acquirer (card machine) sales via the Conciliação API, read-only. Lists transactions for a period with date and time, gross and net amounts, payment method, card brand, capture type, installments and status, and consolidates totals by payment method, brand or day. Also covers cancellations, chargebacks, the receivables schedule and the settlements deposited into the account. Each StoneCode is one connection, and the same key works for every StoneCode under the same tax id. Auth uses the key the account holder creates in the Stone portal, under authentication keys. Complements Stone Pagamentos, which reads the bank account through Open Finance.

  • 📊 9 tools
  • 🔒 Read-only
  • 💬 Works with any MCP client: Claude Desktop, Cursor, VS Code, Cline, Continue
  • 🔑 Magic-link login (no password)

Versão em português · Full docs (PT-BR) · Agent skill


One-click install

Claude (Web and Desktop)

Anthropic unified MCP installation at claude.ai/customize/connectors. The same link works for Claude Web and Claude Desktop (just be logged in):

➕ Open in Claude and connect

Manual (if the deeplink does not open): claude.ai/customize/connectors → + → Add custom connector → paste Name Stone Vendas and URL https://api.mcp.ai/p_stone_vendas.

Cursor

➕ Install Stone Vendas in Cursor

VS Code (Copilot Chat)

➕ Install Stone Vendas in VS Code

ChatGPT, Manus, OpenClaw and 40+ other clients

Works with any MCP client that speaks MCP over HTTP. The server URL is always:

https://api.mcp.ai/p_stone_vendas

Per-client details: INSTALL.md.


Example prompts

What was the Stone sales summary last month by payment method?List last week's Stone sales by card brandHow much am I due to receive from Stone in the coming days?Were there any chargebacks or cancellations on Stone this month?How much came in through Pix on the Stone card machine last week?

9 tools available

ToolDescription
stone_vendas_contasLista os StoneCodes (estabelecimentos) Stone conectados neste install, com id e apelido.
stone_vendas_listarLista as vendas do adquirente Stone no período, uma linha por transação capturada, com data e hora, valor bruto e líquido, forma de pagamento (crédito, débito, pré-pago, voucher, boleto), bandeira, cartão truncado, ti…
stone_vendas_resumoTotais consolidados das vendas Stone no período, o equivalente ao Resumo de vendas do painel.
stone_vendas_cancelamentosCancelamentos, chargebacks e reapresentações de chargeback da conta Stone no período, com o NSU da venda de origem, valor, datas e motivo.
stone_vendas_recebiveisAgenda de recebíveis Stone: as parcelas ainda não pagas com a data prevista de pagamento, detalhadas e totalizadas por data.
stone_vendas_liquidacoesLiquidações da Stone no período, o que foi efetivamente depositado, com valor total e a conta bancária favorecida.
stone_vendas_pixVendas por Pix na maquininha Stone no período, com data e hora, valor, taxa, status (paga ou cancelada), terminal, chave Pix, e2e id e dados do pagador.
stone_vendas_limpar_cacheForça a Stone a regerar o arquivo de conciliação do período, descartando o extrato que ela mantém em cache.
stone_vendas_arquivoArquivo de conciliação completo de um único dia, já convertido de XML para JSON, com todos os blocos (vendas, liquidações na conta, agenda prevista, eventos financeiros, pagamentos e posição de carteira).

Details for each tool: docs/ferramentas.md (PT-BR)


Pricing

See docs/precos.md (PT-BR).


Privacy & data protection

  • Read-only, no tool changes data at the source.
  • Sub-processors: Stone, the LLM host you choose (Claude, ChatGPT, Cursor, your own agent). Full list in docs/privacidade-lgpd.md.
  • Data returned by the tools is sent to the LLM host you choose, a sub-processor outside our control. We recommend plans with training opt-out.

FAQ

Is the server open source? The server is proprietary (hosted). This repository is the public wrapper with manifests, docs and skills, all MIT.

Can I use it with my own agent (not Claude/Cursor)? Yes, any client that speaks MCP over HTTP. URL: https://api.mcp.ai/p_stone_vendas.


Support


License

MIT — see LICENSE. The MCP server at api.mcp.ai/p_stone_vendas is proprietary (hosted); this repo (manifests, docs, skills) is MIT.

Source: README.md at commit 45ea1b4

Tools

15

stone_vendas_contas

Lista os StoneCodes (estabelecimentos) Stone conectados neste install, com id e apelido.

Parametersaccount

stone_vendas_listar

Lista as vendas do adquirente Stone no período, uma linha por transação capturada, com data e hora, valor bruto e líquido, forma de pagamento (crédito, débito, pré-pago, voucher, boleto), bandeira, cartão truncado, tipo de captura (POS, e-commerce, TEF), parcelas e status (aprovada, cancelada, contestada, liquidada). A Stone fecha um arquivo por dia e o do dia só fica pronto depois das 5h do dia seguinte, então o padrão vai até ontem. Máximo de 92 dias por chamada.

Parameterslimitestatusaccountbandeiradata_fimdata_inicioforma_pagamento

stone_vendas_resumo

Totais consolidados das vendas Stone no período, o equivalente ao Resumo de vendas do painel. Agrupa por forma de pagamento, bandeira, dia, status, tipo de captura ou terminal, e devolve quantidade, valor bruto, valor líquido, cancelado e chargebacks de cada grupo. Inclui crédito, débito, pré-pago, voucher, boleto e também o Pix na maquininha. A Stone fecha um arquivo por dia e o do dia só fica pronto depois das 5h do dia seguinte, então o padrão vai até ontem. Máximo de 92 dias por chamada.

Parametersaccountdata_fimagrupar_pordata_inicioincluir_pix

stone_vendas_cancelamentos

Cancelamentos, chargebacks e reapresentações de chargeback da conta Stone no período, com o NSU da venda de origem, valor, datas e motivo. A Stone fecha um arquivo por dia e o do dia só fica pronto depois das 5h do dia seguinte, então o padrão vai até ontem. Máximo de 92 dias por chamada.

Parametersaccountdata_fimdata_inicio

stone_vendas_recebiveis

Agenda de recebíveis Stone: as parcelas ainda não pagas com a data prevista de pagamento, detalhadas e totalizadas por data. A Stone fecha um arquivo por dia e o do dia só fica pronto depois das 5h do dia seguinte, então o padrão vai até ontem. Máximo de 92 dias por chamada.

Parametersaccountdata_fimdata_inicio

stone_vendas_liquidacoes

Liquidações da Stone no período, o que foi efetivamente depositado, com valor total e a conta bancária favorecida. É a ponta que fecha com o extrato bancário. A Stone fecha um arquivo por dia e o do dia só fica pronto depois das 5h do dia seguinte, então o padrão vai até ontem. Máximo de 92 dias por chamada.

Parametersaccountdata_fimdata_inicio

stone_vendas_pix

Vendas por Pix na maquininha Stone no período, com data e hora, valor, taxa, status (paga ou cancelada), terminal, chave Pix, e2e id e dados do pagador. A Stone entrega o Pix num arquivo separado e assíncrono, por CNPJ, então esta tool pede os arquivos que faltam e devolve os que já ficaram prontos, listando em dias_pendentes o que ainda está processando (pode levar até 30 minutos). Se houver dias pendentes, chame de novo mais tarde para completar o período. Exige o campo Documento preenchido na conexão. Máximo de 31 dias por chamada.

Parameterslimitestatusaccountdata_fimdata_inicioapenas_maquininha

stone_vendas_limpar_cache

Força a Stone a regerar o arquivo de conciliação do período, descartando o extrato que ela mantém em cache. Use quando os números não baterem com o painel da Stone. Não altera nada da conta, não move dinheiro e não mexe em venda, só descarta o cache de um relatório. Consome a mesma cota de 7 requisições por hora por dia, então não repita em sequência.

Parametersaccountdata_fimdata_inicio

stone_vendas_arquivo

Arquivo de conciliação completo de um único dia, já convertido de XML para JSON, com todos os blocos (vendas, liquidações na conta, agenda prevista, eventos financeiros, pagamentos e posição de carteira). Use quando as tools de período não cobrirem o campo que você precisa.

Parametersdatarequiredaccount

show_version

Show Version

Show the current MCP platform and adapter versions.

Takes no parameters.

report_bug

Report Bug

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

Parameterscontextmessagerequiredconversation

connect

Connection Status

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.

Takes no parameters.

toolkit_info

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.

Takes no parameters.

marketplace

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.

Parameterslimitqueryactionmcp_idmessagetool_idargumentsimmediatetier_slugprompt_bodyprompt_slugprompt_tool+11 more

authenticate

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.

Parameterstoken

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts