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.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 8/8 | The cloud endpoint answered at the last check |
| Usage score | 20/100 |
Quality: Passed 5/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Lexvibe. Follow https://mcp.popnx.com/i/marcosnovo-lexvibe.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (golexvibe.com) · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Lexvibehttps://golexvibe.com/api/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsLexvibe
Use Lexvibe and tell me what you can do for me, then show me one thing✓ If Claude says it is using Lexvibe or shows a Lexvibe tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Lexvibehttps://golexvibe.com/api/mcpStart a new chat and pick Lexvibe from your plugins before typing
Use Lexvibe and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Lexvibe or shows a Lexvibe tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user lexvibe https://golexvibe.com/api/mcpYou should see Lexvibe listed as connected
Use Lexvibe and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Lexvibe or shows a Lexvibe tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use Lexvibe and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Lexvibe or shows a Lexvibe tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use Lexvibe and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Lexvibe or shows a Lexvibe tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://golexvibe.com/api/mcpJSON settings are under “For developers” below
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 envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @lexvibe/mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Tool names and descriptions exactly as the server reported them on Nov 18, 2026. The maker wrote them, not us; we show them as plain text.
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
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account marcosnovo, which owns the repo
Code last changed 6 days ago
Uses MIT
Responded in 159 ms (HTTP 200)
No sign-in needed
Read 10 tool descriptions and found no hidden instructions to the AI
No entries on OSV.dev for @lexvibe/mcp@1.0.4
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/marcosnovo-lexvibe)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed 6 days ago, and the latest version (1.0.4) reached the registry 31 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
| This one Lexvibe | Global law | Open Legal Data (Germany) | LibreJustice | InfraNode | Fedlex Connector | |
|---|---|---|---|---|---|---|
| Runs where | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | NOASSERTION | MIT | Apache-2.0 | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
-