Legal Data Hunter MCP connector for AI agents

CALL ANY TOOL

7 tools covering get, discover.

legaldatahuntermcp_discover_countries

List all available countries with their document counts and

List all available countries with their document counts and source counts. returns ldh jurisdiction codes (mostly iso 3166-1 alpha-2, plus supranational codes like eu, un, coe, intl, oecd) with case law, legislation, and doctrine source counts and total document counts. this is the authoritative list of valid country codes to use in search and resolve_reference.

Parameters

Name

Type

Required

Description

—

No parameters required

legaldatahuntermcp_discover_sources

List all data sources available for a specific country. retu

legaldatahuntermcp_get_document

Retrieve a legal document by its source and source_id. retur

legaldatahuntermcp_get_filters

Get available filter values for a specific data source. retu

legaldatahuntermcp_report_source_issue

Report an issue with a data source to the platform maintaine

legaldatahuntermcp_resolve_reference

Resolve a loose legal citation or reference to the exact mat

legaldatahuntermcp_search

Search the world's fastest-growing legal database using hybr

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="legaldatahuntermcp")

mcp = MultiServerMCPClient({
    "legaldatahuntermcp": {
        "url": "https://mcp.scalekit.com/legaldatahuntermcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "legaldatahuntermcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/legaldatahuntermcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "legaldatahuntermcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/legaldatahuntermcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="legaldatahuntermcp")
# Connect to MCP at https://mcp.scalekit.com/legaldatahuntermcp
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Get started

Copy the prompt

Copied

Search the world’s fastest-growing legal database using hybrid semantic and keyword matching?

Copy the prompt

Copied

Resolve a loose legal citation or reference to the exact matching document(s)?

Advanced

Copy the prompt

Copied

Report an issue with a data source to the platform maintainer?

Copy the prompt

Copied

Get available filter values for a specific data source?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

1

Authorize

Your user connects

Legal Data Hunter MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

2

Store

Their

Legal Data Hunter MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

3

Resolve

When your agent calls a

Legal Data Hunter MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

4

Audit

Every

Legal Data Hunter MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

No items found.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Legal Data Hunter as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Legal Data Hunter OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Legal Data Hunter?
Yes. Pass a tool name filter to listScopedTools so the research agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Legal Data Hunter.

What happens when a user revokes Legal Data Hunter access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Which legal data sources can the agent search?
All sources indexed for the authorizing user's Legal Data Hunter account. Document retrieval and coverage queries run per user, keeping matter research attributable.

Legal Data Hunter MCP

Legal Data Hunter MCP tools for AI agents