Brazilian CEP MCP
Related Servers
Alternatives to Brazilian CEP MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides a tool to query Brazilian postal codes (CEPs) via the ViaCEP API, returning address details such as street, neighborhood, city, and state.-
- AlicenseNot gradedqualityCmaintenanceMCP server for querying Brazilian postal codes (CEP) and territorial areas using official Correios data, providing a read-only tool to complete CEP information.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for querying Brazilian postal codes (CEP) from the official Correios source, supporting read-only lookups via natural language in any MCP-compatible client.MIT
- FlicenseNot gradedqualityDmaintenanceEnables lookup of Brazilian addresses by CEP (postal code) using the ViaCEP API, returning formatted address information including street, neighborhood, city, and state.1-
- AlicenseAqualityDmaintenanceProvides tools to query Brazilian CNPJ (company registration), CEP (postal codes), and currency exchange rates (USD and EUR) through an MCP server.3MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Brazilian data lookups (Pix codes, CEP, CNPJ) and web rendering tasks (Markdown, screenshots, PDFs) via a paid HTTP API with x402 billing.43 npm1MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and singular.
Since there is only one tool, naming consistency is inherently perfect, as there are no other tool names to compare it against for patterns or conventions.
A single tool for a CEP lookup server feels thin and under-scoped, as it only provides query functionality without supporting related operations like validation, batch processing, or reverse lookup. This limits the server's utility for broader agent workflows.
The server is severely incomplete for a CEP domain, as it only offers a query tool without any complementary operations such as address validation, error handling for invalid CEPs, or integration with other Brazilian address services, leaving significant gaps in functionality.