Bring Entity Extraction
to LlamaIndex
Learn how to connect Brazilian Judiciary Dictionary Engine to LlamaIndex and start using 1 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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)
Searches text for known legal entities (courts, tribunals) using a strict offline dictionary
Why LlamaIndex?
LlamaIndex agents combine Brazilian Judiciary Dictionary Engine tool responses with indexed documents for comprehensive, grounded answers. Connect 1 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Brazilian Judiciary Dictionary Engine tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Brazilian Judiciary Dictionary Engine tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Brazilian Judiciary Dictionary Engine, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Brazilian Judiciary Dictionary Engine tools were called, what data was returned, and how it influenced the final answer
Brazilian Judiciary Dictionary Engine in LlamaIndex
Brazilian Judiciary Dictionary Engine and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Brazilian Judiciary Dictionary Engine to LlamaIndex 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Brazilian Judiciary Dictionary Engine in LlamaIndex
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 LlamaIndex 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.
* 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
How Vinkius secures
Brazilian Judiciary Dictionary Engine for LlamaIndex
Every tool call from LlamaIndex 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.
Frequently asked questions
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).
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.
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.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Brazilian Judiciary Dictionary Engine tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
Explore More MCP Servers
View all →
OmniEngage
12 toolsReach customers across email, SMS, push, and in-app with unified omnichannel marketing that personalizes every touchpoint.
Focus NFe
5 toolsEmit, consult, cancel and download XML for NFS-e and NF-e via Focus NFe API.
Nmap Online
10 toolsPerform network discovery and security auditing via Nmap — track port scans, DNS lookups, and traceroutes directly from your AI agent.
OpenFDA Alternative
8 toolsAccess FDA drug safety data, device recalls, food enforcement reports and approved drug information.