Legalithm Mcp Server
- Updated June 18, 2026
- legalithm/legalithm
Legalithm Mcp Server is an offline MCP server that classifies EU AI Act risk, cites obligations, drafts Article 50 transparency text, and checks compliance records for developers shipping AI features to EU users.
About
Legalithm brings EU AI Act compliance into the coding loop through an offline MCP server (legalithm-mcp-server) and a CLI with setup, init, and check commands. Four MCP tools—classify, explain_obligation, generate_disclosure, and check_record—run without an API key or network, checking outputs against Regulation (EU) 2024/1689. Running npx legalithm init writes compliance/legalithm.json recording your system's risk tier and cited obligations, while npx legalithm check fails CI on drift when the app or law changes. A GitHub Action enforces the committed record on pull requests. Legalithm explicitly frames outputs as a cited starting point for human legal review—not certification. Reach for it when shipping AI features to EU users and you need editor-time risk classification plus a versioned compliance artifact in the repo.
- Offline MCP tools: classify, explain_obligation, generate_disclosure, check_record—no API key
- npx legalithm init writes dated compliance/legalithm.json with risk tier and cited obligations
- npx legalithm check exits non-zero on compliance drift for CI pipelines
- GitHub Action validates committed compliance record on pull requests
Legalithm Mcp Server by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add legalithm-mcp-server -- npx -y legalithm-mcp-serverAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | legalithm-mcp-server |
|---|---|
| Transport | STDIO |
| Auth | None |
| Last updated | June 18, 2026 |
| Repository | legalithm/legalithm ↗ |
How do you check EU AI Act compliance in your editor?
Classifies EU AI Act risk tier, cites obligations, drafts Article 50 disclosure text, and writes compliance/legalithm.json via offline MCP tools and CLI check.
Who is it for?
Developers shipping AI features to EU users who need offline risk classification, obligation citations, and CI-verified compliance records.
Skip if: Non-AI applications outside EU regulatory scope or teams requiring certified legal advice instead of a cited starting point.
What you get
Dated compliance/legalithm.json record, risk-tier classification, cited obligation references, and Article 50 disclosure draft text.
- compliance/legalithm.json
- Article 50 disclosure draft
- CI compliance gate
By the numbers
- Exposes 4 offline MCP tools
- Article 50 transparency from Aug 2026; high-risk obligations from Dec 2027
Recommended MCP Servers
1Claw VaultHSM-backed vault secrets for AI agents (JIT fetch) plus prompt-injection and threat scanning.2
1passwordMCP server for 1Password service accounts — tools and resources for vaults and credentials18
402sentinel McpAssess an x402 counterparty's risk BEFORE paying: allow/review/block, scored on-chain (Base).1
A2adependencyinspector McpRemote MCP for A2A dependency inspector MCP, structured receipts, audit logs, and reviewer-ready evi
A2a Governance Bridge McpA2A Governance Bridge MCP server.A2aidentitytoll McpRemote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.How it compares
Use Legalithm for EU AI Act risk tiers and Article 50 drafts in-editor; use general security scanners when the concern is CVEs rather than AI regulation.
FAQ
Does Legalithm Mcp Server require an API key or network?
Legalithm Mcp Server runs fully offline with no API key and no network. Install via `npx -y legalithm-mcp-server` in Claude Code or Cursor MCP config alongside the Legalithm CLI.
Which MCP tools does Legalithm expose?
Legalithm Mcp Server exposes four tools: classify for AI system risk tier, explain_obligation for cited EU AI Act duties, generate_disclosure for Article 50 text, and check_record to validate the committed compliance file.
How does Legalithm integrate with CI pipelines?
Legalithm writes compliance/legalithm.json on init and `npx legalithm check` exits non-zero when the record drifts. A GitHub Action runs on pull requests to fail builds when the app or law changes under you.