legalize-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GH_TOKEN | No | Enables code search; lifts rate limits (alternative to GITHUB_TOKEN). | |
| GITHUB_TOKEN | No | Enables code search; lifts rate limits. | |
| LEGALIZE_AUDIT_DIR | No | JSONL audit log location (AI Act art. 12). | ~/.matematic/audit |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| legalize_list_countriesB | List the jurisdictions available in the legalize-dev corpus. |
| legalize_search_lawsA | Search a jurisdiction's laws by keyword (GitHub code search; requires a token). |
| legalize_get_lawA | Fetch a law's metadata and full text by id (optionally at a historical commit). |
| legalize_get_metaA | Fetch only a law's frontmatter metadata (no body) - cheap for citation checks. |
| legalize_list_reformsA | List the reform history (commits) of a law - the legislative timeline. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: retrieving full law text, retrieving metadata only, listing available countries, listing reform history, and searching laws. No ambiguity.
All tools follow the consistent pattern of 'legalize_' prefix followed by verb_noun (e.g., get_law, list_countries, search_laws). Perfectly uniform.
With 5 tools, the server covers core operations for a legal document retrieval system without being sparse or bloated. Well-scoped.
The server provides full retrieval (by ID), metadata-only retrieval, jurisdiction listing, reform timeline, and keyword search. For a read-only legal database, this is complete.