Skip to main content
Glama
Brazil CNPJ Company Data MCP Server

Brazil CNPJ Company Data MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesYour 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count3/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues