ViaCEP Brasil MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getAddressByCEPA | Fetches a Brazilian address using a postal code (CEP). |
| getCEPByAddressA | Fetches a list of CEPs based on a Brazilian address. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ViaCEP README | Documentation for the ViaCEP MCP Server |
TDQS
Scored across 2 tools
The two tools perform reverse operations—one returns an address for a given CEP, the other returns CEPs for a given address. Their purposes are clearly distinct with no overlap.
Both tools follow a consistent 'get<Target>By<Query>' pattern, e.g., 'getAddressByCEP' and 'getCEPByAddress'. The naming is symmetric and predictable.
With exactly two tools, the set is minimal and perfectly scoped for bidirectional CEP-address lookup. Each tool provides a distinct, necessary function without redundancy.
The pair covers both directions of the CEP-address mapping, which is the complete domain for a ViaCEP service. No obvious missing operations.