Skip to main content
Glama
Sign In
@lexvibe/mcp

@lexvibe/mcp

by marcosnovo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @lexvibe/mcp

Related Servers

  • PrivacyPage MCP Server

    rushi053
    A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to generate privacy policies, terms of service, EULAs, cookie policies, and disclaimers directly within the development workflow, with free previews and optional full-document unlocking via a one-time license key.
    6
    52 npm
    MIT

  • LegalForge MCP Server

    automatikstudio
    F
    license
    B
    quality
    Not graded
    maintenance
    Enables the generation of professional, jurisdiction-specific legal documents like privacy policies, terms of service, and cookie policies. It allows users to produce structured HTML legal content by providing specific parties, terms, and service configurations to an AI-driven tool.
    1
    -

  • ApproveKit

    yateshaw
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables coding agents to build an inventory of what an app collects from its repo and run a free audit against the rules Apple, Google Play and Google OAuth reviewers apply. Also generates and hosts the required submission documents (privacy policy, account deletion page, reviewer notes, scope justifications) for a one-time fee once the user approves a checkout.
    MIT
Deploy Server
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

A4.6/5.0

Scored across 10 tools

Disambiguation4/5

Most tools target clearly distinct actions (scan_project, check_website, generate_policies, install_snippet, verify_snippet, check_ai_act). The potential overlaps — check_compliance vs make_compliant vs scan_project vs check_website — are explicitly differentiated in the descriptions (read-only vs write, local source vs deployed URL), so an agent can tell them apart, though the cluster of 'check*' tools requires careful reading.

Naming Consistency5/5

All ten tools follow a consistent snake_case verb_noun pattern (claim_app, check_compliance, generate_policies, install_snippet, verify_snippet, scan_project). The convention is uniform throughout with no mixed casing or stylistic drift.

Tool Count5/5

Ten tools is well-scoped for a legal-compliance server spanning scan, generate, install, verify, and app-claim workflows. Each tool earns its place with no redundant or filler entries.

Completeness4/5

The surface covers a full lifecycle: scan_project → generate_policies → install_snippet → verify_snippet, plus claim_app/get_claim_status, check_website, check_ai_act, and the one-shot make_compliant. Minor gaps exist (no snippet removal, no update/delete of previously generated documents), but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues

Resources