Stone Vendas MCP server
Stone acquirer (card machine) sales via the Conciliação API, read-only. Lists transactions for a per.
source repositorytool list publishedupdated recentlyhosted endpointactive entryno credentials
HostedCOMMUNITY Other
Details
- Registry name
- io.github.mcp-dir/stone_vendas-mcp
- Publisher
- mcp-dir
- Version
- 0.1.1
- Distribution
- Hosted. the publisher runs this server and your client connects to their URL over HTTP. Nothing to install, but your requests go to a third party.
- Transports
- streamable-http
- Source repository
- mcp-dir/stone_vendas-mcp
- Website
- -
- First published
- Registry updated
- Credentials required
- -
- Schema generation
- 2025-12-11
Hosted endpoints
Endpoint 1
- URL
- https://api.mcp.ai/p_stone_vendas
- Transport
- streamable-http
- Authentication
- not declared
Install Stone Vendas
Pick your client. The configuration below is generated from this server's published package and endpoint data.
Claude Code command line
Configuration file: .mcp.json or ~/.claude.json
claude mcp add stone-vendas --transport http https://api.mcp.ai/p_stone_vendasNothing to install. The client connects to the publisher's URL.
Check it worked: Run claude mcp list and check the server reports connected.
Cursor IDE
Configuration file: .cursor/mcp.json or ~/.cursor/mcp.json
{
"mcpServers": {
"stone-vendas": {
"type": "http",
"url": "https://api.mcp.ai/p_stone_vendas"
}
}
}Nothing to install. The client connects to the publisher's URL.
Check it worked: The server appears under Settings, then MCP with a green dot.
Claude Desktop desktop app
Configuration file: ~/Library/Application Support/Claude/claude_desktop_config.json or %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"stone-vendas": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.mcp.ai/p_stone_vendas"]
}
}
}Nothing to install. The client connects to the publisher's URL.
Quit the app completely and reopen it.
Check it worked: Look for the tools icon in the message composer.
Visual Studio Code IDE
Configuration file: .vscode/mcp.json or user settings.json under mcp
{
"servers": {
"stone-vendas": {
"type": "http",
"url": "https://api.mcp.ai/p_stone_vendas"
}
}
}Nothing to install. The client connects to the publisher's URL.
Check it worked: Open the Copilot chat tools picker and confirm the server is listed.
Codex CLI command line
Configuration file: ~/.codex/config.toml
codex mcp add stone-vendas --transport http https://api.mcp.ai/p_stone_vendasNothing to install. The client connects to the publisher's URL.
Check it worked: Run codex mcp list and check the server is present.
More clients (9), including automation platforms
ChatGPT web app
This client does not support the transport this server offers.
Cline IDE
Configuration file: cline_mcp_settings.json, reachable from the MCP Servers pane
{
"mcpServers": {
"stone-vendas": {
"type": "streamableHttp",
"url": "https://api.mcp.ai/p_stone_vendas"
}
}
}Nothing to install. The client connects to the publisher's URL.
Check it worked: The server appears in the MCP Servers pane with its tool count.
Goose desktop app
Configuration file: ~/.config/goose/config.yaml
extensions:
stone-vendas:
type: streamable_http
uri: https://api.mcp.ai/p_stone_vendas
enabled: trueNothing to install. The client connects to the publisher's URL.
Check it worked: Run goose session and confirm the extension loads.
LangChain agent framework
Install the MCP adapter package and construct a client in code
client = MultiServerMCPClient({
"stone-vendas": {
"url": "https://api.mcp.ai/p_stone_vendas",
"transport": "streamable_http",
}
})Nothing to install. The client connects to the publisher's URL.
Check it worked: Print the loaded tool list before running the agent.
Make automation platform
This client does not support the transport this server offers.
n8n automation platform
This client does not support the transport this server offers.
Windsurf IDE
Configuration file: ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"stone-vendas": {
"serverUrl": "https://api.mcp.ai/p_stone_vendas"
}
}
}Nothing to install. The client connects to the publisher's URL.
Check it worked: The server appears in the Cascade plugin list.
Zapier automation platform
This client does not support the transport this server offers.
Zed IDE
This client does not support the transport this server offers.
Tools
15 tools, from the publisher's manifest. A parameter marked with an asterisk is required. By intent: 4 answer, 1 act and 10 not classified.
Intent says what a tool does with the world. Answer reads and returns information and changes nothing. Act changes state somewhere, by writing, creating, sending or deleting. Transact moves money, buys something or commits to a cost. A value marked declared is the publisher's own annotation on their own tool. A value marked inferred is this catalogue reading the tool name and description, and is not a claim by the publisher. Where neither settles it, the tool is left unclassified rather than guessed at.
| Tool | What it does | Intent | Parameters |
|---|---|---|---|
| stone_vendas_contas | Lista os StoneCodes (estabelecimentos) Stone conectados neste install, com id e apelido. | not classified | account |
| 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. | not classified | limite, status, account, bandeira, data_fim, data_inicio, forma_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. | not classified | account, data_fim, agrupar_por, data_inicio, incluir_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. | not classified | account, data_fim, data_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. | not classified | account, data_fim, data_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. | not classified | account, data_fim, data_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. | not classified | limite, status, account, data_fim, data_inicio, apenas_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. | not classified | account, data_fim, data_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. | not classified | data, account |
| show_version | Show the current MCP platform and adapter versions. | answer inferred | none |
| report_bug | Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction. | answer inferred | context, message, conversation |
| 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. | answer inferred | none |
| 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. | answer inferred | none |
| 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. | not classified | limit, query, action, mcp_id, message, tool_id, arguments, immediate |
| 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. | act inferred | token |
Command line alternative
Could not determine. The available signals were not conclusive enough to say either way, so this is left open rather than guessed.
Repository signals
Not checked yet. Stars, licence, language and last commit date are read from the source host, and that pass has not run against this record.
Security, privacy and enterprise use
The publisher has not published a website, so there is no site to read policies from. For a server distributed only as source, the repository is the place to look.
Publisher
The publisher has not disclosed a website in their registry entry, so there is nothing to read a profile from.
Frequently asked questions
- What does the Stone Vendas MCP server do?
- Stone acquirer (card machine) sales via the Conciliação API, read-only. Lists transactions for a per.
- Do I need to install anything to use Stone Vendas?
- No. Stone Vendas is published as a hosted endpoint, so a compatible client connects to it over the network.
- How do I install Stone Vendas?
- Point your client at the hosted endpoint https://api.mcp.ai/p_stone_vendas. No local install is needed.
- Which transport does Stone Vendas use?
- Streamable http. Your client has to support that transport to connect.
- Where is the source code for Stone Vendas?
- The publisher lists https://github.com/mcp-dir/stone_vendas-mcp as the source repository.
- Who publishes Stone Vendas?
- It is published under io.github.mcp-dir, a community namespace tied to the GitHub account mcp-dir. Community servers are not reviewed before they appear in the registry.
- Which version of Stone Vendas is listed here?
- Version 0.1.1, taken from the latest registry entry.
Other servers in Other
航班管家航空数据 MCP | Flight Master Aviation Data MCP
航班管家 DAST 官方航空数据 MCP，支持 Remote HTTP 与 npm STDIO，提供航班动态、天气、轨迹及延误风险。Official Flight Master MCP.Kin
The system of record for AI-written software.Inite Diagnostic
Takes a business process apart and says what to automate first. Eight questions free, 43 paid.ApyHub Utility Tools (EU)
GDPR-compliant ApyHub utility APIs hosted in the EU. Requires an EU-generated ApyHub API key.Federal Grant Evidence
Find U.S. federal grants and return cited hard-gate and award-history evidence packs.SAP ABAP MCP
Develop, test, analyze, and operate SAP ABAP systems through ADT from AI coding agents.Crossave import duty & VAT
EU import duty & VAT calculator (rules since 1 July 2026), real shop origins and shipping rates.ToolsMonk tool catalog
Find the right ToolsMonk tool for a task: 255 free browser-based tools, read-only lookups.