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

Leis do Brasil

PYPI · LEIS-MCP · 2 COMPONENTS

Busca e cita o texto oficial de mais de 1,2 milhão de normas brasileiras (ctresb/leis).

66 Trust /100

Last scanned (5 hours ago)

Scores higher than 63% of PyPI servers

Category Education and Research

Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 32 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 mazulo/leis-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 944 tokens (~188/item across 5 items; 4 tools + 1 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 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
  • 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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.

What we tested

Checks we ran (14)

  • 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 (2)

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.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • 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 →

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.

  • 4 Nov 26 66

    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 5 Nov 2026 · Analysed pypi/leis-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 mazulo/leis-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/mazulo/leis-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3683190128
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:b65a6b184c9bdcd6ce6d83be0bac9a6b3197f870af7d262e75b9eda69d2bc5fe

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool uv_build

Background: Why install scripts are a supply-chain risk →

Dependencies 32 packages
Packages resolved 32
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~765 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. 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 →

Tool Tokens
buscar_norma ~235

Localiza uma norma e devolve metadados do cabeçalho (título, ementa, data, revogada, versão do texto), caminho no repositório e link oficial da fonte.

NameTypeReqDescription
ano––Ano (4 dígitos).
esfera––federal, estaduais, municipais, reguladores, jurisprudencia ou tratados.
limiteinteger–Máximo de resultados (1 a 50).
numero––Número da norma (alternativa a `referencia`).
referencia––Referência livre: 'Lei 8.245/91', '8245/1991', '8.245', 'LC 123/2006', 'DL 5.452', ou apelido ('CDC', 'CLT', 'código civil', 'constituição').
tipo––Tipo: 'lei', 'lei complementar', 'decreto-lei', 'decreto', 'medida provisória', 'emenda constitucional' ou nome do diretório ('leis-ordinarias').
uf––UF, para normas estaduais (ex.: 'SP').

Structured output declared, but exposes no named fields.

No examples provided.

buscar_texto ~132

Busca um termo dentro de uma norma, ou nas normas já em cache local, indicando o artigo de cada ocorrência.

NameTypeReqDescription
ano––Filtro de ano.
consultastringyesPalavra ou trecho (ignora maiúsculas e acentos).
esfera––Filtro de esfera.
limiteinteger–Máximo de ocorrências (1 a 100).
norma––Restringe a uma norma (baixada sob demanda). Sem isso, busca só nas normas já em cache local.
tipo––Filtro de tipo.
uf––Filtro de UF.

Structured output declared, but exposes no named fields.

No examples provided.

ler_artigo ~208

Devolve o texto exato de um artigo (ou parágrafo, inciso, alínea), com o caput como contexto, link da fonte e avisos de revogação ou texto não compilado.

NameTypeReqDescription
alinea––Alínea: 'a', 'b'...
artigostringyesArtigo: '23', '9º', '4-A', '1.000'.
bloco––Quando a numeração reinicia na norma (ex.: ADCT na CF), trecho do título do bloco ('transitórias') ou índice.
inciso––Inciso em romano ('III') ou número (3).
normastringyesNorma: '8245/1991', 'Lei 8.245/91', apelido ('CDC', 'CLT', 'CF', 'ADCT') ou caminho no repositório.
paragrafo––Parágrafo: '2', '2º' ou 'único'.

Structured output declared, but exposes no named fields.

No examples provided.

listar_normas ~190

Navega pelo acervo: sem filtros devolve contagens por esfera; com esfera, por tipo; com tipo, por ano; com ano, lista as normas.

NameTypeReqDescription
ano––Ano. Vazio: contagem por ano.
esfera––federal, estaduais, municipais, reguladores, jurisprudencia, tratados. Vazio: contagem por esfera.
limiteinteger–Itens por página (1 a 200).
municipio––Município (slug, ex.: 'rio-branco').
offsetinteger–Deslocamento para paginação.
orgao––Órgão regulador ou tribunal (ex.: 'anvisa', 'stf').
tipo––Tipo (ex.: 'leis-ordinarias'). Vazio: contagem por tipo/UF/órgão.
uf––UF (estaduais/municipais).

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Leis do Brasil MCP server?

Leis do Brasil runs locally as a PyPI package, launched with uvx leis-mcp serve. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · leis-mcp

# add to Claude Code
claude mcp add mazulo-leis-mcp -- uvx leis-mcp serve
Common questions

What is the Leis do Brasil MCP server?

Leis do Brasil is an MCP server listed in the public MCP registry as io.github.mazulo/leis-mcp. Busca e cita o texto oficial de mais de 1,2 milhão de normas brasileiras (ctresb/leis). This page covers its PyPI package (leis-mcp).

Is the Leis do Brasil MCP server safe to use?

Leis do Brasil scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Leis do Brasil MCP server expose?

Leis do Brasil exposes 4 tools: buscar_norma, ler_artigo, buscar_texto, listar_normas. Their descriptions and schemas cost roughly 765 tokens of context every time the server is loaded.

Is the Leis do Brasil MCP server still maintained?

Leis do Brasil is still listed as active in the MCP registry. We last reached this channel on 5 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 Leis do Brasil MCP server under?

Leis do Brasil 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 Leis do Brasil MCP server?

VerifyMCP ran 14 checks on Leis do Brasil, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Leis do Brasil: Malware scan and 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.