verify_snippet
Fetch a deployed URL and confirm the cookie-banner snippet is actually live in the served HTML (ok / missing / unknown).
How to use it
Project documentation lists verify_snippet for the Lexvibe MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install Lexvibe MCP
npx -y @lexvibe/mcp # or build from source: npm run build -w packages/mcpOther tools in Lexvibe MCP (9)
Classify EU AI Act risk and list the applicable obligations with deadlines.
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.
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).
Create a REAL app in the user's LexVibe account: returns a link the user opens to sign in and confirm (30 min).
Generate privacy policy / terms / AI disclosure, localized and tailored per market.
Poll a claim created with claimapp; once confirmed it returns the real app id, install snippet and policy URL.
Insert the cookie-banner snippet before </head>; for JSX layouts it returns exact instructions instead.
One step: scan → generate docs into /legal → install the banner snippet → classify EU AI Act risk.
Detect analytics, payments, generative AI, email collection, third parties and platforms (web / iOS / Android).