# Confere (Brasil) (remote · confere.guilherme-gaiga.workers.dev)

Check a Brazilian company registry record (CNPJ) before paying. Says what was not checked.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `confere.guilherme-gaiga.workers.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/guilherme-gaiga-confere/confere.md), [page](https://verifymcp.io/servers/guilherme-gaiga-confere/confere)

## Channel facts

- Endpoint: `https://confere.guilherme-gaiga.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 370 tokens (~370/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Confere (Brasil) MCP server?

Confere (Brasil) is a hosted endpoint at https://confere.guilherme-gaiga.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http guilherme-gaiga-confere 'https://confere.guilherme-gaiga.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "guilherme-gaiga-confere": {
      "url": "https://confere.guilherme-gaiga.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "guilherme-gaiga-confere": {
      "type": "http",
      "url": "https://confere.guilherme-gaiga.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.guilherme-gaiga-confere]
url = "https://confere.guilherme-gaiga.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "guilherme-gaiga-confere": {
      "type": "remote",
      "url": "https://confere.guilherme-gaiga.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add guilherme-gaiga-confere --url 'https://confere.guilherme-gaiga.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  guilherme-gaiga-confere:
    url: "https://confere.guilherme-gaiga.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "guilherme-gaiga-confere": {
      "Transport": "http",
      "Url": "https://confere.guilherme-gaiga.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add guilherme-gaiga-confere -t streamable-http -u 'https://confere.guilherme-gaiga.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "guilherme-gaiga-confere": {
      "type": "http",
      "url": "https://confere.guilherme-gaiga.workers.dev/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 68, +1)

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

### 2026-11-17 (score 67, +1)

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

### 2026-11-15 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.6.0 → 0.6.1

### 2026-11-14 (score 65)

First indexed and scored.

## MCP tools (1)

### `conferir_empresa` (~126 tokens)

Conferir empresa brasileira

Check a Brazilian company (CNPJ) before paying it: registration status at Receita Federal, company age and registered name. Does not compare the payee (the paid door does). Returns signals with their sources and lists what was not checked; it does not assert fraud. Website checks are not active in this version. Confere empresa (CNPJ) antes de um pagamento. Free, rate-limited.

Input parameters:

- `cnpj` (string): CNPJ of the Brazilian company, with or without punctuation (the alphanumeric format is accepted). CNPJ da empresa, com ou sem pontuação.

Output parameters:

- `ambiente` (string)
- `cnpj_consultado` (string): The CNPJ that was looked up, formatted. CNPJ consultado.
- `conferido` (array): What this lookup checked. O que foi conferido.
- `consultado_em` (string): Time of the lookup (ISO 8601, UTC).
- `empresa` (object): Public registry data of the company, present when the CNPJ was found.
- `leitura` (string): One sentence in Portuguese: the reading, what was checked and what was not. Pass it on. Uma frase com o alcance da conferência.
- `limites` (array): General limits of this check. Limites gerais desta checagem.
- `nao_conferido` (array): What this lookup did NOT check, and why. Tell the person. O que não foi conferido.
- `recebedor` (object): Comparison of the payee the bank shows with the registry. 'confere' does not prove who owns the account. Comparação do recebedor.
- `resumo` (string): Reading of what WAS checked: no alerts in the items checked, caution, alert, or not enough to check. A clean value never covers the items in `nao_conferido`. Leitura do que foi conferido.
- `sinais` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/guilherme-gaiga-confere/confere#diagnostics

## Score history

- 2026-11-21: 68
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 66
- 2026-11-15: 66
- 2026-11-14: 65

## Common questions

### What is the Confere (Brasil) MCP server?

Confere (Brasil) is an MCP server listed in the public MCP registry as io.github.guilherme-gaiga/confere. Check a Brazilian company registry record (CNPJ) before paying. Says what was not checked. This page covers its hosted endpoint (https://confere.guilherme-gaiga.workers.dev/mcp).

### Is the Confere (Brasil) MCP server safe to use?

Confere (Brasil) scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Confere (Brasil) MCP server expose?

Confere (Brasil) exposes 1 tool: conferir_empresa. Their descriptions and schemas cost roughly 126 tokens of context every time the server is loaded.

### Does the Confere (Brasil) MCP server require authentication?

No. We connected to Confere (Brasil) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Confere (Brasil) MCP server still maintained?

Confere (Brasil) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Confere (Brasil) MCP server?

VerifyMCP ran 12 checks on Confere (Brasil), covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Confere (Brasil): HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://confere.guilherme-gaiga.workers.dev/mcp
- Website: https://confere.guilherme-gaiga.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/guilherme-gaiga-confere/confere.xml
- Changelog JSON feed: https://verifymcp.io/servers/guilherme-gaiga-confere/confere/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/guilherme-gaiga-confere/confere.json
- HTML version of this page: https://verifymcp.io/servers/guilherme-gaiga-confere/confere
