MCP Brasil
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port used when `MCP_TRANSPORT=http`. | 3000 |
| LOG_LEVEL | No | `debug`, `info`, `warn` or `error`. Logs always go to stderr. | info |
| MCP_TRANSPORT | No | `stdio` or `http`. | stdio |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validar_documentoA | Valida um CPF ou CNPJ brasileiro (dígitos verificadores) e retorna o documento formatado. Detecta automaticamente o tipo pelo número de dígitos. Funciona totalmente offline, sem consultar APIs externas. Use quando precisar checar se um número de documento informado pelo usuário é válido antes de prosseguir com um cadastro. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of overlap or misselection. Its purpose (validate a CPF/CNPJ and return it formatted) is unambiguous and clearly stated.
The single name 'validar_documento' uses a clean snake_case verb_noun pattern in Portuguese and there are no competing conventions to conflict with it. Consistency is trivially satisfied.
A server named 'MCP Brasil' implies a broader suite of Brazilian utilities (CEP lookup, phone/currency formatting, state data, etc.), so a single validation tool is far too thin for the apparent scope. The tool itself is well-sized, but the surface overall is under-built.
For the narrow stated purpose of checking document validity before a cadastro, CPF and CNPJ are both covered with a self-contained offline implementation. Only minor adjacent operations are missing, such as format-only or generate-valid-document helpers.