Bring Entity Extraction
to CrewAI
Learn how to connect Brazilian Judiciary Dictionary Engine to CrewAI 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 CrewAI?
When paired with CrewAI, Brazilian Judiciary Dictionary Engine becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Brazilian Judiciary Dictionary Engine tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Brazilian Judiciary Dictionary Engine in CrewAI
Brazilian Judiciary Dictionary Engine and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Brazilian Judiciary Dictionary Engine to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Zenserp
10 toolsScrape live search engine results (SERP) from Google, Bing, Yandex, and DuckDuckGo using Zenserp's high-speed API.
Bcrypt Hash Engine
2 toolsHash and verify passwords with the industry-standard bcrypt algorithm. Two tools in one: hash with configurable salt rounds, and verify against stored hashes. Pure JS — zero compilation.
Todoist
7 toolsManage tasks, organize projects, and streamline your personal or team workflows natively with your AI agent.
ServiceNow
10 toolsManage incidents, service requests, change orders, and CMDB records on ServiceNow — the enterprise ITSM backbone.