Home / MCP registry index / io.github.mcp-dir/stone_vendas-mcp
Stone Vendas
io.github.mcp-dir/stone_vendas-mcp in the official MCP registry.
Endpoint https://api.mcp.ai/p_stone_vendas. Source: github.com/mcp-dir/stone_vendas-mcp.
The registry describes it as: Stone acquirer (card machine) sales via the Conciliação API, read-only. Lists transactions for a per
We read its 15 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
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 stone_vendas_arquivo show_version report_bug connect toolkit_info marketplace authenticate
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-stone-vendas-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.