# Legalize [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/legalize-dev/mcp  
**GitHub Stars:** 2  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/legalize-2

## Description
Official MCP connector for Legalize: read and search its whole open corpus, at any point in time.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "legalize": {
    "url": "https://legalize.dev/mcp"
  }
}
```

## Documentation

## What Legalize MCP server does

Legalize MCP server gives AI clients access to an open corpus of legislation maintained by Legalize. The corpus is read-only through the connector: clients cannot edit legal text, versions, or history. Results include the relevant data, a citation, a URL, source information, and a note, with links back to Legalize pages.

The service is designed for questions such as what a law said on a particular date, whether wording changed between two dates, and which other norms amended a given law. Retrieved material can include a complete law or a complete article rather than a truncated passage. Historical results include the git commit SHA associated with the version.

## How it works

The endpoint is available at `https://legalize.dev/mcp` and uses stateless Streamable HTTP. No local Legalize package is required. A compatible client connects to the URL and prompts the user to sign in when a tool is first called. Clients that only support stdio can use `npx mcp-remote https://legalize.dev/mcp` as a bridge.

The normal research flow is to list available countries, search for a law by title words or official number, then pass the returned law ID to retrieval, historical, comparison, or amendment-history tools. The live tool definitions, including argument types, are published at `https://legalize.dev/mcp/tools.json`.

## Tools and capabilities

The Legalize MCP server exposes read operations for:

- `list_countries`, which reports countries represented in the corpus and law counts.
- `search_laws`, which finds laws by title text or official number.
- `get_law`, which returns the current full law or a selected article.
- `law_at_date`, which returns wording from a specified date and its git SHA.
- `diff_law`, which compares law text between two dates.
- `reform_history`, which identifies amending norms, dates, and described changes.
- `law_stats`, which summarizes corpus size and activity.

It also provides subscription management. `preview_webhook` tests a rule against the previous 30 days without creating a subscription. Webhook tools can subscribe an HTTPS endpoint to matching changes, while email digest tools send matching changes in one daily message to the account’s own email address. Filters can target laws, countries, title words, or subject headings; filters combine with AND, and text filters apply within one language.

## Setup and configuration

Add the remote URL in the client’s MCP configuration. Cursor accepts a `url` entry, VS Code uses an HTTP server entry, and Gemini CLI-style configurations use `httpUrl`. Claude Code can register it with `claude mcp add --transport http legalize https://legalize.dev/mcp`. ChatGPT requires developer mode and a custom connector; its form does not receive the URL from the installation link, so the endpoint must be pasted manually.

Authentication requires sign-in. Subscription creation requires a paid plan, while pausing and deleting subscriptions remain available on any plan. Webhooks are HTTPS destinations, signed and delivered in daily batches; email digests are also daily and produce no message when nothing matches.

## Limitations and notes

The connector cannot modify legislation. Subscription creation returns a structured `feature_not_available` error when the account lacks the required feature, and no delivery is created. Webhook signing secrets are not returned by tools; they must be collected and rotated in the Legalize dashboard. Email digests cannot target an arbitrary address. Tool-level errors are returned inside a successful call as structured data so the client can respond to the stated issue.

_Full upstream README: https://allmcps.com/mcp/legalize-2/readme_