JuriBase
REMOTE · BUSCA.JURIBASE.COM.BR
Busca e verifica jurisprudência brasileira real (+400 mil julgados) — anti-alucinação para IA.
Available components
Last scanned (20 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 835 tokens (~417/item across 2 items; 2 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “buscar_jurisprudencia” rewrote its description, which is the text the model reads security
- 30 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “buscar_jurisprudencia” rewrote its description, which is the text the model reads security
- Tool “verificar_citacao” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 · Probed https://busca.juribase.com.br/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=juribase.com.br | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | fb84d6b6ec9ece650e05b5c9659373b5 |
| SANs: juribase.com.br, *.juribase.com.br | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of busca.juribase.com.br. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| br. | DS published | 38298 | 13 | Verified |
| com.br. | DS published | 50930 | 13 | Verified |
| juribase.com.br. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://busca.juribase.com.br/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://busca.juribase.com.br/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://busca.juribase.com.br/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://busca.juribase.com.br/mcp |
| Authorisation server | https://busca.juribase.com.br |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://busca.juribase.com.br/mcp | Verified | 200 | |
| http (plaintext) | http://busca.juribase.com.br/mcp | HTTPS enforced | 301 | https://busca.juribase.com.br/mcp |
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 →
buscar_jurisprudencia Buscar jurisprudência ~208
Busca decisões judiciais brasileiras reais (acórdãos, súmulas, teses, repetitivos) na base JuriBase, de fontes oficiais — todos os 27 TJs, 6 TRFs, STF, STJ, TST, TNU. Útil para encontrar jurisprudência/precedentes que fundamentem uma resposta jurídica. Cada resultado traz o julgado real com a fonte oficial; nunca invente citações — cite só o que a busca devolver. Filtre por tribunais (ex.: ['STJ','TJSP']) quando o usuário especificar. Retorna ementa, processo, relator, data, link da fonte oficial e o escopo coberto.
| Name | Type | Req | Description |
|---|---|---|---|
| consulta | string | yes | tema, pergunta jurídica ou palavras-chave (ex.: 'dano moral negativação indevida') |
| tribunais | array | – | siglas para filtrar (ex.: ['STJ','TJSP']); omita para buscar em toda a base |
No output schema declared.
No examples provided.
verificar_citacao Verificar citação de jurisprudência ~168
Verifica se uma citação de jurisprudência brasileira (número de processo, acórdão ou tese) existe na base JuriBase de fontes oficiais. Útil para checar uma citação antes de apresentá-la ao usuário, ou quando o usuário fornecer uma citação para conferir. Retorna CONFIRMADO (com os dados reais), DIVERGENCIA (existe, mas com dados diferentes), NAO_ENCONTRADO (verifiquei e não achei no escopo coberto) ou INDISPONIVEL (a base não pôde ser consultada agora — NÃO conclua que a citação não existe; tente novamente), mais o escopo coberto.
| Name | Type | Req | Description |
|---|---|---|---|
| texto | string | yes | a citação, número de processo ou trecho a verificar |
No output schema declared.
No examples provided.
How do I install the JuriBase MCP server?
JuriBase is a hosted endpoint at https://busca.juribase.com.br/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.
remote · busca.juribase.com.br
claude mcp add --transport http andersongadelhaadv-cmyk-juri-verify 'https://busca.juribase.com.br/mcp'
What is the JuriBase MCP server?
JuriBase is an MCP server listed in the public MCP registry as io.github.andersongadelhaadv-cmyk/juri-verify. Busca e verifica jurisprudência brasileira real (+400 mil julgados), anti-alucinação para IA. This page covers its hosted endpoint (https://busca.juribase.com.br/mcp).
Is the JuriBase MCP server safe to use?
JuriBase scores 89 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 JuriBase MCP server expose?
JuriBase exposes 2 tools: verificar_citacao, buscar_jurisprudencia. Their descriptions and schemas cost roughly 376 tokens of context every time the server is loaded.
Does the JuriBase MCP server require authentication?
Yes. JuriBase asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the JuriBase MCP server still maintained?
JuriBase 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 did VerifyMCP test on the JuriBase MCP server?
VerifyMCP ran 13 checks on JuriBase, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.