io.github.matematicsolutions/br-eli-mcp
PYPI · BR-ELI-MCP · SCANNED SEP 20
MCP server for Brazilian federal law: legislation, DataJud, STJ, CARF, TST, TCU citations.
Available components
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 Security82
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known advisory affects this package; its severity couldn't be graded. See how to fix → View diagnostics → Fail
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 2 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 26 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4863 tokens (~324/item across 15 items; 15 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.matematicsolutions/br-eli-mcp server?
io.github.matematicsolutions/br-eli-mcp runs locally as a PyPI package, launched with uvx br-eli-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 · br-eli-mcp
claude mcp add matematicsolutions-br-eli-mcp -- uvx br-eli-mcp
{
"mcpServers": {
"matematicsolutions-br-eli-mcp": {
"command": "uvx",
"args": [
"br-eli-mcp"
]
}
}
} {
"servers": {
"matematicsolutions-br-eli-mcp": {
"command": "uvx",
"args": [
"br-eli-mcp"
]
}
}
} codex mcp add matematicsolutions-br-eli-mcp -- uvx br-eli-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"matematicsolutions-br-eli-mcp": {
"type": "local",
"command": [
"uvx",
"br-eli-mcp"
],
"enabled": true
}
}
} openclaw mcp add matematicsolutions-br-eli-mcp --command uvx --arg br-eli-mcp
mcp_servers:
matematicsolutions-br-eli-mcp:
command: "uvx"
args: ["br-eli-mcp"] {
"McpServers": {
"matematicsolutions-br-eli-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"br-eli-mcp"
]
}
}
} assistant mcp add matematicsolutions-br-eli-mcp -t stdio -c uvx -a br-eli-mcp
{
"mcpServers": {
"matematicsolutions-br-eli-mcp": {
"command": "uvx",
"args": [
"br-eli-mcp"
]
}
}
} 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 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.83 functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed pypi/br-eli-mcp@0.8.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w8v5-vhqr-4h9v | CVE-2025-69872 | medium | no | |
| PYSEC-2026-2447 | CVE-2025-69872 | none | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 2 |
| 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 →
br_coverage ~102
Declare what this connector covers, how it is sourced, and what it does NOT cover. Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead. Returns: ``Coverage`` with families, an as-of note, and a non-empty list of known gaps.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_note | string | yes | States what the dates mean, and what they do not promise. |
| families | array | – | – |
| known_gaps | array | – | Never empty. An empty list would mean 'not checked', not 'no gaps'. |
| status | string | – | – |
No examples provided.
br_get_case_carf ~146
Fetch one CARF (tax appeals) acordao by exact docket or decision number. Exactly one of `numero_processo` / `numero_decisao` must be given - this is an exact lookup, not a search. There is no free-text search tool for CARF because its full-text index is not reliably populated upstream (confirmed empty on live probing for common Portuguese terms).
| Name | Type | Req | Description |
|---|---|---|---|
| numero_decisao | – | – | CARF decision number, e.g. ``"9101-002.402"``. |
| numero_processo | – | – | CARF docket number, e.g. ``"16095.000602/2007-70"``. |
Structured output declared, but exposes no named fields.
No examples provided.
br_get_case_stj ~76
Fetch one STJ acordao by its exact numeroProcesso, with real ruling text.
| Name | Type | Req | Description |
|---|---|---|---|
| numero_processo | string | yes | the STJ process or registration number (digits; punctuation ignored). |
| orgao | string | yes | deciding chamber/section, e.g. ``"CORTE ESPECIAL"``. |
Structured output declared, but exposes no named fields.
No examples provided.
br_get_case_tcu ~198
Fetch one TCU acordao with the real ruling text: `acordao_texto` (deliberation), `relatorio` (rapporteur's report) and `voto` (vote). A TCU acordao is uniquely identified by (numero, ano, colegiado) - the same numero/ano recurs across the Plenario and the two Camaras. When `colegiado` is omitted and more than one acordao matches, this errors and lists the matching bodies instead of guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| ano | string | yes | four-digit year, e.g. ``"2026"``. |
| colegiado | – | – | deciding body - ``"Plenário"``, ``"Primeira Câmara"`` or ``"Segunda Câmara"`` (accent-sensitive, as spelled in the index). |
| numero | string | yes | acordao number, e.g. ``"1771"``. |
Structured output declared, but exposes no named fields.
No examples provided.
br_get_case_tst ~124
Fetch one TST ruling by its exact CNJ unified process number - real ruling text (`ementa` + `inteiro_teor`).
| Name | Type | Req | Description |
|---|---|---|---|
| numero_processo | string | yes | CNJ unified process number, formatted (``"21036-38.2019.5.04.0021"``) or as the raw 20 digits. The fifth segment is 5 (Justica do Trabalho) for every TST case. |
| tipo | string | – | document type (default ``"ACORDAO"``). |
Structured output declared, but exposes no named fields.
No examples provided.
br_get_norma ~145
Resolve a Brazilian Norma Juridica (enacted law/decree/amendment) by its URN Lex. Identification + Diario Oficial da Uniao publication provenance + amendment history + any STF unconstitutionality notes - NOT the full compiled article text (no confirmed URL rule to Planalto; see DISCOVERY.md).
| Name | Type | Req | Description |
|---|---|---|---|
| urn | string | yes | a URN Lex, e.g. ``"urn:lex:br:federal:lei:2002-01-10;10406"`` (Codigo Civil). Must start with ``"urn:lex:br:"`` - never invent one, take it from the user or from another tool's output. |
Structured output declared, but exposes no named fields.
No examples provided.
br_get_norma_index ~139
List the addressable structure of a Norma Juridica: parts, books, titles, chapters, sections, and articles, in document order. Use this to find the `dispositivo` suffix for the article you need (e.g. `"art5"`), then pass it to `br_get_norma_texto` - do not guess a suffix.
| Name | Type | Req | Description |
|---|---|---|---|
| urn | string | yes | a URN Lex, e.g. ``"urn:lex:br:federal:lei:2002-01-10;10406"`` (Codigo Civil). Must start with ``"urn:lex:br:"``. |
Structured output declared, but exposes no named fields.
No examples provided.
br_get_norma_texto ~157
Fetch the real text of one dispositivo (article, or a titulo/capitulo header) of a Norma Juridica. An article's text includes its caput and every paragraph/inciso/alinea beneath it, concatenated in document order - not a summary.
| Name | Type | Req | Description |
|---|---|---|---|
| dispositivo | string | yes | a suffix from `br_get_norma_index`, e.g. ``"art5"``. Never guess one - a wrong suffix returns `not_found`, it does not silently fall back to a different article. |
| urn | string | yes | a URN Lex, e.g. ``"urn:lex:br:federal:lei:2002-01-10;10406"``. |
Structured output declared, but exposes no named fields.
No examples provided.
br_get_processo ~90
Fetch one court docket by its exact CNJ unified process number.
| Name | Type | Req | Description |
|---|---|---|---|
| numero_processo | string | yes | the CNJ unified process number (digits, punctuation ignored), e.g. ``"5000035-87.2010.8.21.0057"``. |
| tribunal | string | yes | one of the supported tribunal codes, e.g. ``"STJ"``. |
Structured output declared, but exposes no named fields.
No examples provided.
br_get_proposicao ~52
Fetch full detail (including current status) for one bill by its numeric id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | the Camara dos Deputados proposicao id (from ``br_search_proposicoes``). |
Structured output declared, but exposes no named fields.
No examples provided.
br_search_case_stj ~222
Search STJ (Superior Tribunal de Justica) acordaos - real ruling text. Unlike `br_search_processos` (DataJud, metadata only), this returns the actual `ementa` (headnote) and `decisao` (ruling body prose) from the STJ Open Data Portal. Scans the most recent monthly bulk files for one orgao julgador (chamber/section) - a miss means "not in the scanned window", not "does not exist". Coverage starts May 2022.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | max results (default 20). |
| orgao | string | yes | deciding chamber/section, one of the keys in the supported list, e.g. ``"CORTE ESPECIAL"``, ``"TERCEIRA TURMA"``. |
| query | string | yes | free text - a process/registration number (6+ digits) matches exactly; anything else matches `ministroRelator` or `ementa` (case-insensitive substring). |
Structured output declared, but exposes no named fields.
No examples provided.
br_search_case_tcu ~135
Search TCU (Federal Court of Accounts) acordaos - public-procurement and public-spending jurisprudence. Returns summaries (`sumario`) plus the index's own total. Use `br_get_case_tcu` for the full ruling text of one acordao. The query supports the portal's own field-scoped syntax in addition to plain words, e.g. ``NUMACORDAO:1771 ANOACORDAO:2026``.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | max results (default 20). |
| query | string | yes | free text or field-scoped query. |
Structured output declared, but exposes no named fields.
No examples provided.
br_search_case_tst ~209
Search TST (labor supreme court) rulings by free text - real ruling text. The query goes into the TST frontend's own "contendo as palavras" (AND) field - quote an expression for an exact-phrase match, e.g. ``"adicional de insalubridade"``. Returns the index's own total plus a page of records carrying the real `ementa` and `inteiro_teor` prose.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | max results per page (default 20). |
| query | string | yes | free text (AND semantics; quotes for exact phrase). |
| tipo | string | – | document type - ``"ACORDAO"`` (default), ``"DESPACHO"``, ``"SUM"`` (sumulas), ``"OJ"`` (orientacoes jurisprudenciais), ``"PN"``, ``"DESPGP"``, ``"DESPGVP"``, ``"DESPGCG"``. |
Structured output declared, but exposes no named fields.
No examples provided.
br_search_processos ~192
Search court dockets (procedural metadata, NOT ruling text) in one tribunal's DataJud CNJ index. DataJud carries classe/assuntos/orgaoJulgador and the full procedural timeline (`movimentos`) for each docket - it does not carry the prose text of a ruling/acordao/ementa. STF is not covered (see server docstring).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | max results (default 20). |
| query | string | yes | free text - a CNJ process number (15+ digits) matches `numeroProcesso` exactly; anything else matches `classe.nome`. |
| tribunal | string | yes | one of the supported tribunal codes, e.g. ``"STJ"``, ``"TST"``, ``"TRF1"``, ``"TJSP"``, ``"TRT2"``, ``"TRE-SP"``. |
Structured output declared, but exposes no named fields.
No examples provided.
br_search_proposicoes ~99
List Brazilian federal bills (proposicoes) of a given type and year.
| Name | Type | Req | Description |
|---|---|---|---|
| ano | integer | yes | year, e.g. ``2024``. |
| itens | integer | – | max results (default 20, API caps around 100). |
| sigla_tipo | string | yes | bill type code, e.g. ``"PL"`` (Projeto de Lei), ``"PLP"``, ``"PEC"``. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.matematicsolutions/br-eli-mcp server?
io.github.matematicsolutions/br-eli-mcp is listed in the public MCP registry as io.github.matematicsolutions/br-eli-mcp. MCP server for Brazilian federal law: legislation, DataJud, STJ, CARF, TST, TCU citations. This page covers its PyPI package (br-eli-mcp).
Is the io.github.matematicsolutions/br-eli-mcp server safe to use?
io.github.matematicsolutions/br-eli-mcp scores 78 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 20 September 2026. 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 io.github.matematicsolutions/br-eli-mcp server expose?
io.github.matematicsolutions/br-eli-mcp exposes 15 tools: br_search_proposicoes, br_get_proposicao, br_get_norma, br_get_norma_index, br_get_norma_texto, and 10 more. Their descriptions and schemas cost roughly 2,086 tokens of context every time the server is loaded.
Is the io.github.matematicsolutions/br-eli-mcp server still maintained?
io.github.matematicsolutions/br-eli-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.matematicsolutions/br-eli-mcp server under?
io.github.matematicsolutions/br-eli-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.