No legal advice — every response carries not_legal_advice: true. The server retrieves; lawyers interpret.
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.
Citation required — all results include source URLs, jurisdiction tags, and retrieval timestamps.
Human review recommended — every response flags human_review_recommended: true.
Multi-jurisdictional — 14 countries across Americas, Europe, Asia-Pacific, and global sanctions.
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.
ADK-Rust agent
Chooses a capability from the reviewed tool catalog.
MCP client
Discovers schemas, sends calls, and receives typed content.
Legal Reference MCP Server
Validates the request and owns 14 documented tool contracts.
Domain system
Keeps the API, data, credentials, and business rules behind the server.
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_casesSearch US case law opinions by keyword
read onlyget_caseGet a specific US court opinion by cluster ID
read onlysearch_uk_legislationSearch UK legislation by keyword
read onlyget_uk_legislationGet UK legislation by identifier
read onlysearch_eu_legislationSearch EU legislation on EUR-Lex
read onlyget_eu_documentGet EU document by CELEX number
read onlysearch_federal_registerSearch US Federal Register for regulations
read onlyget_federal_register_documentGet Federal Register document by number
read onlyscreen_entityScreen entity against global sanctions lists
read onlysearch_sanctionsSearch sanctions lists by keyword
read onlyget_sanctions_recordGet detailed sanctions record by entity ID
read onlylist_supported_jurisdictionsList supported jurisdictions and sources
read onlyGovernance
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.
- 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.
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.
cargo install mcp-legal{
"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.
Keep exploring
More in industry solutions.
Source record
Release and repository metadata for this catalog entry.
- Version
- 1.4.1
- License
- Apache-2.0
- Tools
- 14
- Revision
- 64667b837ae3
- Updated
- May 27, 2026