Ozav MCP Server

If you already use Ozav, the ozav mcp server is the piece that lets your assistant work with it directly. Forex, IOF tax, US accounts, stablecoins, and international payments in Brazil.

What the server does

Servidor MCP publico que conecta IAs a 55 categorias de conhecimento sobre cambio, IOF, contas nos EUA, stablecoins, cartoes internacionais, pagamentos B2B, M&A, franquias, esports, healthtech, cybersecurity e 40+ outros setores no Brasil.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Stack — ** TypeScript + Hono + @modelcontextprotocol/sdk
• Transport — ** Streamable HTTP (stateless)
• Deploy — ** Vercel (serverless)
• Auth — ** Nenhuma (conteudo publico)
• Latencia — ** <100ms por request
• Website — ** ozav.com.br
• Resource — Tema
• Prompt — Descricao
• ozav_consulta_cambio — Template para consulta sobre operacao de cambio
• ozav_comparativo — Template para comparar OZAV com concorrentes
• ozav_simulacao — Template para simular economia com vs sem OZAV
• Cursor — Settings → MCP Servers → Add: json { "mcpServers": { "ozav": { "url": "https://mcp.ozav.com.br/mcp" } } }

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Ozav's toolset — Stack, Transport, Deploy and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ElToro1855; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Ozav's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ozav.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.