KivoHub Pesquisa de Leis
REMOTE · LEIS.KIVOHUB.AI
Artigos de lei, súmulas e temas do STF, STJ e TST com o link da fonte oficial. Grátis, sem login.
Available components
Last scanned (16 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 617 tokens (~205/item across 3 items; 3 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → good functional
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 0
- Tool “get_precedent” rewrote its description, which is the text the model reads security
- “get_precedent” reworded the description of “kind” cosmetic
- “get_precedent” reworded the description of “number” cosmetic
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 21 Nov 2026 · Probed https://leis.kivohub.ai/mcp?src=registro
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kivohub.ai | CN=YE2,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6517f537290d9da2327204d4f6ab71ee104 |
| SANs: *.kivohub.ai, kivohub.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of leis.kivohub.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| kivohub.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://leis.kivohub.ai/mcp?src=registro | Verified | 200 | |
| http (plaintext) | http://leis.kivohub.ai/mcp?src=registro | HTTPS enforced | 301 | https://leis.kivohub.ai/mcp?src=registro |
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 →
get_precedent Súmula ou tema de tribunal ~226
Enunciado de súmula do STF, STJ ou TST (inclui OJ do TST), ou tema do STJ ou do STF (repercussão geral), com a questão, a tese e o link da fonte. O mesmo número de tema existe em tribunais diferentes. Cada resultado traz `status`: verified (conferido no texto compilado do Planalto), unverified (ainda não conferido), under_review (o texto desta base difere do oficial e não é exibido) ou revoked (revogado).
| Name | Type | Req | Description |
|---|---|---|---|
| binding | boolean | – | true para súmula vinculante do STF |
| court | string | yes | "STF", "STJ" ou "TST" |
| kind | string | – | "sumula" (padrão), "tema" (STJ ou STF) ou "oj" (OJ do TST) |
| number | string | yes | Número da súmula ou do tema ("331", "677"). OJ do TST com o órgão: "SDI-1 191" |
Structured output declared, but exposes no named fields.
No examples provided.
get_provision Texto de artigo de lei ~199
Texto de um artigo, parágrafo, inciso ou alínea de lei federal brasileira, com o link oficial. Cada resultado traz `status`: verified (conferido no texto compilado do Planalto), unverified (ainda não conferido), under_review (o texto desta base difere do oficial e não é exibido) ou revoked (revogado).
| Name | Type | Req | Description |
|---|---|---|---|
| article | string | yes | Número do artigo. Ex.: "11", "7º", "1.022", "11-A" |
| block | – | – | Só para o ADCT da Constituição: "ADCT" |
| item | – | – | Inciso em romano: "XXIX" |
| law | string | yes | Lei: apelido ou URN. Ex.: "CLT", "Código Civil", "CF", "CDC" |
| paragraph | – | – | Parágrafo: "1", "2º" ou "único" |
| subitem | – | – | Alínea: "a" |
Structured output declared, but exposes no named fields.
No examples provided.
search_legislation Busca de leis por assunto ~148
Busca dispositivos de lei e súmulas por uma pergunta em linguagem natural e devolve os mais próximos, com o link oficial. Cada resultado traz `status`: verified (conferido no texto compilado do Planalto), unverified (ainda não conferido), under_review (o texto desta base difere do oficial e não é exibido) ou revoked (revogado).
| Name | Type | Req | Description |
|---|---|---|---|
| law | – | – | Restringe a uma lei: "CDC", "CLT", "CF"… |
| query | string | yes | Pergunta. Ex.: "prazo para reclamar de vício aparente" |
| top_k | integer | – | Quantos artigos devolver (padrão 5) |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the KivoHub Pesquisa de Leis MCP server?
KivoHub Pesquisa de Leis is a hosted endpoint at https://leis.kivohub.ai/mcp?src=registro, 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 · leis.kivohub.ai
claude mcp add --transport http ai-kivohub-pesquisa-de-leis 'https://leis.kivohub.ai/mcp?src=registro'
What is the KivoHub Pesquisa de Leis MCP server?
KivoHub Pesquisa de Leis is an MCP server listed in the public MCP registry as ai.kivohub/pesquisa-de-leis. Artigos de lei, súmulas e temas do STF, STJ e TST com o link da fonte oficial. Grátis, sem login. This page covers its hosted endpoint (https://leis.kivohub.ai/mcp?src=registro).
Is the KivoHub Pesquisa de Leis MCP server safe to use?
KivoHub Pesquisa de Leis scores 76 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 KivoHub Pesquisa de Leis MCP server expose?
KivoHub Pesquisa de Leis exposes 3 tools: get_provision, get_precedent, search_legislation. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.
Does the KivoHub Pesquisa de Leis MCP server require authentication?
No. We connected to KivoHub Pesquisa de Leis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the KivoHub Pesquisa de Leis MCP server still maintained?
KivoHub Pesquisa de Leis is still listed as active in the MCP registry. We last reached this channel on 21 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 KivoHub Pesquisa de Leis MCP server?
VerifyMCP ran 13 checks on KivoHub Pesquisa de Leis, 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.