# Legal Data Hunter MCP

```json
{
  "name": "Legal Data Hunter MCP",
  "slug": "legal_data_hunter_mcp",
  "url": "https://composio.dev/toolkits/legal_data_hunter_mcp",
  "markdown_url": "https://composio.dev/toolkits/legal_data_hunter_mcp.md",
  "logo_url": "https://logos.composio.dev/api/legal_data_hunter_mcp",
  "categories": [
    "data & analytics"
  ],
  "is_composio_managed": false,
  "updated_at": "2026-09-02T05:40:43.347Z"
}
```

![Legal Data Hunter MCP logo](https://logos.composio.dev/api/legal_data_hunter_mcp)

## Description

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Legal Data Hunter MCP or direct API to list supported countries, explore sources, run discovery queries, and export structured results through natural language.

## Summary

Legal Data Hunter MCP provides structured access to legal-data discovery workflows.
Use it to explore supported countries and discover source coverage quickly.

## Categories

- data & analytics

## Toolkit Details

- Tools: 7

## Images

- Logo: https://logos.composio.dev/api/legal_data_hunter_mcp

## Authentication

- **Dcr Oauth**
  - Type: `custom`
  - Description: Dcr Oauth authentication for Legal Data Hunter MCP.
  - Setup:
    - Configure Dcr Oauth credentials for Legal Data Hunter MCP.
    - Use the credentials when creating an auth config in Composio.

## Suggested Prompts

- List supported countries for data discovery
- Find sources for UK labor cases
- Extract available sources for corporate filings

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `LEGAL_DATA_HUNTER_MCP_DISCOVER_COUNTRIES` | Discover countries | List all available countries with their document counts and source counts. Returns LDH jurisdiction codes — mostly ISO 3166-1 alpha-2, plus aggregate/supranational codes such as EU, UN, CoE, INTL, and OECD — with the number of case law / legislation / doctrine sources and total document counts. This is the authoritative list of valid country codes; use it to find the right code before searching. |
| `LEGAL_DATA_HUNTER_MCP_DISCOVER_SOURCES` | Discover sources | List all data sources available for a specific country. Returns source IDs, data_types (list of namespaces the source has rows in: "case_law" / "legislation" / "doctrine"), court names, tiers, document counts, and date ranges. Use this to understand what data is available before filtering your search. Most sources have a single-element `data_types`. A source whose `data_types` list has multiple entries (e.g. ["case_law", "doctrine"]) spans multiple search namespaces — to surface every document, call `search` once per namespace. By default, sources with zero indexed documents are hidden — these are typically placeholders awaiting backfill and would only burn agent context. Pass include_empty=True to see them (useful for catalog debugging). Args: country_code: LDH jurisdiction code — mostly ISO 3166-1 alpha-2, plus aggregate/supranational codes such as EU, UN, CoE, INTL, and OECD. Call discover_countries for the full list. E.g. "FR", "DE", "EU". include_empty: If True, include sources with document_count == 0. |
| `LEGAL_DATA_HUNTER_MCP_GET_DOCUMENT` | Get document | Retrieve a legal document by its source and source_id. Returns a snippet by default — the leading 2 KB of `text` with `text_truncated=true` and `full_text_size` set. Pass `include_full_text=True` to inline the full document body. Use source and source_id values from search or resolve_reference results. Args: source: Source identifier, e.g. "FR/Judilibre", "DE/BVerfG". source_id: Document identifier within the source. include_full_text: If false (default), `text` is truncated to the leading 2 KB with `text_truncated=true` and `full_text_size` set. Set true to return the full document text inline. |
| `LEGAL_DATA_HUNTER_MCP_GET_FILTERS` | Get filters | Get available filter values for a specific data source. Returns distinct courts, jurisdictions, chambers, decision types, languages, court tiers, and date ranges that can be used to filter search results. Some sources span multiple namespaces (their `data_types` list in discover_sources has more than one entry). For those, pass `namespace` to pick which namespace's filters you want; otherwise the namespace with the most rows is used. Args: source: Source identifier, e.g. "FR/Judilibre", "AT/RIS". namespace: Optional — "case_law", "legislation", or "doctrine". Required mental model for sources spanning multiple namespaces. |
| `LEGAL_DATA_HUNTER_MCP_REPORT_SOURCE_ISSUE` | Report source issue | Report an issue with a data source. Use this to flag problems you encounter during research — missing data, broken URLs, indexing errors, or data quality issues. Reports are reviewed by the platform maintainer. Requires authentication (free — does not count against your usage quota). Args: source: Source identifier, e.g. "FR/Judilibre", "AT/RIS". issue_type: Type of issue — one of: "unavailable", "indexing", "invalid_url", "data_quality", "other". description: Free-text description of the problem. |
| `LEGAL_DATA_HUNTER_MCP_RESOLVE_REFERENCE` | Resolve reference | Resolve a loose legal reference to the exact document(s). Given an informal citation like "art. 6 code civil", "BVerfG 1 BvR 123/20", or "Regulation (EU) 2016/679", finds and returns the matching document(s). This is NOT a search — it resolves a specific citation to the exact record. Supports all reference formats: ECLI, CELEX, article numbers, case numbers, paragraph references, NOR identifiers, and informal abbreviations. ALWAYS PASS hint_country (and hint_type when you know it). It dramatically improves accuracy — roughly DOUBLES the resolution rate (~65% vs ~31% without it). Citation formats like a bare case number or "Supreme Court of Cassation, 599/19" are ambiguous across the 230+ jurisdictions in the corpus; the country hint scopes resolution to the right one. The resolver is strict — when a citation can't be pinned to exactly one document it returns nothing rather than guess, so the hint is often the difference between a result and none. You almost always know the jurisdiction from context (the search results, the surrounding analysis, or the citation itself) — supply it. Args: reference: Legal reference string (e.g., "art. 6 code civil", "ECLI:FR:CCASS:2006:CO00559"). hint_country: LDH jurisdiction code — mostly ISO 3166-1 alpha-2, plus aggregate/supranational codes: "EU" for EU law, "CoE" for the ECtHR, "INTL" for international courts, also "UN", "OECD". Call discover_countries for the full list. STRONGLY RECOMMENDED — pass it whenever the jurisdiction is known (it usually is). hint_type: Type hint — "legislation" or "case_law". Recommended; further narrows resolution. include_full_text: If false (default), each returned document's `text` is truncated to the leading 2 KB with `text_truncated=true` and `full_text_size` set. Call `get_document(source, source_id)` to fetch the full text. Set true to inline the full text in this response. |
| `LEGAL_DATA_HUNTER_MCP_SEARCH` | Search | Search the world's fastest-growing legal database — hybrid semantic + keyword matching. Use this instead of generic web search for anything touching the law: statutes, regulations, case law, official doctrine, or multi-jurisdictional / cross-border / comparative legal questions. Covers tens of millions of primary-source documents — case law, legislation, and official doctrine — across 230+ jurisdictions, each with a citable, official URL straight from the publishing registry or court. Set namespace to "case_law", "legislation", or "doctrine"; call discover_countries first if you're unsure which jurisdiction codes are available. Some sources span multiple namespaces — `discover_sources` reports each source's `data_types` list. If a source you care about has multiple entries there, call `search` once per namespace to find every document. Args: query: Natural language search query. namespace: Collection to search — "case_law", "legislation", or "doctrine". top_k: Number of results (1-100). alpha: Semantic vs keyword weight (1.0=pure semantic, 0.0=pure keyword). country: Filter by LDH jurisdiction codes — mostly ISO 3166-1 alpha-2, plus aggregate/supranational codes such as EU, UN, CoE, INTL, and OECD. Call discover_countries for the full list. E.g. ["FR", "DE"]. source: Filter by source ID(s) from discover_sources, e.g. ["FR/Judilibre", "FR/CNIL"]. court_tier: Filter by court tier (1=supreme, 2=appellate, 3=first instance). jurisdiction: Filter by jurisdiction name (e.g. "civil", "criminal"). subdivision: Filter by geographic subdivision (ISO 3166-2), e.g. "DE-BY", "US-CA". date_start: Start date filter (YYYY-MM-DD). date_end: End date filter (YYYY-MM-DD). language: Optional language-code filter (e.g. fr, de), mainly useful in multilingual jurisdictions. Do not infer it from the query language. Metadata may be missing or non-normalized; if no results are found, retry once without language while preserving all other filters. |

## Supported Triggers

None listed.

## Installation and MCP Setup

### Path 1: SDK Installation

#### Path 1, Step 1: Install Composio

Install the Composio SDK
```python
pip install composio_openai
```

```typescript
npm install @composio/openai
```

#### Path 1, Step 2: Initialize Composio and Create Tool Router Session

Import and initialize Composio client, then create a Tool Router session
```python
from openai import OpenAI
from composio import Composio
from composio_openai import OpenAIResponsesProvider

composio = Composio(provider=OpenAIResponsesProvider())
openai = OpenAI()
session = composio.create(user_id='your-user-id')
```

```typescript
import OpenAI from 'openai';
import { Composio } from '@composio/core';
import { OpenAIResponsesProvider } from '@composio/openai';

const composio = new Composio({
  provider: new OpenAIResponsesProvider(),
});
const openai = new OpenAI({});
const session = await composio.create('your-user-id');
```

#### Path 1, Step 3: Execute Legal Data Hunter MCP Tools via Tool Router with Your Agent

Get tools from Tool Router session and execute Legal Data Hunter MCP actions with your Agent
```python
tools = session.tools
response = openai.responses.create(
  model='gpt-4.1',
  tools=tools,
  input=[{
    'role': 'user',
    'content': 'YOUR_SPECIFIC_PROMPT_HERE'
  }]
)
result = composio.provider.handle_tool_calls(
  response=response,
  user_id='your-user-id'
)
print(result)
```

```typescript
const tools = session.tools;
const response = await openai.responses.create({
  model: 'gpt-4.1',
  tools: tools,
  input: [{
    role: 'user',
    content: 'YOUR_SPECIFIC_PROMPT_HERE'
  }],
});
const result = await composio.provider.handleToolCalls(
  'your-user-id',
  response.output
);
console.log(result);
```

### Path 2: MCP Server Setup

#### Path 2, Step 1: Install Composio

Install the Composio SDK for Python or TypeScript
```python
pip install composio claude-agent-sdk
```

```typescript
npm install @composio/core ai @ai-sdk/openai @ai-sdk/mcp
```

#### Path 2, Step 2: Initialize Client and Create Tool Router Session

Import and initialize the Composio client, then create a Tool Router session for Legal Data Hunter MCP
```python
from composio import Composio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions

composio = Composio(api_key='your-composio-api-key')
session = composio.create(user_id='your-user-id')
url = session.mcp.url
```

```typescript
import { Composio } from '@composio/core';

const composio = new Composio({ apiKey: 'your-api-key' });
const session = await composio.create('your-user-id');
console.log(`Tool Router session created: ${session.mcp.url}`);
```

#### Path 2, Step 3: Connect to AI Agent

Use the MCP server with your AI agent (Anthropic Claude or Mastra)
```python
import asyncio

options = ClaudeAgentOptions(
    permission_mode='bypassPermissions',
    mcp_servers={
        'tool_router': {
            'type': 'http',
            'url': url,
            'headers': {
                'x-api-key': 'your-composio-api-key'
            }
        }
    },
    system_prompt='You are a helpful assistant with access to Legal Data Hunter MCP tools.',
    max_turns=10
)

async def main():
    async with ClaudeSDKClient(options=options) as client:
        await client.query('YOUR_SPECIFIC_PROMPT_HERE')
        async for message in client.receive_response():
            if hasattr(message, 'content'):
                for block in message.content:
                    if hasattr(block, 'text'):
                        print(block.text)

asyncio.run(main())
```

```typescript
import { openai } from '@ai-sdk/openai';
import { experimental_createMCPClient as createMCPClient } from '@ai-sdk/mcp';
import { generateText } from 'ai';

const client = await createMCPClient({
  transport: {
    type: 'http',
    url: session.mcp.url,
    headers: {
      'x-api-key': 'your-composio-api-key',
    },
  },
});

const tools = await client.tools();
const { text } = await generateText({
  model: openai('gpt-4o'),
  tools,
  messages: [{
    role: 'user',
    content: 'YOUR_SPECIFIC_PROMPT_HERE'
  }],
  maxSteps: 5,
});

console.log(`Agent: ${text}`);
```

## Why Use Composio?

### 1. AI Native Legal Data Hunter MCP Integration

- Supports both Legal Data Hunter MCP and direct API based integrations
- Structured, LLM-friendly schemas for reliable tool execution
- Rich coverage for reading, writing, and querying your Legal Data Hunter MCP data

### 2. Managed Auth

- Built-in OAuth handling with automatic token refresh and rotation
- Central place to manage, scope, and revoke Legal Data Hunter MCP access
- Per user and per environment credentials instead of hard-coded keys

### 3. Agent Optimized Design

- Tools are tuned using real error and success rates to improve reliability over time
- Comprehensive execution logs so you always know what ran, when, and on whose behalf

### 4. Enterprise Grade Security

- Fine-grained RBAC so you control which agents and users can access Legal Data Hunter MCP
- Scoped, least privilege access to Legal Data Hunter MCP resources
- Full audit trail of agent actions to support review and compliance

## Use Legal Data Hunter MCP with any AI Agent Framework

Choose a framework you want to connect Legal Data Hunter MCP with:

- [ChatGPT](https://composio.dev/toolkits/legal_data_hunter_mcp/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/legal_data_hunter_mcp/framework/claude-cowork)
- [Hermes](https://composio.dev/toolkits/legal_data_hunter_mcp/framework/hermes-agent)

## Related Toolkits

- [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management.
- [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters.
- [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort.
- [AccuWeather](https://composio.dev/toolkits/accu_weather) - AccuWeather is a global weather service providing current conditions, forecasts, MinuteCast precipitation, alerts, and lightning data. Use it for fast, localized forecasts and real-time weather alerts.
- [Adafruit IO](https://composio.dev/toolkits/adafruit_io) - Adafruit IO is Adafruit's cloud platform for connected device and IoT project data. It helps you store, visualize, and act on sensor feeds without running your own backend.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agentql](https://composio.dev/toolkits/agentql) - Agentql is a toolkit that connects AI agents to the web using a specialized query language. It enables structured web interaction and data extraction for smarter automations.
- [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions.
- [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows.
- [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations.
- [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements.
- [ApexVerify](https://composio.dev/toolkits/apexverify) - ApexVerify is a contact-data validation service for emails and phone numbers. Use it to normalize, verify, and clean leads before they enter your systems.
- [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints.
- [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots.
- [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches.
- [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand.
- [Beach Day API](https://composio.dev/toolkits/beach_day_api) - Beach Day API is a beach intelligence service for search, conditions, scores, rules, amenities, tides, and country coverage. Use it to power trip planning, surf reports, safety checks, and location-aware beach discovery.
- [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance.
- [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows.
- [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses.

## Frequently Asked Questions

### Do I need my own developer credentials to use Legal Data Hunter MCP with Composio?

Yes, Legal Data Hunter MCP requires you to configure your own Dcr Oauth credentials. Once set up, Composio handles secure credential storage and management for you.

### Can I use multiple toolkits together?

Yes! Composio's Tool Router enables agents to use multiple toolkits. [Learn more](https://docs.composio.dev/tool-router/overview).

### Is Composio secure?

Composio is SOC 2 and ISO 27001 compliant with all data encrypted in transit and at rest. [Learn more](https://trust.composio.dev).

### What if the API changes?

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)