Skip to content
External endpointresponds

lexvibe

One-step legal compliance for vibe-coded apps: privacy, terms, cookie banner and EU AI Act check.

Endpoint URL
https://golexvibe.com/api/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:02 AM UTC
Check
MCP initialize · 8s limit
Latency
441 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.marcosnovo/lexvibe

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
lexvibe
Version
0.1.9
Capability keys
tools
Tool names
check_website, check_store, generate_policies, check_ai_act, get_install_snippet, claim_app, get_claim_status, lookup_framework, list_frameworks, applicable_frameworks
Instructions excerpt

LexVibe makes vibe-coded apps (Lovable, Bolt, v0, Next.js, plain HTML) legally compliant: GDPR privacy policy, terms of service, cookie consent banner with real script blocking, and EU AI Act risk classification. This is the REMOTE server (no filesystem access): use check_website or check_store to analyze a live site or store listing, generate_policies for localized document drafts, check_ai_act to classify EU AI Act risk, and get_install_snippet for the exact install steps. To create a REAL app in the user's account (real app id instead of YOUR_APP_ID, hosted + auto-updated policies), call claim_app — it returns a link the user opens to confirm — then poll get_claim_status. Legal documents describe the app as it was when they were generated: after adding any SDK, analytics, payments, auth or AI integration, run check_website again — for claimed apps it returns a drift section listing processing the hosted documents don't cover yet, with a recommendation to regenerate. For local-

Reported Aug 17, 2026, 05:02 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 239ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 1,263ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 1,087ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 441ms