Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

BrazilMCP

REMOTE · API.BRAZILMCP.DEV · SCANNED AUG 3

Brazilian company data (CNPJ): registry lookup, sanctions screening and KYB dossier, paid via x402

+59 this week 62 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2246 tokens (~449/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.brazilmcp.dev

# add to Claude Code
claude mcp add --transport http dev-brazilmcp-brazilmcp https://api.brazilmcp.dev/mcp
# ~/.codex/config.toml
[mcp_servers.dev-brazilmcp-brazilmcp]
url = "https://api.brazilmcp.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-brazilmcp-brazilmcp": {
      "type": "remote",
      "url": "https://api.brazilmcp.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-brazilmcp-brazilmcp --url https://api.brazilmcp.dev/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-brazilmcp-brazilmcp:
    url: "https://api.brazilmcp.dev/mcp"
// mcp.json
{
  "mcpServers": {
    "dev-brazilmcp-brazilmcp": {
      "type": "http",
      "url": "https://api.brazilmcp.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +46
    • Transport: fail → pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
  • 29 Jul 26 +11
    • HSTS header: unverified → fail security
    • TLS certificate: unverified → pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. security
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 3

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://api.brazilmcp.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.brazilmcp.dev CN=YE1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 66839901ed381b407bd85f85d9a8e4b3d2f
SANs: api.brazilmcp.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of api.brazilmcp.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
brazilmcp.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.brazilmcp.dev/mcp Verified 200
http (plaintext) http://api.brazilmcp.dev/mcp HTTPS enforced 308 https://api.brazilmcp.dev/mcp
MCP tools — 5 exposed · ~1,399 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
company_debts ~288

Check a Brazilian company for federal tax debt by CNPJ (the 14-digit Brazilian company tax ID, punctuation optional). Returns the company's registered federal debt (Dívida Ativa da União) as published quarterly by the PGFN, Brazil's federal treasury attorney general: number of inscriptions, consolidated amount in BRL, how many are under judicial enforcement, how many are in installment plans or renegotiated, the oldest and newest inscription dates, and a breakdown by type — non-social-security, social security contributions and FGTS (severance fund). Debt is aggregated across every establishment of the company, so querying a branch still surfaces debt registered against headquarters. Tax delinquency is the first question in Brazilian due diligence and is not part of the company registry: it is a separate federal dataset. Useful for KYB, credit and counterparty risk, supplier onboarding and financial health checks. Consolidated amounts are the registered stock and include suspended, renegotiated and installment-plan inscriptions — the response carries counters and a disclaimer so the number is never read as immediately enforceable debt. Federal scope only: state (ICMS) and municipal (ISS) debts are not covered. A CNPJ with no debt returns result_status "no_debt"; one absent from the registry returns "not_found".

NameTypeReqDescription
querystringyesA CNPJ (14-digit Brazilian company tax ID, punctuation optional)

No output schema declared.

No examples provided.

company_dossier ~267

Build an aggregated due-diligence dossier on a Brazilian company by CNPJ (the 14-digit Brazilian company tax ID, punctuation optional). One call aggregates multiple official government sources into a single structured report: full registry record from Receita Federal (status, legal name, activities, address, partners/QSA); public procurement contracts from PNCP (Brazil's national procurement portal); the corporate group ownership graph (company-to-company shareholders and subsidiaries); registered federal tax debt from the PGFN Dívida Ativa da União, including social security and FGTS, aggregated across every establishment of the company; sanctions screening across 5 federal lists (CEIS, CNEP, CEPIM, leniency agreements and the MTE forced-labor register); and derived compliance risk flags (inactive company, active sanction, federal tax debt, recently opened). Sections are independent and degrade gracefully: if a source is down its section is marked unavailable, never a total error. Replaces an analyst-hour of manual checks across Brazilian government portals. Useful for KYB (know your business), vendor and supplier due diligence, counterparty risk, credit analysis, AML/compliance screening, and M&A research on companies in Brazil.

NameTypeReqDescription
querystringyesA CNPJ (14-digit Brazilian company tax ID, punctuation optional)

No output schema declared.

No examples provided.

company_group ~271

Map the corporate group (economic group) of a Brazilian company by CNPJ (the 14-digit Brazilian company tax ID, punctuation optional). Answers what a standard registry lookup cannot: not just who the corporate shareholders of this company are, but its subsidiaries (the companies it holds), the parent companies above those shareholders, the sibling companies under the same parent, and the ultimate parent at the top of the ownership chain. Returns exact counts plus the nodes themselves — each with legal name, registration status, company size and state — so no follow-up lookups are needed. Consortium relationships ("Sociedade Consorciada", an alliance for a single contract) are reported separately and never counted as control. Built from the Receita Federal partner registry (QSA), rebuilt monthly. Company-to-company shareholding only: natural-person partners are never used to link companies and never appear in the response. Ownership percentages are not published by the source. Useful for KYB (know your business), AML and sanctions exposure through affiliates, counterparty and concentration risk, M&A research and supplier due diligence in Brazil. Companies with no corporate shareholder return result_status "no_group" — common for micro companies, expected for mid-size and large ones.

NameTypeReqDescription
querystringyesA CNPJ (14-digit Brazilian company tax ID, punctuation optional)

No output schema declared.

No examples provided.

company_lookup ~345

Look up a Brazilian company in the official government registry by CNPJ or company name. Returns the full registration record from the Receita Federal (Brazil's federal tax authority) CNPJ database: registration status (active, suspended, closed), legal name (razão social), trade name (nome fantasia), head office or branch, opening date, legal nature, company size, share capital, main and secondary economic activities (CNAE codes with descriptions), full address with IBGE city code, tax regime (Simples Nacional / MEI), and the partners and shareholders board (QSA) as registered. Input: a CNPJ — the 14-digit Brazilian company tax ID, punctuation optional — or a company name, resolved via full-text search over legal and trade names. A CNPJ that does not exist returns result_status "not_found". Useful for KYB (know your business), due diligence, supplier and vendor verification, credit analysis, B2B prospecting, and compliance checks on companies in Brazil. Registry data is refreshed monthly from official open data; the response carries its source reference date. The response also carries has_corporate_group: true when the company has corporate (PJ) shareholders or subsidiaries, i.e. when company_group would return an actual graph. Use this cheap call to qualify before spending on the more expensive one — only ~0.7% of Brazilian companies have a corporate shareholder (27-39% among those with share capital above R$ 1M). Null means the ownership graph is not loaded, never assume false.

NameTypeReqDescription
querystringyesA CNPJ (14-digit Brazilian company tax ID, punctuation optional) or a company name

No output schema declared.

No examples provided.

company_sanctions ~228

Screen a Brazilian company for sanctions and debarment by CNPJ (the 14-digit Brazilian company tax ID, punctuation optional). One call checks 5 federal sanction lists: CEIS (companies debarred from public contracting), CNEP (penalties under the anti-corruption law), CEPIM (non-profits barred from federal agreements), Acordos de Leniência (leniency agreements with enforcement status) and the MTE forced-labor employers register ("Lista Suja" do trabalho escravo). Returns each matching entry with list, sanction type, sanctioning body and validity dates, plus an is_currently_sanctioned verdict, the lists checked and any list that was unavailable — sources and reference dates declared. The Brazilian complement that global OFAC/EU/UK/UN and PEP screens miss. Useful for KYB (know your business), AML/compliance screening, supplier and vendor onboarding, procurement eligibility checks and counterparty risk on companies in Brazil.

NameTypeReqDescription
querystringyesA CNPJ (14-digit Brazilian company tax ID, punctuation optional)

No output schema declared.

No examples provided.