4,000+ servers built on vurb.ts
Vinkius
Unlock for AI Agents
LangChainFramework
Brazilian Judiciary Dictionary Engine MCP Server

Bring Entity Extraction
to LangChain

Learn how to connect Brazilian Judiciary Dictionary Engine to LangChain and start using 1 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Search Legal Entities

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Brazilian Judiciary Dictionary Engine

What is the Brazilian Judiciary Dictionary Engine MCP Server?

Language models consistently fail to accurately identify and count legal entity acronyms in large document sets. This engine performs strict, deterministic regex boundary matching against the complete Brazilian judiciary.

What Is Included

  • 5 Tribunais Superiores: STF, STJ, TST, TSE, STM
  • 6 TRFs: TRF1 through TRF6
  • 24 TRTs: TRT1 (RJ) through TRT24 (MS)
  • 27 TJs: Every State Court including TJDFT
  • 3 TJMs: Tribunais de Justiça Militar (MG, RS, SP)
  • Órgãos de Controle: CNJ, CNMP, TCU
  • Ministério Público e Advocacia: AGU, MPF, MPT, MPM, MPDFT, DPU, OAB
  • Agências Reguladoras: CADE, CVM, BACEN, INPI, INSS, SUSEP, ANATEL, ANVISA, ANS, ANAC, ANEEL, ANP, ANA, ANTT, ANTAQ

What Is NOT Included

This engine covers exclusively the Brazilian judiciary and regulatory apparatus. Courts from other countries (US, UK, EU, etc.) are not included. Use the custom dictionary parameter to add entities from any other jurisdiction.

How It Works

  • Pure local regex with word boundary matching — zero AI, zero false positives.
  • Results grouped by category (Superior, TRF, TRT, TJ, Regulador, etc.).
  • Extensible via custom JSON dictionary for additional entities.

Built-in capabilities (1)

search_legal_entities

Searches text for known legal entities (courts, tribunals) using a strict offline dictionary

Why LangChain?

LangChain's ecosystem of 500+ components combines seamlessly with Brazilian Judiciary Dictionary Engine through native MCP adapters. Connect 1 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.

  • The largest ecosystem of integrations, chains, and agents. combine Brazilian Judiciary Dictionary Engine MCP tools with 500+ LangChain components

  • Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step

  • LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging

  • Memory and conversation persistence let agents maintain context across Brazilian Judiciary Dictionary Engine queries for multi-turn workflows

See it in action

Brazilian Judiciary Dictionary Engine in LangChain

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Brazilian Judiciary Dictionary Engine and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Brazilian Judiciary Dictionary Engine to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Brazilian Judiciary Dictionary Engine in LangChain

The Brazilian Judiciary Dictionary Engine MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 1 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Brazilian Judiciary Dictionary Engine
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Brazilian Judiciary Dictionary Engine for LangChain

Every tool call from LangChain to the Brazilian Judiciary Dictionary Engine MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

What exactly is pre-indexed?

The complete Brazilian judiciary: 5 Superior Courts, 6 TRFs, 24 TRTs, 27 TJs (including TJDFT), 3 military TJMs, oversight bodies (CNJ, CNMP, TCU), prosecution and advocacy (AGU, MPF, MPT, MPM, MPDFT, DPU, OAB), and 15 regulatory agencies (CADE, CVM, BACEN, INPI, INSS, SUSEP, ANATEL, ANVISA, ANS, ANAC, ANEEL, ANP, ANA, ANTT, ANTAQ).

02

Does it cover courts from other countries?

No. This engine covers exclusively the Brazilian legal system. To add courts from other countries, pass a custom JSON dictionary mapping acronyms to full names. Custom entries are tagged separately in the output.

03

How are results organized?

Each detected entity includes its acronym, full official name, category (Superior, TRF, TRT, TJ, TJM, Controle, MP/Advocacia, Regulador), and exact mention count. A category summary is also provided for quick analysis.

04

How does LangChain connect to MCP servers?

Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.

05

Which LangChain agent types work with MCP?

All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.

06

Can I trace MCP tool calls in LangSmith?

Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.

07

MultiServerMCPClient not found

Install: pip install langchain-mcp-adapters

Explore More MCP Servers

View all →