4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
UniCourt MCP Server

Bring Court Records
to CrewAI

Learn how to connect UniCourt to CrewAI and start using 27 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
Delete Pacer CredentialGenerate TokenGet CaseGet Case Count AnalyticsGet Case Export CallbackGet Case Update StatusGet Document Order CallbackGet Norm AttorneyGet Norm JudgeGet Norm Law FirmGet Norm PartyGet Pacer CredentialImport CaseImport Pacer CaseOrder Case DocumentRequest Case ExportRequest Case UpdateSearch CasesSearch Norm AttorneySearch Norm JudgeSearch Norm Law FirmSearch Norm PartySearch Pacer Case LocatorTrack CaseTrack Norm AttorneyTrack Norm Law FirmUpdate Pacer Credential

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
UniCourt

What is the UniCourt MCP Server?

Connect your UniCourt account to any AI agent to streamline legal research and litigation tracking through natural language.

What you can do

  • Case Search — Search across millions of court cases using keyword expressions and filters
  • Automated Tracking — Use track_case to monitor specific litigation and receive updates on a schedule
  • Normalized Data — Access structured profiles for attorneys, law firms, judges, and parties to perform deep background checks
  • Document Management — Order court documents and export case data directly into your workflow
  • Legal Analytics — Retrieve case counts and analytics to understand litigation trends

How it works

  1. Subscribe to this server
  2. Enter your UniCourt Access Token
  3. Start querying legal records from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Legal Professionals — automate case monitoring and perform quick conflict checks
  • Researchers — gather large-scale litigation data for market analysis
  • Insurance & Finance — assess legal risks by inspecting party histories and active court cases

Built-in capabilities (27)

delete_pacer_credential

Delete PACER account credentials

generate_token

Generate a new UniCourt access token

get_case

Get details for a specific case

get_case_count_analytics

Get case count analytics by case type

get_case_export_callback

Get the file URL for a completed case export

get_case_update_status

Check the status of a requested case update

get_document_order_callback

Get the file URL for a completed document order

get_norm_attorney

Get analytics and details for a normalized attorney

get_norm_judge

Get analytics and details for a normalized judge

get_norm_law_firm

Get analytics and details for a normalized law firm

get_norm_party

Get analytics and details for a normalized party

get_pacer_credential

Retrieve current PACER account credentials status

import_case

High-priority case import

import_pacer_case

Import a case not in UniCourt via PACER

order_case_document

Order a court document

request_case_export

Request an export of case data as a ZIP file

request_case_update

Request an asynchronous update for a case

search_cases

g., caseName:pfizer). Search for court cases

search_norm_attorney

Search for normalized attorneys

search_norm_judge

Search for normalized judges

search_norm_law_firm

Search for normalized law firms

search_norm_party

Search for normalized parties

search_pacer_case_locator

Search PACER directly via Case Locator

track_case

Automatically update cases on a schedule

track_norm_attorney

Schedule recurring bar source refreshes for an attorney

track_norm_law_firm

Schedule recurring source refreshes for a law firm

update_pacer_credential

Manage PACER account credentials

Why CrewAI?

When paired with CrewAI, UniCourt becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call UniCourt 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 mcps parameter 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

See it in action

UniCourt in CrewAI

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

UniCourt and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect UniCourt 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.

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 UniCourt in CrewAI

The UniCourt 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 27 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.

UniCourt
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 UniCourt for CrewAI

Every tool call from CrewAI to the UniCourt 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

How can I search for court cases involving a specific company?

Use the search_cases tool with a query like caseName:"Company Name". The agent will return a list of matching cases with their UniCourt IDs and basic details.

02

Can the AI automatically track a case for new updates?

Yes! By using the track_case tool with a specific caseId, you can set up automated monitoring. You can even specify a refreshWindow like '1d' for daily updates.

03

Is it possible to get professional background data for an attorney?

Absolutely. Use search_norm_attorney to find the attorney and then get_norm_attorney with their ID to retrieve detailed analytics and professional history.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

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 →