get_claim_status

MCP tool from Lexvibe MCP by marcosnovo

Poll a claim created with claimapp; once confirmed it returns the real app id, install snippet and policy URL.

How to use it

get_claim_status is exposed by the Lexvibe MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the get_claim_status tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

Install Lexvibe MCP

$npx -y @lexvibe/mcp # or build from source: npm run build -w packages/mcp

FULL LEXVIBE MCP LISTING

Other tools in Lexvibe MCP (9)

check_ai_act

Classify EU AI Act risk and list the applicable obligations with deadlines.

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.

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).

claim_app

Create a REAL app in the user's LexVibe account: returns a link the user opens to sign in and confirm (30 min).

generate_policies

Generate privacy policy / terms / AI disclosure, localized and tailored per market.

install_snippet

Insert the cookie-banner snippet before </head>; for JSX layouts it returns exact instructions instead.

make_compliant

One step: scan → generate docs into /legal → install the banner snippet → classify EU AI Act risk.

scan_project

Detect analytics, payments, generative AI, email collection, third parties and platforms (web / iOS / Android).

verify_snippet

Fetch a deployed URL and confirm the cookie-banner snippet is actually live in the served HTML (ok / missing / unknown).