MCP server registry
Industry solutionsPublic source

Legal Reference MCP Server

Governed, global legal reference data for ADK-Rust Enterprise agents. Provides 24 MCP tools across 14 jurisdictions — retrieves and structures legal information without providing legal advice.

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

01

No legal advice — every response carries not_legal_advice: true. The server retrieves; lawyers interpret.

02

Citation required — all results include source URLs, jurisdiction tags, and retrieval timestamps.

03

Human review recommended — every response flags human_review_recommended: true.

04

Multi-jurisdictional — 14 countries across Americas, Europe, Asia-Pacific, and global sanctions.

05

Governed access — all tools are read-only with governance gates for audit compliance.

Architecture

How Legal Reference MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

01

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

02

MCP client

Discovers schemas, sends calls, and receives typed content.

03

Legal Reference MCP Server

Validates the request and owns 14 documented tool contracts.

04

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.

Tool catalog

What can an agent ask Legal Reference MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

14 named tools

search_cases

Search US case law opinions by keyword

read only
get_case

Get a specific US court opinion by cluster ID

read only
search_uk_legislation

Search UK legislation by keyword

read only
get_uk_legislation

Get UK legislation by identifier

read only
search_eu_legislation

Search EU legislation on EUR-Lex

read only
get_eu_document

Get EU document by CELEX number

read only
search_federal_register

Search US Federal Register for regulations

read only
get_federal_register_document

Get Federal Register document by number

read only
screen_entity

Screen entity against global sanctions lists

read only
search_sanctions

Search sanctions lists by keyword

read only
get_sanctions_record

Get detailed sanctions record by entity ID

read only
list_supported_jurisdictions

List supported jurisdictions and sources

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

14 read only
  • Governed access — all tools are read-only with governance gates for audit compliance.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.
ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install
cargo install mcp-legal
MCP client configuration
{
  "mcpServers": {
    "legal": {
      "command": "mcp-legal"
    }
  }
}

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Source record

Release and repository metadata for this catalog entry.

View public repository ↗
Version
1.4.1
License
Apache-2.0
Tools
14
Revision
64667b837ae3
Updated
May 27, 2026
Transportsstdio