gov.br APIs MCP
PYPI · GOVBR-APIS-MCP
A catalog-driven gateway over Brazilian government APIs, loading OpenAPI specs on demand.
Available components
Last scanned (3 hours ago)
Scores higher than 75% of PyPI servers
Category Developer Tools
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to thalisantunes/govbr-apis-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Oct 26 62
First indexed and scored.
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 6 Nov 2026 · Analysed pypi/govbr-apis-mcp@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | thalisantunes/govbr-apis-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/thalisantunes/govbr-apis-mcp/.github/workflows/publish.yml@refs/tags/v0.2.0 |
| Rekor log index | 3326689189 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:69b6f6d94724914c9353e4489f560c8248ee7e2815dc42b130fb5d29c61e77e6 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 33 packages
| Packages resolved | 33 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_api ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_id | string | yes | – |
| body | – | – | – |
| headers | – | – | – |
| method | string | – | – |
| path | string | yes | – |
| query | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
credentials_status ~89
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).
| Name | Type | Req | Description |
|---|---|---|---|
| api_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
describe_api ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_id | string | yes | – |
| method | – | – | – |
| path | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_apis ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| limit | integer | – | – |
| status | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_catalog ~93
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).
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
pypi · govbr-apis-mcp
claude mcp add thalisantunes-govbr-apis-mcp -- uvx govbr-apis-mcp
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.