Global law
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
International legal analysis (ISO 31000) — 27 tools, 63 selectable jurisdictions; coverage varies.
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 6/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 21/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Nexus Legal。按照 https://mcp.popnx.com/i/djtellado-nexus-legal.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(legal.nexusquantum.legal) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Nexus Legalhttps://legal.nexusquantum.legal/api/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsNexus Legal
用 Nexus Legal 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Nexus Legal,或回答中出现 Nexus Legal 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Nexus Legalhttps://legal.nexusquantum.legal/api/mcp开启新聊天,输入前先从插件列表中选择 Nexus Legal
用 Nexus Legal 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Nexus Legal,或回答中出现 Nexus Legal 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user nexus-legal https://legal.nexusquantum.legal/api/mcp应能看到 Nexus Legal 在列表中并显示已连接
用 Nexus Legal 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Nexus Legal,或回答中出现 Nexus Legal 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Nexus Legal 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Nexus Legal,或回答中出现 Nexus Legal 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Nexus Legal 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Nexus Legal,或回答中出现 Nexus Legal 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://legal.nexusquantum.legal/api/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user nexus-legal https://legal.nexusquantum.legal/api/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"nexus-legal": {
"url": "https://legal.nexusquantum.legal/api/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"nexus-legal": {
"type": "http",
"url": "https://legal.nexusquantum.legal/api/mcp"
}
}
}Claude Code
claude mcp add --scope user nexus-legal --env NEXUS_API_KEY=your-value -- npx -y @nexus-legal/mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"nexus-legal": {
"command": "npx",
"args": [
"-y",
"@nexus-legal/mcp"
],
"env": {
"NEXUS_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"nexus-legal": {
"command": "npx",
"args": [
"-y",
"@nexus-legal/mcp"
],
"env": {
"NEXUS_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"nexus-legal": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@nexus-legal/mcp"
],
"env": {
"NEXUS_API_KEY": "your-value"
}
}
}
}NEXUS_API_KEY 机密 必填 envNEXUS_BASE_URL envNEXUS_TIMEOUT_MS env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 djtellado 验证,该账户拥有此仓库
代码最后更新于2个月前
使用 Apache-2.0
在 517 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
云端地址最近 6 次检查中有 6 次响应 · 最近一次 517 ms · 检查于 2026年11月20日
OSV.dev 中没有 @nexus-legal/mcp@0.6.3 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/djtellado-nexus-legal)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:NEXUS_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于2个月前,最新版本(0.6.3)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
German court decisions (Rechtsprechung) and laws (Gesetze) with citation graph and citation checks.
Search French-language and European case law and French legal texts (codes, statutes, treaties).
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.
Search Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint.
| 本项 Nexus Legal | Global law | Open Legal Data (Germany) | LibreJustice | InfraNode | Fedlex Connector | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | Apache-2.0 | NOASSERTION | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP (Model Context Protocol) server for Nexus Legal — exposes 27 specialised legal capabilities to Claude Desktop, Claude Code, Cursor and any other MCP-compatible client.
What is this? Connect your Claude to Nexus in 30 seconds. From then on Claude can run ISO 31000 legal analysis, Monte Carlo litigation simulation, case-law search, legal drafting, administrative doctrine, adversarial red teaming, multi-jurisdiction comparison (cross-border), citation verification, procedural time-limit computation, the statute↔case-law citation graph, and analysis of Box files by
file_id(box_analyze) — without leaving the conversation.
Go to legal.nexusquantum.legal/developers, choose "MCP server", give it a name (e.g. "personal MacBook") and press + Create MCP key. Copy the nlk_... key — it is shown only once.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": { "nexus-legal": { "command": "npx", "args": ["-y", "@nexus-legal/mcp"], "env": { "NEXUS_API_KEY": "nlk_YOUR_KEY_HERE" } } } }
Restart Claude Desktop. You will see a 🔌 icon in the chat with the 27 Nexus tools available.
Edit %APPDATA%\Claude\claude_desktop_config.json with the same contents.
claude mcp add nexus-legal -- npx -y @nexus-legal/mcp
export NEXUS_API_KEY=nlk_YOUR_KEY_HERE
Edit ~/.cursor/mcp.json:
{
"mcpServers": { "nexus-legal": { "command": "npx", "args": ["-y", "@nexus-legal/mcp"], "env": { "NEXUS_API_KEY": "nlk_YOUR_KEY_HERE" } } } }
In Claude Desktop, type:
Analyse this contract with Nexus in jurisdiction GB, commercial branch, conservative profile: «[paste the contract text here]»
Claude will call the nexus_analyze tool and return the report with certainty locks [L1]/[L2-J]/[L3-NV]/[L4], blocking signals [L5-C]/[L5-P], and a NEXUS-AUDIT-TRAIL block.
| Tool | Capability | Typical cost |
|---|---|---|
nexus_analyze | Full legal analysis (Node A — ISO 31000) | 1-3 credits |
nexus_consulta | Open legal question, with or without a document | 1 credit |
nexus_draft | Legal drafting (appeal, claim, defence, clause…) | 2-4 credits |
nexus_audit | Cross-audit of a Node A analysis (Node B) | 1-2 credits |
nexus_consensus | Multi-agent consensus Node A ↔ Node B (analysis + adversarial audit in a loop until consensus; jurisdiction required; long operation ~3-6 min) | 3-7 credits |
nexus_monte_carlo | Monte Carlo scenario simulation (ISO 31000 §6) | 4 credits |
nexus_doctrina | Administrative doctrine search, by jurisdiction | 1 credit |
nexus_opinion | Multi-LLM second opinion on a previous analysis | 2 credits |
nexus_redteam | Adversarial red team (vulnerabilities as structured JSON) | 5 credits |
nexus_adversarial | Adversarial argument in prose over a previous analysis | 2-3 credits |
nexus_cross_border_compare | Multi-jurisdiction comparison (2-15 jurisdictions) | 2-4 credits |
nexus_jurisprudencia_search | Semantic search over the multi-jurisdiction case-law corpus | requires balance + the case-law add-on for that jurisdiction |
verify_cita | Deterministic verification of one citation (judgment or provision) against the official corpus | requires balance (+ case-law add-on if the citation is case law) |
plazos_calcular | Procedural time limits by forum. jurisdiction is required, no default: ES (LEC + LOPJ, CGPJ/regional holidays, August non-working) or GB-EAW (CPR r 2.8, *clear days*, England and Wales bank holidays, no August recess). Scotland and Northern Ireland are rejected: their rules and their holidays are different | requires balance |
cruce_normativa_jurisprudencia | Citation graph: provisions ↔ judgments | requires balance + case-law add-on |
box_analyze | Analysis of a Box file by file_id (requires an active Box connection) | 1-2 credits |
nexus_verificacion | Verification Centre: checks EVERY citation in a document against the official corpus (deterministic, no LLM cost) | requires balance |
nexus_playbook | Strategic negotiation playbook over a previous analysis | 2-3 credits |
nexus_compare_versions | Comparison of two versions of a document (V1 ↔ V2) | 2 credits |
nexus_conflict_check | Conflict check (conflicts of interest) over the parties to a case file | 1 credit |
nexus_inbox | Firm-wide attention inbox (what needs action) | requires balance |
nexus_chat | Legal chat with the case context | 1 credit |
nexus_normativa_search | Semantic search over legislation in force | requires balance + the legislation add-on for that jurisdiction |
nexus_normativa_articulo | Literal text of a provision at a date (lex temporis) | requires balance + legislation add-on |
nexus_normativa_pyramid | Legislative hierarchy: coverage by level | requires balance |
nexus_corpus_coverage | Inventory of the case-law corpus | read-only |
nexus_normativa_coverage | Legislation corpus coverage (jurisdictions + freshness) | read-only |
Billing: the MCP server is not free. Every call requires an account with a credit balance > 0 (paid from minute one). Premium content is per jurisdiction add-on: case law and extra legislation are add-ons (Layer 3) — the subscription includes the legislation of one jurisdiction. Without the matching add-on, searches and lookups for that jurisdiction return
403 CONTENT_NOT_ENTITLED.
On jurisdictions and coverage. 63 jurisdiction codes are selectable (GB, ES, CO, SG, US with the US-CA/US-NY/US-DE/US-TX state overlays, MULTI for cross-border, and others). Selectable is not the same as grounded: what corpus actually backs a given jurisdiction — how many provisions, when our copy was last written, whether search is enabled for it — varies, and it is not something to infer from this list. Call nexus_normativa_coverage with your key: it answers for the jurisdictions your account has active, with the figures of each. A jurisdiction with no grounding corpus still analyses, but without literal citation against an official source.
Some accounts are provisioned so that legal generation runs only on the firm's own LLM engine, with no fallback chain. That is not a limitation: it is the guarantee that documents never reach a Nexus engine.
While no provider is registered and enabled, every generative tool (nexus_analyze, nexus_consulta, nexus_chat, nexus_draft, nexus_audit, nexus_adversarial, nexus_redteam, nexus_doctrina, nexus_consensus, nexus_monte_carlo, nexus_opinion, nexus_playbook, nexus_compare_versions, nexus_cross_border_compare, box_analyze) returns:
Error running nexus_analyze: BYO_PROVIDER_REQUIRED: This account requires its own
BYO LLM engine for AI-generative endpoints … This is a configuration state, not a transient failure — retrying returns the same 409. Register and enable a provider via POST /api/v1/llm-providers, then retry.
Retrying does not fix it, and no credits are charged for a run that stops there. Register the engine once (POST /api/v1/llm-providers, or header → AI models in the application) and run it again.
If your engine is a reasoning model (DeepSeek V-pro, o1-style, Claude 5 with thinking), a heavy analysis can take longer than a synchronous HTTP request is allowed to last. The gateway closes the connection at 300 s — that ceiling is ours to live with, not to raise.
MEASURED on 2026-08-18: nexus_analyze in mode: "auditoria" over a ~5 KB contract, on a BYO DeepSeek engine, went past it and returned 502. The reason is not a fault in your engine: a reasoning model spends a large part of its completion budget thinking before it writes, and when it runs out mid-thought Nexus automatically re-issues the call with a wider budget — which costs more wall clock again.
Two ways round it, in order of preference:
POST /api/v1/jobs with kind: "analyze" returns 202 and a jobId you poll (or a signed webhook). No wall clock. This is the right door for reasoning engines and for auditoria on large documents.mode: "standard" through the MCP tool, which is materially shorter.Platform engines and mode: "standard" are unaffected: the synchronous tool is the right one there and stays the default.
Read-only tools work without an engine, because they generate nothing: nexus_jurisprudencia_search, verify_cita, nexus_verificacion, nexus_normativa_search / _articulo / _pyramid, nexus_corpus_coverage, nexus_normativa_coverage, cruce_normativa_jurisprudencia, plazos_calcular, nexus_conflict_check (deterministic name matching, no LLM) and nexus_inbox.
| Variable | Default | Description |
|---|---|---|
NEXUS_API_KEY | — | Required. An nlk_... key with mcp scope. |
NEXUS_BASE_URL | https://legal.nexusquantum.legal | For test or self-hosted environments. |
NEXUS_TIMEOUT_MS | 180000 (3 min) | Timeout for long analyses. |
Language. This package sends the same tool descriptions to every client — MCP publishes them once, in tools/list, and no tool here takes a language argument — so descriptions and rendered output are in English. Where a tool produces a legal deliverable, the language of that deliverable follows the jurisdiction and the account, not this README.
You can name the role and the party in your own terms. professionalRole takes lawyer, solicitor, barrister, prosecutor, notary, registrar, judge, in-house and individual. proceduralSide takes the term your forum actually uses: claimant (England and Wales, CPR r 2.3), pursuer (Scotland), plaintiff (Northern Ireland, which did not adopt the CPR), defendant, defender. The original Spanish wire values — abogado, demandante, auditoria — are unchanged and will keep working: this adds spellings, it does not retire any. Everything resolves to the same protocol value before it reaches the analysis, so the two are interchangeable in every call.
API version: this server speaks to the Nexus v1 API, the same one used by the TypeScript and Python SDKs. Read-only and verification tools call /api/v1/* routes; generative ones enter through the backend node routes with the same nlk_ key (mcp scope), the same billing and the same BYO enforcement.
This stdio package exposes 27 of the catalogue's capabilities. The remote connector (https://legal.nexusquantum.legal/api/mcp, nothing to install) also exposes the case-file, firm-memory, firm-governance, legal-analytics, account and billing capabilities. If you need any of those, use the remote connector or the v1 API directly.
[DNI_1], [ACCOUNT_3]…). The MCP client only ever sees output already re-identified by our pipeline.