Brazil CNPJ Company Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
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 |
|---|---|
| lookup_brazil_cnpjA | Look up Brazilian companies by CNPJ in the Receita Federal open data. Returns one row per company with legal and trade name, registration status, legal nature, size, share capital, main and secondary CNAE activities, address, phones, email, Simples and MEI options, and tax regime; with partners on, one row per partner or administrator (QSA). |
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
There is only one tool, so no misselection between tools is possible. Its purpose (CNPJ lookup against Receita Federal open data) is explicitly and narrowly stated.
The single name lookup_brazil_cnpj follows a clean verb_noun snake_case pattern. With only one tool, a consistent convention can be suggested but not demonstrated across the set.
The server is scoped to one narrow operation, but a single tool is thin even for that purpose — no batch lookup, name search, or CNAE query tool accompanies it. Borderline under-provisioned rather than clearly wrong.
The returned payload is very rich (address, CNAE, Simples/MEI, QSA partners), but the surface requires a known CNPJ, so an agent that only has a company name, state, or activity code hits a dead end. Search/filter operations are a notable gap.