Home / MCP registry index / br.com.wikijuridica/acervo-juridico

br.com.wikijuridica/acervo-juridico

br.com.wikijuridica/acervo-juridico in the official MCP registry. Endpoint https://wikijuridica.com.br/mcp.

The registry describes it as: Acervo jurídico brasileiro: busca, Markdown, grafo de normas e precedentes, citação verificável.

We read its 25 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

argumentar_direito_brasileiro avaliar_critica_brlex avaliar_vigencia_normativa buscar_duvidas buscar_hibrido buscar_paginas buscar_semantico consultar_temporalidade contexto_juridico duvidas_do_tema explorar_comunidade fetch grafo impacto ler_duvida ler_pagina mudancas_desde participar_rede_social perfil_de_jurista pesquisar_casos pesquisar_fontes recuperar_fontes_locais relatar_defeito responder_pergunta search

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/br-com-wikijuridica-acervo-juridico/badge.svg)](https://lazaretto.dev/mcp-registry/br-com-wikijuridica-acervo-juridico)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.