brasil-data-mcp
Related Servers
Alternatives to brasil-data-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP Server for accessing 36 Brazilian public data sources and 1 agent, enabling AI agents to query government data on economy, legislation, transparency, judiciary, elections, environment, health, and more.6MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects AI agents to 28 Brazilian public APIs, providing tools to query government data on economy, legislation, transparency, judiciary, elections, environment, health, and more.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for consulting official ANTT transport data in read-only mode via a hosted HTTP endpoint. Works with any MCP-compatible client, including Claude, ChatGPT, and Cursor.MIT
- FlicenseNot gradedqualityBmaintenanceSelf-hosted MCP connector for querying Brazilian legal jurisprudence via JurisprudenciaIA. Enables natural language legal research using Claude.ai, with tools for consulting, searching, and comparing jurisprudence and legal theses.14-
- AlicenseNot gradedqualityCmaintenanceEnables read-only queries to official CVM (Brazilian Securities Commission) administrative sanctioning procedures via a paid, hosted MCP server. Works with any MCP-over-HTTP client like Claude, Cursor, and VS Code.MIT
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server for connecting to Pluggy Open Finance Brasil, exposing accounts, balances, transactions, and investments to Claude agents.-
TDQS
Scored across 15 tools
Each tool targets a distinct Brazilian data resource (CNPJ, CEP, banks, holidays, DDD, ISBN, taxes, brokers, FX, states, municipalities, .br domains), and the descriptions explicitly state what each tool should not be used for. Even the companion list/consult tools (e.g., listar_bancos vs consultar_banco) have clear boundaries.
All tools follow a consistent Portuguese snake_case pattern: consultar_ for lookup-by-identifier and listar_ for fetching full collections. There is no mixing of conventions or vague verbs.
At 15 tools, the server is at the upper edge of the ideal range but each tool maps to a distinct BrasilAPI endpoint and earns its place. The consult/list pairs (bancos, taxas, moedas) are justified by different query needs rather than redundancy.
The server covers a broad and practical range of Brazilian public data queries, with sensible consult/list pairs and clearly documented read-only behavior. Obvious gaps include FIPE vehicle prices, demographic/census data, and inverse lookups (address to CEP, city to DDD), but these appear to be external API limitations rather than broken workflows.