# gov.br APIs MCP (pypi · govbr-apis-mcp)

A catalog-driven gateway over Brazilian government APIs, loading OpenAPI specs on demand.

- Trust score: 77/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- pypi · `govbr-apis-mcp`: 77/100 (this document), [markdown](https://verifymcp.io/servers/thalisantunes-govbr-apis-mcp/govbr-apis-mcp.md), [page](https://verifymcp.io/servers/thalisantunes-govbr-apis-mcp/govbr-apis-mcp)

## Channel facts

- Registry: `pypi`
- Package: `govbr-apis-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-06.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 33 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to thalisantunes/govbr-apis-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 17 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 614 tokens (~122/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the gov.br APIs MCP server?

gov.br APIs MCP runs locally as a PyPI package, launched with uvx govbr-apis-mcp. 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 thalisantunes-govbr-apis-mcp -- uvx govbr-apis-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "thalisantunes-govbr-apis-mcp": {
      "command": "uvx",
      "args": [
        "govbr-apis-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "thalisantunes-govbr-apis-mcp": {
      "command": "uvx",
      "args": [
        "govbr-apis-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add thalisantunes-govbr-apis-mcp -- uvx govbr-apis-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thalisantunes-govbr-apis-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "govbr-apis-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add thalisantunes-govbr-apis-mcp --command uvx --arg govbr-apis-mcp
```

### Hermes

```yaml
mcp_servers:
  thalisantunes-govbr-apis-mcp:
    command: "uvx"
    args: ["govbr-apis-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "thalisantunes-govbr-apis-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "govbr-apis-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add thalisantunes-govbr-apis-mcp -t stdio -c uvx -a govbr-apis-mcp
```

### Other

```json
{
  "mcpServers": {
    "thalisantunes-govbr-apis-mcp": {
      "command": "uvx",
      "args": [
        "govbr-apis-mcp"
      ]
    }
  }
}
```

## 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-10-20 (score 77, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-19 (score 62)

First indexed and scored.

## MCP tools (5)

### `search_catalog` (~93 tokens)

Search the government API catalog by keyword (accent-insensitive; matches
name, provider, tags and description).

category filters to: 'public' (free, callable today), 'meia-entrada'
(half-price ticket eligibility sources), 'serpro' (commercial, needs contract)
or 'conecta' (requires public-sector adhesion, not callable yet).

Input parameters:

- `category`
- `query` (string, required)

### `list_apis` (~97 tokens)

List catalog entries, most useful with a filter.

category: public | meia-entrada | serpro | conecta.
status: available | unstable | manual_only | requires_contract | requires_public_entity.
Note the catalog holds ~95 Conecta stubs that are not callable yet, so an
unfiltered listing is mostly noise — filter by category or status.

Input parameters:

- `category`
- `limit` (integer)
- `status`

### `describe_api` (~107 tokens)

Describe an API from the catalog.

Without `path`: catalog metadata plus, when an OpenAPI spec is published, the
full operation list (method + path + summary). With `path` (templated exactly
as the spec lists it): parameter/request/response schemas for that operation.

Paths from the spec are relative to the API's base_url — pass them to call_api
unchanged.

Input parameters:

- `api_id` (string, required)
- `method`
- `path`

### `call_api` (~228 tokens)

Call an endpoint of a catalog API; base URL and credentials are resolved for you.

\`path` is relative to the API's base_url (e.g. '/estados/mg') and may carry a query
string; `query` overrides its keys, and a list value repeats a key. `method` is GET,
HEAD, POST, PUT, PATCH, DELETE or OPTIONS; send `body` (JSON) only with POST/PUT/PATCH.
Credential, Host, proxy and framing headers in `headers` are dropped and listed in
\`ignored_headers`.

Returns {status, url, body} (JSON parsed, text cut at 60k chars); a 3xx is not followed
and carries its absolute `location`. Problems come back as {error}. Entries flagged
\`pii: true` return personal data (CPF/CNPJ): call them only when the user asked.

Input parameters:

- `api_id` (string, required)
- `body`
- `headers`
- `method` (string)
- `path` (string, required)
- `query`

### `credentials_status` (~89 tokens)

Show which APIs have credentials configured. Without api_id, reports every
catalog entry that requires auth, so you can see what is ready to call.

\`ready` says whether the credential env vars are set; `callable` whether call_api
accepts the entry right now (a requires_contract entry, such as Serpro's, only does
once they are).

Input parameters:

- `api_id`

Output parameters:

- `result` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/thalisantunes-govbr-apis-mcp/govbr-apis-mcp#diagnostics

## Score history

- 2026-11-06: 77
- 2026-11-05: 77
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 62

## Common questions

### What is the gov.br APIs MCP server?

gov.br APIs MCP is listed in the public MCP registry as io.github.thalisantunes/govbr-apis-mcp. A catalog-driven gateway over Brazilian government APIs, loading OpenAPI specs on demand. This page covers its PyPI package (govbr-apis-mcp).

### Is the gov.br APIs MCP server safe to use?

gov.br APIs MCP scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. Its build provenance is signed and verified. 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 gov.br APIs MCP server expose?

gov.br APIs MCP exposes 5 tools: search_catalog, list_apis, describe_api, call_api, credentials_status. Their descriptions and schemas cost roughly 614 tokens of context every time the server is loaded.

### Is the gov.br APIs MCP server still maintained?

gov.br APIs MCP is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the gov.br APIs MCP server under?

gov.br APIs MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the gov.br APIs MCP server?

VerifyMCP ran 15 checks on gov.br APIs MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about gov.br APIs MCP: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/govbr-apis-mcp/
- Socket report: https://socket.dev/pypi/package/govbr-apis-mcp
- Repository: https://github.com/thalisantunes/govbr-apis-mcp
- Changelog RSS feed: https://verifymcp.io/servers/thalisantunes-govbr-apis-mcp/govbr-apis-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/thalisantunes-govbr-apis-mcp/govbr-apis-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/thalisantunes-govbr-apis-mcp/govbr-apis-mcp.json
- HTML version of this page: https://verifymcp.io/servers/thalisantunes-govbr-apis-mcp/govbr-apis-mcp