# io.github.marcosnovo/lexvibe (remote · golexvibe.com)

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

- Trust score: 73/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `golexvibe.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/marcosnovo-lexvibe/api-mcp.md), [page](https://verifymcp.io/servers/marcosnovo-lexvibe/api-mcp)
- npm · `@lexvibe/mcp`: 65/100, [markdown](https://verifymcp.io/servers/marcosnovo-lexvibe/lexvibe-mcp.md), [page](https://verifymcp.io/servers/marcosnovo-lexvibe/lexvibe-mcp)

## Channel facts

- Endpoint: `https://golexvibe.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3245 tokens (~324/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http marcosnovo-lexvibe https://golexvibe.com/api/mcp
```

### Codex

```toml
[mcp_servers.marcosnovo-lexvibe]
url = "https://golexvibe.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marcosnovo-lexvibe": {
      "type": "remote",
      "url": "https://golexvibe.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add marcosnovo-lexvibe --url https://golexvibe.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  marcosnovo-lexvibe:
    url: "https://golexvibe.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "marcosnovo-lexvibe": {
      "type": "http",
      "url": "https://golexvibe.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 73, 0)

- [cosmetic] “claim_app” added an optional parameter “aiAct”

### 2026-08-02 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 72, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 282 → 319
- [functional regression] Schema quality: 282 → 316
- [functional regression] Schema quality: 282 → 347
- [functional] Server version: 0.1.8 → 0.1.9
- [functional] New tool “applicable_frameworks”
- [functional] New tool “list_frameworks”
- [functional] New tool “lookup_framework”
- [cosmetic] “claim_app” reworded the description of “url”
- [cosmetic] “claim_app” reworded the description of “markets”

### 2026-07-29 (score 67, +1)

- [functional] Server version: 0.1.7 → 0.1.8

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (10)

### `check_website` (~358 tokens)

Check website compliance

Free 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-consent setup the site needs, whether the EU AI Act applies, and suggestedAnswers you can pass straight to generate_policies. Result contract: `fetched` is true only when the page HTML was actually read; when false, `fetchError` says why ("unreachable": the URL could not be resolved or connected; "blocked": the server answered with an error status) and the detected signals are NOT meaningful — report the check as inconclusive, not as clean. Run it again after adding any SDK, analytics, payment, auth or AI integration: when an appId is passed (or read from the installed LexVibe snippet) the result ALWAYS includes a `drift` key — status "in_sync", "outdated" (listing processing the hosted legal documents don't cover yet) or "unavailable" with a bounded `reason` (no-database, app-not-found, no-baseline, domain-mismatch, page-not-fetched) when the comparison could not be made; treat "unavailable" as unknown, never as in sync. Read-only.

Input parameters:

- `appId` (string): Optional LexVibe app id of a claimed app. When provided (or when the page already carries the installed LexVibe snippet), the result includes a drift report comparing the current site against the bas…
- `url` (string, required): Website URL or bare domain, e.g. https://myapp.com or myapp.com.

### `check_store` (~131 tokens)

Check app-store listing compliance

Free 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 detected data processing, compliance recommendations, whether the EU AI Act applies, and suggestedAnswers for generate_policies. Read-only.

Input parameters:

- `url` (string, required): App Store or Google Play listing URL, e.g. https://apps.apple.com/app/id123456789 or https://play.google.com/store/apps/details?id=com.example.app.

### `generate_policies` (~250 tokens)

Generate legal documents

Generate 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 disclose the right processing. Anonymous remote generation is template-based and capped at 3 locales; AI-tailored, hosted and auto-updated documents require a LexVibe account (https://golexvibe.com).

Input parameters:

- `answers` (object): Compliance flags; pass check_website's suggestedAnswers. Recognized keys: usesAnalytics, processesPayments, usesGenerativeAI, collectsEmails, sharesWithThirdParties, platformType.
- `appName` (string, required): Public / commercial name of the product.
- `contactEmail` (string): Contact email for privacy requests and data-subject rights.
- `entity` (string): Data controller / legal entity responsible for the app.
- `locales` (array): Document languages (max 3 for anonymous callers). Defaults to the languages suggested by the chosen markets.
- `markets` (array, required): Regions where the app has users; determines the legal frameworks covered.

### `check_ai_act` (~954 tokens)

Classify EU AI Act risk

Classify 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 parameters fall into three groups, all optional and defaulting to the safest 'not applicable' value: (1) transparency triggers — usesAI, interactsWithPeople, generatesContent, automatedDecisions; (2) the eight prohibited practices of art. 5 — socialScoring, realtimeBiometricPublic + realtimeBiometricLawEnforcement, emotionRecognitionWorkEducation, biometricCategorisationSensitive, untargetedFaceScraping, manipulativeOrExploitative, individualPredictivePolicing; (3) high-risk triggers — embeddedInRegulatedProduct, annexIII domains. Answer the boolean questions about what the system does; leave unknowns at their defaults, which never over-report risk. Read-only and instant.

Input parameters:

- `annexIII` (array): Annex III high-risk domains that apply. Only these exact values count; anything else is not Annex III and must be left out.
- `automatedDecisions` (boolean): Does it make automated decisions with legal or similarly significant effects on people (credit, hiring, admissions…)? Adds GDPR art. 22 duties; high risk only if an Annex III domain applies.
- `biometricCategorisationSensitive` (boolean): Does it use biometric data (face, voice, gait…) to infer sensitive attributes — race, political opinion, religion, trade-union membership, sexual orientation (art. 5.1.g)? Prohibited. Ordinary face-u…
- `embeddedInRegulatedProduct` (boolean): Is the AI a safety component embedded in an Annex I regulated product (toys, machinery, medical devices…)? High risk via art. 6.1, deadline Aug 2, 2028.
- `emotionRecognitionWorkEducation` (boolean): Does it infer emotions (frustration, attention, mood…) from employees at work or students in education, e.g. to flag disengaged staff or bored students (art. 5.1.f)? Prohibited. Emotion inference on…
- `generatesContent` (boolean): Does it generate text, images, audio or video shown to users? Triggers the art. 50 duty to label AI-generated content.
- `individualPredictivePolicing` (boolean): Predicting an individual's criminal risk based solely on profiling or personality traits (art. 5.1.d)? Prohibited.
- `interactsWithPeople` (boolean): Do people interact directly with the AI (chatbot, voice assistant…)? Triggers the art. 50 duty to disclose they are talking to an AI.
- `manipulativeOrExploitative` (boolean): Does it use subliminal techniques beyond a person's consciousness, or exploit a known vulnerability (age, disability, specific social or economic situation) to materially distort behavior and cause h…
- `realtimeBiometricLawEnforcement` (boolean): Only if realtimeBiometricPublic: is it used FOR LAW ENFORCEMENT purposes? That combination is prohibited under art. 5.1.h and already in force; any other use of public real-time biometric ID is high…
- `realtimeBiometricPublic` (boolean): Real-time remote biometric identification in publicly accessible spaces (e.g. live face recognition)? High risk (Annex III biometrics) — prohibited only when combined with realtimeBiometricLawEnforce…
- `socialScoring` (boolean): Does it score people's social behavior or traits causing detrimental treatment in unrelated contexts, or disproportionate to the behavior (art. 5.1.c)? Prohibited. A seller rating or fitness points a…
- `untargetedFaceScraping` (boolean): Does it untargetedly scrape facial images from the internet or CCTV footage to build or expand a face-recognition database (art. 5.1.e)? Prohibited. Matching a user's own consented selfie against the…
- `usesAI` (boolean): Does the product use AI at all (LLM calls, recommendations, computer vision…)? false ⇒ minimal risk, the AI Act does not apply.

### `get_install_snippet` (~158 tokens)

Get install snippet

Return what to install for a LexVibe app id. For web: the one-line <script> snippet (cookie banner with real script blocking + hosted policy links) to paste before </head>, plus a JSX variant for React/Next.js layouts. For iOS/Android: the hosted privacy-policy URL and the exact App Store Connect / Google Play Console fields to paste it into. No app id yet? Call claim_app to create one in the user's account.

Input parameters:

- `accent` (string): Optional brand color for the banner, as a hex value like #4f46e5.
- `appId` (string, required): LexVibe app id from the dashboard.
- `platform` (string): Target platform. Defaults to web.

### `claim_app` (~422 tokens)

Claim a real LexVibe app

Create 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 expires in 30 minutes. On confirmation LexVibe creates the app, scans the URL (if given), generates and hosts the legal documents. After the user confirms, call get_claim_status with the returned code to retrieve the real app id and install snippet. Provide at least `url` or `appName`.

Input parameters:

- `aiAct` (object): If you already ran check_ai_act for this product, pass the SAME answers object here. The EU AI Act classification is then saved against the app on confirmation and shown in the user's dashboard, inst…
- `answers` (object): Compliance flags you already know (pass check_website's suggestedAnswers): usesAnalytics, processesPayments, usesGenerativeAI, collectsEmails, sharesWithThirdParties, platformType, companyEntity, con…
- `appName` (string): App / business name (required if no url is provided).
- `markets` (array): Regions where the app has users; each market pack cites its own frameworks: eu → GDPR/ePrivacy, uk → UK GDPR/PECR, us → CCPA/CPRA, ca → PIPEDA, latam → LGPD…; 'global' is NOT a union of the others —…
- `platform` (string): Target platform when there is no url to infer it from.
- `url` (string): Public URL of the app: a website URL, or an App Store / Google Play listing URL for a mobile-only product. LexVibe scans whichever kind is provided on confirmation. If you don't have a listing URL ye…

### `get_claim_status` (~100 tokens)

Get claim status

Check 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 expires in 30 minutes). Once claimed it returns the REAL app id, the install snippet and the hosted privacy-policy URL: replace any placeholder (YOUR_APP_ID) snippet with the real one.

Input parameters:

- `code` (string, required): The claim code returned by claim_app.

### `lookup_framework` (~183 tokens)

Look up a privacy or AI framework

Look 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 articles, and a link to the OFFICIAL text (plus the supervisory authority). Use it to answer 'what does the TDPSA require?' or 'when does the EU AI Act apply?' with citations instead of guesses. Call list_frameworks first if you don't know the id. Read-only, instant, no signup.

Input parameters:

- `id` (string, required): Framework id, e.g. "gdpr", "eu-ai-act", "ccpa", "tdpsa", "lgpd", "pipl", "dpdp", "popia". Get the full list from list_frameworks.

### `list_frameworks` (~202 tokens)

List the frameworks LexVibe tracks

List every privacy and AI framework LexVibe generates documents against — 60 laws across 60+ jurisdictions, including GDPR, ePrivacy, the EU AI Act, UK GDPR and PECR, Swiss nFADP, CCPA/CPRA and 18 US state privacy laws modelled individually, PIPEDA and Quebec Law 25, LGPD and other LatAm regimes, APPI, PIPA, PDPA, Australia's Privacy Act, India's DPDP, China's PIPL, Saudi and UAE PDPL, POPIA and more. Each entry carries its id, jurisdiction, effective date and official-text URL. Optionally filter by market pack or by jurisdiction. Read-only, instant.

Input parameters:

- `jurisdiction` (string): Optional jurisdiction id to filter by, e.g. "us-tx", "br", "eu".
- `market` (string): Optional market pack to filter by (eu, uk, us, latam, apac…).

### `applicable_frameworks` (~128 tokens)

Which laws apply to my markets

Given 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 what generate_policies uses internally, so the answer matches the documents LexVibe would actually produce. Use it to answer 'I sell to the EU and Texas — what do I need?'. Read-only, instant.

Input parameters:

- `markets` (array, required): Markets the product serves, e.g. ["eu", "us"].

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/marcosnovo-lexvibe/api-mcp#diagnostics

## Score history

- 2026-08-03: 73
- 2026-08-02: 73
- 2026-08-01: 72
- 2026-07-31: 69
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://golexvibe.com/api/mcp
- Repository: https://github.com/marcosnovo/lexvibe-mcp
- Website: https://golexvibe.com/
- Changelog RSS feed: https://verifymcp.io/servers/marcosnovo-lexvibe/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/marcosnovo-lexvibe/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/marcosnovo-lexvibe/api-mcp