Legalithm Mcp Server

io.github.legalithm由 GitHub 帳號 legalithm 發布v0.1.2更新於 Oct 24, 2026

EU AI Act compliance in your editor: classify risk, cite obligations, draft Article 50 text.

已驗證STDIO僅桌面開發者工具安全與監控

概覽

AI 產生的概覽

一個離線 MCP 伺服器,協助助理判定 AI 功能的歐盟 AI 法案風險等級、引用相關義務,並草擬第 50 條透明度文字。

可以做什麼
對 AI 系統進行歐盟 AI 法案風險分級,提供引用的條文與附件、命中的規則、信心分數與適用期限,不確定時標記需人工複核。說明分級背後的義務,包括義務數量與主要義務標題。草擬第 50 條要求的 AI 生成內容揭露文字。對照公開 API 檢查合規紀錄。
適用情境
適合在向歐盟使用者發布 AI 功能時,於編輯器內快速取得有引用的風險等級與透明度義務起點,或草擬第 50 條揭露文字。它只是有引用的起點,不構成法律意見或認證。
執行需求
以 stdio 在本機執行,通常透過 npx 使用 npm 套件 legalithm-mcp-server;離線工具不需 API 金鑰。check_record 工具會讀取公開 API,因此需要網路存取。獨立 CLI 的 mark 與 verify 指令需要選用的原生相依套件。
安裝前請注意
輸出只是有引用的起點,不構成法律意見,也不是認證;低於棄權門檻的結果會被標記為需人工複核。check_record 工具會存取公開 API。獨立 CLI 的 init 與 check 指令需要免費 API 金鑰並連線至託管紀錄服務;GitHub Action 範例以密鑰形式傳入金鑰。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Legalithm Mcp Server,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Legalithm — EU AI Act compliance in your coding loop

[npm version] [Add to Cursor]

Shipping an AI feature to EU users? Article 50 transparency duties have applied since 2 August 2026. Content marking for systems placed before that date is due 2 December 2026, and Annex III high-risk obligations follow on 2 December 2027. Catch it where you code, in seconds.

[Source code on the left, connected by four branching lines to a sealed legal document on the right.]

This image is AI-generated, and it is marked as such with our own tool: legalithm mark --watermark added a C2PA content credential and a pixel watermark, which is what Article 50(2) asks for. Download it and run legalithm verify on it. The credential is signed with the CLI's test certificate, so it is valid but not trust-listed.

Quickstart

Install the offline server in your editor. No API key, and nothing leaves your machine.

bash
claude plugin marketplace add legalithm-org/legalithmclaude plugin install legalithm@legalithm

Codex:

bash
codex plugin marketplace add legalithm-org/legalithmcodex plugin add legalithm@legalithm

Cursor: use the Add to Cursor badge above.

Then ask your agent "does the EU AI Act apply to this feature, and what tier?"

What comes back (real output, CV screening as the provider)
json
{  "risk": "high",  "confidence": "high",  "rationale": "This AI system is classified as high-risk under Article 6(2) as it falls into the category of Employment, Workers Management and Access to Self-employment as specified in Annex III...",  "citations": [    {      "article": "6(2)",      "annex": "III",      "label": "Article 6(2) & Annex III - High-Risk AI Systems",      "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202401689#article-6",      "asOf": "2026-08-03",      "appliesFrom": "2027-12-02"    }  ],  "matchedRules": ["high_risk_employment", "high_risk_domain_selected"],  "applicableDeadline": "2027-12-02",  "obligationsHint": {    "count": 10,    "topTitles": [      "Quality Management System (Article 17)",      "Data Governance (Article 10)",      "Technical Documentation (Article 11)",      "Human Oversight (Article 14)"    ]  },  "confidenceScore": 0.72,  "reviewRequired": false}

Note matchedRules, asOf and confidenceScore. You can see which rule fired, how old the corpus is, and how sure the engine was. Below the abstention threshold it sets reviewRequired and tells you to get a human instead of guessing.

Content marking for Article 50(2), also no key:

bash
npm i -g legalithmlegalithm mark ./out.png --watermark   # writes out.signed.pnglegalithm verify ./out.signed.png      # detect both layers

Install it rather than using npx for these two: C2PA and the watermark come from c2pa-node and sharp, which are optional native dependencies that npx does not reliably fetch. Without them mark warns and marks nothing. Everything else in this README works fine under npx.

The compliance record (needs a free key)

bash
npx legalithm setup   # wires hooks, editor rule and MCP confignpx legalithm init    # writes a dated, cited compliance/legalithm.jsonnpx legalithm check   # re-verify; non-zero exit on drift (for CI)

init and check talk to the hosted record service, so they need a free API key. Everything above this line does not.

Three surfaces

  1. Editor — an offline MCP server (legalithm-mcp-server) exposing 4 tools (classify, explain_obligation, generate_disclosure, check_record). No API key. The first three run fully offline; check_record reads a public API.
  2. Repo — legalithm init writes a dated, cited compliance/legalithm.json that records your AI system's risk tier and the obligations behind it.
  3. CI — legalithm check and the GitHub Action fail the build when the committed record drifts — because your app changed or the law changed under you.

MCP config

Add the offline server to Claude Code, Cursor or Codex manually:

json
{  "mcpServers": {    "legalithm": {      "command": "npx",      "args": ["-y", "legalithm-mcp-server"]    }  }}

GitHub Action

yaml
# .github/workflows/ai-act.ymlname: AI Acton: [pull_request]jobs:  ai-act:    runs-on: ubuntu-latest    steps:      - uses: actions/checkout@v4      - uses: legalithm-org/legalithm/packages/action@v1        with:          api-key: ${{ secrets.LEGALITHM_API_KEY }}

Honest framing

A cited starting point that tells you when to get a human — not legal advice. When unsure, it flags the result for review instead of guessing. Every output is checked against Regulation (EU) 2024/1689; it is not a certification.

Links

License

MIT

來源:README.md,提交 4c5717e

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.2最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分