Global law
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
One-step legal compliance for vibe-coded apps: privacy, terms, cookie banner and EU AI Act check.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Lexvibe。按照 https://mcp.popnx.com/i/marcosnovo-lexvibe.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(golexvibe.com) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Lexvibehttps://golexvibe.com/api/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsLexvibe
用 Lexvibe 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Lexvibe,或回答中出现 Lexvibe 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Lexvibehttps://golexvibe.com/api/mcp开启新聊天,输入前先从插件列表中选择 Lexvibe
用 Lexvibe 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Lexvibe,或回答中出现 Lexvibe 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user lexvibe https://golexvibe.com/api/mcp应能看到 Lexvibe 在列表中并显示已连接
用 Lexvibe 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Lexvibe,或回答中出现 Lexvibe 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Lexvibe 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Lexvibe,或回答中出现 Lexvibe 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Lexvibe 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Lexvibe,或回答中出现 Lexvibe 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://golexvibe.com/api/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user lexvibe https://golexvibe.com/api/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"lexvibe": {
"url": "https://golexvibe.com/api/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"lexvibe": {
"type": "http",
"url": "https://golexvibe.com/api/mcp"
}
}
}Claude Code
claude mcp add --scope user lexvibe -- npx -y @lexvibe/mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"lexvibe": {
"command": "npx",
"args": [
"-y",
"@lexvibe/mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"lexvibe": {
"command": "npx",
"args": [
"-y",
"@lexvibe/mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"lexvibe": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@lexvibe/mcp"
]
}
}
}LEXVIBE_APP_ID envLEXVIBE_API_URL envLEXVIBE_CDN_URL envLEXVIBE_EVENTS_URL envLEXVIBE_TELEMETRY 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月18日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
check_websiteFree legal-compliance check of a public website (no signup). Fetches the URL server-side and detects data processing relevant to compliance — analytics, marketing pixels, payments, generative AI, email collection, third-party sharing — then returns the legal documents and cookie-
check_storeFree legal-compliance check of a mobile app from its PUBLIC App Store (apps.apple.com) or Google Play (play.google.com) listing URL — no repo or developer-account access needed. Follows the privacy-policy link the developer declared on the listing, analyzes that page, and returns
generate_policiesGenerate the legal documents (privacy policy, terms of service and, if applicable, an AI disclosure) localized and tailored to the target markets (GDPR, UK GDPR, CCPA…). Returns Markdown drafts. Pass check_website's or check_store's suggestedAnswers as `answers` so the documents
check_ai_actClassify a product's risk level under the EU AI Act — minimal, limited, high or prohibited — and return the applicable obligations, each with its compliance deadline (limited-risk transparency duties apply from Aug 2, 2026; Annex III high risk from Dec 2, 2027). The boolean param
get_install_snippetReturn what to install for a LexVibe app id. For web: the one-line snippet (cookie banner with real script blocking + hosted policy links) to paste before , plus a JSX variant for React/Next.js layouts. For iOS/Android: the hosted privacy-policy URL and the exact App Store Connec
claim_appCreate a REAL LexVibe app in the user's account (replaces any YOUR_APP_ID placeholder). Returns a claim link: show it to the user so they can sign in and confirm — the link stays valid for 7 days, so the user can open it later. On confirmation LexVibe creates the app, scans the U
get_claim_statusCheck whether the user has confirmed a claim created with claim_app. While the user hasn't confirmed yet it returns {status: 'pending'} — wait a few seconds and call again (the link stays valid for 7 days). Once claimed it returns the REAL app id, the install snippet and the host
lookup_frameworkLook up a privacy or AI law by id and get structured, primary-sourced facts: full name, jurisdiction, effective date, applicability threshold, the documents it requires, the rights it grants, its cookie-consent regime, whether it requires honouring Global Privacy Control, key art
list_frameworksList every privacy and AI framework LexVibe generates documents against — 55 laws across 46 jurisdictions, including GDPR, ePrivacy, the EU AI Act, UK GDPR and PECR, Swiss nFADP, 17 US state privacy laws modelled individually (CCPA/CPRA among them), PIPEDA and Quebec Law 25, LGPD
applicable_frameworksGiven the markets a product serves, return every framework that applies, the documents it must publish, the strictest cookie-consent regime across those markets, and whether a universal opt-out signal (Global Privacy Control) has to be honoured. This is the read-only version of w
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 marcosnovo 验证,该账户拥有此仓库
代码最后更新于6天前
使用 MIT
在 159 毫秒内响应(HTTP 200)
无需登录
已读取 10 个工具描述,未发现针对 AI 的隐藏指令
OSV.dev 中没有 @lexvibe/mcp@1.0.4 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/marcosnovo-lexvibe)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于6天前,最新版本(1.0.4)于31天前进入注册中心。
支持 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.
| 本项 Lexvibe | 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、图片和脚本已被移除。链接会离开本站。
LexVibe MCP server — one-step legal compliance for vibe-coded apps (Lovable, Bolt, v0, Next.js, plain HTML). Wire it into your AI assistant (Claude Code, Claude Desktop, Cursor…) and it makes your app "legally ready" without you knowing the law: privacy policy, terms of service, cookie consent banner with real script blocking, and an EU AI Act risk check.
Not using an AI coding tool? The same checks run in the browser: paste your URL into the free website checker — no signup.
| Tool | What it does |
|---|---|
make_compliant | One step: scan → generate docs into /legal → install the banner snippet → classify EU AI Act risk. |
check_compliance | Read-only readiness report: what was detected, what could be auto-derived, and which human facts are still missing. Run it again after adding any SDK to catch drift. |
scan_project | Detect analytics, payments, generative AI, email collection, third parties and platforms (web / iOS / Android). |
check_website | Free, no-signup compliance check of a deployed site by URL: per-vendor signals, recommendations and EU AI Act applicability (the same public checker as /check). |
verify_snippet | Fetch a deployed URL and confirm the cookie-banner snippet is actually live in the served HTML (ok / missing / unknown). |
generate_policies | Generate privacy policy / terms / AI disclosure, localized and tailored per market. |
install_snippet | Insert the cookie-banner snippet before ; for JSX layouts it returns exact instructions instead. |
check_ai_act | Classify EU AI Act risk and list the applicable obligations with deadlines. |
claim_app | Create a REAL app in the user's LexVibe account: returns a link the user opens to sign in and confirm (valid 7 days). |
get_claim_status | Poll a claim created with claim_app; once confirmed it returns the real app id, install snippet and policy URL. |
"Make my app legally compliant for the EU and the US."
One make_compliant call: the agent scans the project, writes the localized policies to /legal, installs the cookie-banner snippet in your HTML head and returns the EU AI Act classification plus next steps. You just review and approve.
Draft-first flow: start with check_compliance — it reports what the scan could figure out on its own and returns an agentPrompt your coding agent can answer by reading the repo (company entity, contact email, target markets), so there are no forms to fill.
No app id yet? The agent calls claim_app and hands you a link: open it, sign in and confirm — that creates the real app in your LexVibe account (hosted, auto-updated policies and consent proof linked to you). The agent then picks up the real app id via get_claim_status and replaces any YOUR_APP_ID placeholder automatically.
Legal documents describe your app as it was when they were generated. Every SDK you add afterwards — payments, analytics, auth, AI — is a processing activity your documents don't cover yet. LexVibe calls this drift, and the MCP server is the sensor that lives inside your AI dev loop: the same assistant that adds the SDK can catch the compliance gap before you deploy.
Paste this standing rule into your assistant's project rules — AGENTS.md (Codex, Gemini CLI and most agents), CLAUDE.md, .cursorrules, .windsurfrules…:
After adding any SDK, analytics, payments, auth or AI integration to this
project, run LexVibe's
check_compliancetool and follow its
recommendation.
When check_compliance reports processing activities that were added after your documents were generated, re-run generate_policies (or make_compliant) so the documents disclose the new processing. The same applies to the deployed site: check_website detects the trackers that actually ship to visitors, so you can catch drift the local scan can't see (scripts injected by a CMS, a tag manager, a no-code platform…). Claimed apps are also watched by LexVibe's other drift sensors (periodic site rechecks and the GitHub integration), and the remote check_website tool additionally returns a drift section for claimed apps comparing the live site against the baseline the documents were generated from.
skills/lexvibe-compliance/SKILL.md is an Agent Skill that tells your coding agent _when_ to use this server (before a deploy, after adding an SDK) and how to report the result honestly. Drop the folder into your agent's skills directory — e.g. .claude/skills/ in Claude Code — next to the MCP server below.
npx -y @lexvibe/mcp # or build from source: npm run build -w packages/mcp
.mcp.json in your project, or claude mcp add){
"mcpServers": { "lexvibe": { "command": "npx", "args": ["-y", "@lexvibe/mcp"], "env": { "LEXVIBE_APP_ID": "your-app-id" } } } }
~/.cursor/mcp.json){
"mcpServers": { "lexvibe": { "command": "npx", "args": ["-y", "@lexvibe/mcp"], "env": { "LEXVIBE_APP_ID": "your-app-id" } } } }
Claude Desktop uses the same mcpServers structure in claude_desktop_config.json.
~/.codex/config.toml)Codex is the one client that does not use the mcpServers JSON above — its config is TOML:
codex mcp add lexvibe -- npx -y @lexvibe/mcp
Or by hand:
[mcp_servers.lexvibe]
command = "npx" args = ["-y", "@lexvibe/mcp"] env = { LEXVIBE_APP_ID = "YOUR_APP_ID" }
Project-scoped config lives in .codex/config.toml (trusted projects only).
~/.gemini/settings.json)Same mcpServers shape as Cursor. For the remote server use httpUrl, not url: in Gemini CLI url means SSE, and this endpoint speaks Streamable HTTP only, so url fails without saying why.
{
"mcpServers": { "lexvibe": { "httpUrl": "https://golexvibe.com/api/mcp" } } }
Browser-based agents that cannot run local processes — claude.ai / Claude Desktop connectors, ChatGPT connectors — can use the hosted remote server instead (Streamable HTTP, no auth):
https://golexvibe.com/api/mcp
The remote server has no filesystem access, so it exposes the remote-safe subset: check_website, check_store, generate_policies (template-based drafts, capped for anonymous callers), check_ai_act, get_install_snippet, plus claim_app / get_claim_status to create a real app in the user's account. Stdio-only clients can bridge to it with npx -y mcp-remote https://golexvibe.com/api/mcp.
| Platform | Integration | How |
|---|---|---|
| Claude Code | stdio (or remote) | claude mcp add lexvibe -- npx -y @lexvibe/mcp |
| Cursor / Windsurf / Cline / VS Code | stdio | mcpServers config with npx -y @lexvibe/mcp |
| Codex CLI | stdio (or remote) | codex mcp add lexvibe -- npx -y @lexvibe/mcp |
| Gemini CLI | stdio (or remote) | mcpServers in ~/.gemini/settings.json |
| Zed | stdio (or remote) | context_servers in settings.json |
| Claude Desktop / claude.ai | remote | Settings → Connectors → https://golexvibe.com/api/mcp |
| ChatGPT | remote | Settings → Connectors → https://golexvibe.com/api/mcp |
| Lovable / Bolt / v0 / Base44 / Replit | prompt (no MCP) | Paste the one-liner from https://golexvibe.com/prompt |
Full per-platform setup guide: https://golexvibe.com/docs/integrations
| Variable | Default | Purpose |
|---|---|---|
LEXVIBE_APP_ID | YOUR_APP_ID | Your LexVibe app id (links the snippet to your hosted policies) |
LEXVIBE_API_URL | https://golexvibe.com | LexVibe instance that generates documents and classifies AI risk |
LEXVIBE_CDN_URL | https://golexvibe.com | Host the widget script is served from (self-hosting only) |
LEXVIBE_EVENTS_URL | LexVibe events endpoint | Override where anonymous tool-usage events are sent (self-hosting) |
LEXVIBE_TELEMETRY | 1 | Set to 0 / false / off to disable usage telemetry |
Each tool call sends one anonymous mcp_tool_call event to LexVibe so your MCP usage shows up alongside your website in the Platform analytics dashboard (same event the hosted remote server already records, tagged source: "mcp_stdio" so the two channels are distinguishable).
LEXVIBE_APP_ID is a real app id (a valid UUID) — that app id, so the events map to your app. Placeholders like your-app-id are ignored. Never your file paths, file contents, app name, emails or generated documents.LEXVIBE_TELEMETRY=0 (or the de-facto DO_NOT_TRACK=1) to turn it off completely.Side effects:
scan_project,check_compliance,check_website,
verify_snippet,check_ai_actandget_claim_statusare read-only
(
check_website, the AI Act check and the claim poll call the LexVibe API;
verify_snippetfetches the URL you pass it — public http(s) hosts only,
with the same anti-SSRF validation the platform uses).
generate_policiescalls the API and returns Markdown.
install_snippetedits one file on your local filesystem (only when it
contains
).make_compliantdoes both: it calls the API and
writes files (
/legal/*.mdplus the snippet in your HTML head).
claim_appcreates a pending claim in LexVibe; the app itself is only
created when the user confirms the link while signed in.
-