Stone Vendas MCP server
io.github.mcp-dir/stone_vendas-mcpmcp-dirstreamable-httpv0.1.1Scanned
Stone acquirer (card machine) sales via the Conciliação API, read-only. Lists transactions for a per
15 tools: 12 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
12 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Stone Vendas MCP server can do
The Stone Vendas MCP server is published by the GitHub account mcp-dir. It has 15 tools. It can create or change data (12 tools: stone_vendas_contas, stone_vendas_listar, stone_vendas_resumo, stone_vendas_cancelamentos and 8 more), but cannot delete data. 3 tools only read.
1 tool brings in text other people can write (marketplace).
The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 0.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Changes things 12Claude Code: ask
authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Authenticate
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them.Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...ating the tool list. If the MCP needs a credential/login, invoke returns a connect link; i..."
Description, as the server wrote it 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.
Annotations the server declares
- title: Marketplace
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
report_bugReport a bug, missing feature, or send feedback.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Annotations the server declares
- title: Report Bug
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: stone_vendas_arquivo
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: stone_vendas_cancelamentos
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
stone_vendas_contasLista os StoneCodes (estabelecimentos) Stone conectados neste install, com id e apelido.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Lista os StoneCodes (estabelecimentos) Stone conectados neste install, com id e apelido.
Annotations the server declares
- title: stone_vendas_contas
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: stone_vendas_limpar_cache
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
stone_vendas_liquidacoesLiquidações da Stone no período, o que foi efetivamente depositado, com valor total e a conta bancária favorecida.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: stone_vendas_liquidacoes
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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, b…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: stone_vendas_listar
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: stone_vendas_pix
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
stone_vendas_recebiveisAgenda de recebíveis Stone: as parcelas ainda não pagas com a data prevista de pagamento, detalhadas e totalizadas por data.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: stone_vendas_recebiveis
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
stone_vendas_resumoTotais consolidados das vendas Stone no período, o equivalente ao Resumo de vendas do painel.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: stone_vendas_resumo
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
connectReturns connection status and URLs.1 finding
Why it is in this group
- The description's first verb is "return": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...nticated:true and empty pending[]. When credentials are missing, returns connect_url for th..."
Description, as the server wrote it 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.
Annotations the server declares
- title: Connection Status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
show_versionShow the current MCP platform and adapter versions.No findings
Why it is in this group
- The name "show_version" says "show": a word for reading.
Description, as the server wrote it Show the current MCP platform and adapter versions.
Annotations the server declares
- title: Show Version
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Annotations the server declares
- title: Toolkit Info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:43 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 12
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 12 tools that change things (12 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.mcp.ai/p_stone_vendas: tools/list returned 15 tools to an anonymous client, including stone_vendas_contas (write), stone_vendas_listar (write), stone_vendas_resumo (write), stone_vendas_cancelamentos (write), stone_vendas_recebiveis (write) and 7 more
Findings
Matches of fixed checks, with the text they matched.
- Infoconnect
The description mentions "credentials".
What this check looks forMatched text
description: "...nticated:true and empty pending[]. When credentials are missing, returns connect_url for th..."
- Infomarketplace
The description mentions "credential".
What this check looks forMatched text
description: "...ating the tool list. If the MCP needs a credential/login, invoke returns a connect link; i..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http stone_vendas https://api.mcp.ai/p_stone_vendasclaude mcp add --transport http stone_vendas https://api.mcp.ai/p_stone_vendasRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__stone_vendas__show_version",
"mcp__stone_vendas__connect",
"mcp__stone_vendas__toolkit_info"
],
"ask": [
"mcp__stone_vendas__stone_vendas_contas",
"mcp__stone_vendas__stone_vendas_listar",
"mcp__stone_vendas__stone_vendas_resumo",
"mcp__stone_vendas__stone_vendas_cancelamentos",
"mcp__stone_vendas__stone_vendas_recebiveis",
"mcp__stone_vendas__stone_vendas_liquidacoes",
"mcp__stone_vendas__stone_vendas_pix",
"mcp__stone_vendas__stone_vendas_limpar_cache",
"mcp__stone_vendas__stone_vendas_arquivo",
"mcp__stone_vendas__report_bug",
"mcp__stone_vendas__marketplace",
"mcp__stone_vendas__authenticate"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as stone_vendas. Review it before you use it.
Capability tags behind 1 rule
- mcp__stone_vendas__marketplace untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.mcp-dir/stone_vendas-mcp/verify?hash=f2d91e8f14792d7579120afd4c32a8944fe465158dcbde5b197efbe5b93f3f17" | jq -e '.changed == false'Pinned hash f2d91e8f1479, from Nov 8, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.mcp-dir/stone_vendas-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.mcp-dir/stone_vendas-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:40 UTC.
Stone Vendas MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Stone Vendas MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 12 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Stone Vendas MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Stone Vendas MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Stone Vendas MCP server have?
- 15 tools: 12 write, 3 read. stone_vendas_contas, stone_vendas_listar, stone_vendas_resumo, stone_vendas_cancelamentos, stone_vendas_recebiveis, stone_vendas_liquidacoes, stone_vendas_pix, stone_vendas_limpar_cache and 7 more.
Does the Stone Vendas MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Stone Vendas MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Stone Vendas MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.