Global law
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
28 pay-per-event tools for regulatory, sanctions, procurement, and corporate-registry monitoring.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 4/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 24/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Delta Registry — Regulatory & Compliance Monitoring (28 tools)。按照 https://mcp.popnx.com/i/stefanoseggio-delta-registry.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.apify.com) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
打开 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 网站 ↗
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Delta Registry — Regulatory & Compliance Monitoring (28 tools)https://mcp.apify.com?tools=stefano_seggio/actor-18-b2b-lead-magnet,stefano_seggio/actor-19-maritime-sanctions-monitor,stefano_seggio/actor-20-mdb-procurement-monitor,stefano_seggio/actor-21-patent-ip-enforcement-monitor,stefano_seggio/actor-22-drug-safety-recalls-monitor,stefano_seggio/actor-24-cl…在 Request headers 下添加这个名称和值
AuthorizationBearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsDelta Registry — Regulatory & Compliance Monitoring (28 tools)
用 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Delta Registry — Regulatory & Compliance Monitoring (28 tools),或回答中出现 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Delta Registry — Regulatory & Compliance Monitoring (28 tools)
Delta Registry — Regulatory & Compliance Monitoring (28 tools) 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 的应用
B · 法律与政府数据 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code · 约 5 分钟
需要 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
打开 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 网站 ↗
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user delta-registry 'https://mcp.apify.com?tools=stefano_seggio/actor-18-b2b-lead-magnet,stefano_seggio/actor-19-maritime-sanctions-monitor,stefano_seggio/actor-20-mdb-procurement-monitor,stefano_seggio/actor-21-patent-ip-enforcement-monitor,stefano_seggio/actor-22-drug-safety-recalls-monitor,stefano_seggio/actor-24-cl…' --header 'Authorization: Bearer your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 在列表中并显示已连接
用 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Delta Registry — Regulatory & Compliance Monitoring (28 tools),或回答中出现 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
打开 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 网站 ↗
在 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Delta Registry — Regulatory & Compliance Monitoring (28 tools),或回答中出现 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
打开 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 网站 ↗
在 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Delta Registry — Regulatory & Compliance Monitoring (28 tools),或回答中出现 Delta Registry — Regulatory & Compliance Monitoring (28 tools) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.apify.com?tools=stefano_seggio/actor-18-b2b-lead-magnet,stefano_seggio/actor-19-maritime-sanctions-monitor,stefano_seggio/actor-20-mdb-procurement-monitor,stefano_seggio/actor-21-patent-ip-enforcement-monitor,stefano_seggio/actor-22-drug-safety-recalls-monitor,stefano_seggio/actor-24-cl…JSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user delta-registry 'https://mcp.apify.com?tools=stefano_seggio/actor-18-b2b-lead-magnet,stefano_seggio/actor-19-maritime-sanctions-monitor,stefano_seggio/actor-20-mdb-procurement-monitor,stefano_seggio/actor-21-patent-ip-enforcement-monitor,stefano_seggio/actor-22-drug-safety-recalls-monitor,stefano_seggio/actor-24-cl…' --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"delta-registry": {
"url": "https://mcp.apify.com?tools=stefano_seggio/actor-18-b2b-lead-magnet,stefano_seggio/actor-19-maritime-sanctions-monitor,stefano_seggio/actor-20-mdb-procurement-monitor,stefano_seggio/actor-21-patent-ip-enforcement-monitor,stefano_seggio/actor-22-drug-safety-recalls-monitor,stefano_seggio/actor-24-cl…",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"delta-registry": {
"type": "http",
"url": "https://mcp.apify.com?tools=stefano_seggio/actor-18-b2b-lead-magnet,stefano_seggio/actor-19-maritime-sanctions-monitor,stefano_seggio/actor-20-mdb-procurement-monitor,stefano_seggio/actor-21-patent-ip-enforcement-monitor,stefano_seggio/actor-22-drug-safety-recalls-monitor,stefano_seggio/actor-24-cl…",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}说明仍为英文原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日
注册名称已通过 GitHub 账户 stefanoseggio 验证,该账户拥有此仓库
代码最后更新于今天
使用 MIT
在 86 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/stefanoseggio-delta-registry)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于今天,最新版本(1.0.0)于2个月前进入注册中心。
支持 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.
| 本项 Delta Registry — Regulatory & Compliance Monitoring (28 tools) | Global law | Open Legal Data (Germany) | LibreJustice | InfraNode | Fedlex Connector | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | NOASSERTION | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The public marketing site for Delta Registry — architecture explainer, pricing overview, and delta-engine internals for the full fleet of pay-per-event Apify Actors. Built with the Next.js App Router, React 18, and Tailwind CSS.
npm install
npm run dev
Then open http://localhost:3000. npm run build && npm run start runs the production build; npm run typecheck and npm run lint run TypeScript and ESLint respectively.
app/ — Next.js App Router pages and layouts. app/page.tsx composes every section (Header, Hero, ArchitectureMatrix, HowItWorks, EconomicEngine, IntegrationTerminal, DeltaEngineDocs, FaqAccordion, Footer) in render order; there is no other route.components/ — one React component per site section. Sections that need interactivity (the fleet filter, the JSON delta-viewer playground, the accordion, the code-language tabs) are client components ('use client'); everything else renders on the server.lib/ — the site's data contract. lib/types.ts defines the Actor shape; lib/actors.ts exports the real ACTORS array plus derived constants (ACTOR_COUNT, DOMAINS, GITHUB_REPO_COUNT).middleware.ts — edge middleware for the deployed site.lib/actors.ts as the single source of truthEvery number, price, badge, and filter option rendered anywhere on this site — the hero stat counters, the fleet catalog cards, the pricing comparison table, the BYOK disclosure, the integration workbench's actor tabs, the FAQ's live counts — is read from the same ACTORS array in lib/actors.ts, never hand-typed a second time in a component. Each Actor record carries slug, title, domain, jurisdiction, dataSource, pricing[] (per-event-type price and unit), deltaEvents[], storeUrl, githubUrl, byok ('required' | 'optional' | 'none', plus byokDetail when applicable), updateFrequency, and isPublic.
This is deliberate, not incidental: it means a component can never drift out of sync with the real fleet, and every price or claim on this marketing site traces back to one file that's independently re-verified against each actor's own Apify Store listing and README whenever the fleet changes. When an actor's price changes or a new actor launches, updating lib/actors.ts is the only change needed — every section that references it (filters, cards, comparison tables, code snippets) updates automatically.
next.config.js sets standard hardening headers (X-Frame-Options: DENY, X-Content-Type-Options: nosniff, Strict-Transport-Security, a restrictive Permissions-Policy) globally. The Content-Security-Policy is set separately, per-request, in middleware.ts — not as a static header — because a static script-src 'self' blocks Next.js's own inline hydration/bootstrap scripts and breaks the app at runtime. Instead, middleware.ts generates a fresh nonce on every request, threads it to Next.js via the x-nonce request header (read in app/layout.tsx), and scopes the CSP to that nonce (script-src 'self' 'nonce- ' 'strict-dynamic') rather than falling back to 'unsafe-inline', which would defeat the policy's purpose. 'unsafe-eval' is included only when NODE_ENV === 'development' (webpack's Fast Refresh needs it) and is never present in the production CSP.
No compliance badges (SOC 2, ISO 27001, etc.) are displayed anywhere on this site — Delta Registry holds no such certification, and the headers above are genuine engineering hardening, not a marketing trust signal standing in for one.
None required. This is a fully static-data marketing site — it reads lib/actors.ts at build time and calls no external API, database, or authenticated service at runtime or during the build. npm install && npm run dev (or npm run build) works with no .env file. The APIFY_TOKEN references visible in this repo are inside display-only code-snippet strings in components/IntegrationTerminal.tsx — example commands shown to site visitors for calling the Apify API themselves, not a variable this app reads.
Deployed continuously on Vercel from the main branch.
Every actor in this fleet is callable today from Claude Code, Claude Desktop, or Cursor via Apify's own hosted MCP server — no custom integration, no SDK to install, no infrastructure to run. The full closed-scope endpoint (all 28 actors, none of Apify's other 70,000+ Store actors in scope), the exact verified client config for each tool, and the real per-tool BYOK/pricing/routing notes are in MCP_INTEGRATION.md.
To connect your own Claude Code or Cursor installation in one step, run the onboarding script for your platform — each one prompts you for your own Apify API token (never logged, never written in plaintext) and configures whichever client it finds installed:
# macOS / Linux / Git Bash on Windows
./connect_mcp.sh
# Windows PowerShell
.\connect_mcp.ps1
This exact end-to-end path — real config injection, then a real live tool call through the actual MCP wire protocol — was independently validated against a live actor run; see LOCAL_MCP_VALIDATION_REPORT.md for the real run ID, latency, and returned data from that test.
Delta Registry is a pay-per-event regulatory and compliance data infrastructure operation built and operated by Stefano Seggio — 28 Apify Actors spanning government procurement, regulatory enforcement, patent/trademark monitoring, sanctions/compliance screening, corporate registries, and sovereign debt markets. Browse the full Actor catalog on the Apify Store or GitHub. For enterprise licensing or a custom monitor, connect on LinkedIn.