Lextiva Compliance MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_regulationsA | Returns the list of all privacy and AI regulations covered, with short_name, full name, jurisdiction, effective_date, and official_url for each. Currently 29 regulations across EU, UK, US (federal + 10 states), and Canada. Use this first when the user asks about coverage or when you need to look up a regulation ID for follow-up calls. |
| get_regulationA | Returns the full record for a single regulation including key_articles, scope, applicable_to, data_subject_rights granted, supervisory authority, and primary-source URL. Pass the short id like 'gdpr', 'ccpa_cpra', 'eu_ai_act', 'vcdpa'. |
| list_jurisdictionsA | Returns the list of all jurisdictions tracked: countries, supranational unions, and US states. Currently 24 jurisdictions. Each carries ISO code, type (country/us_state/supranational), and the regulation IDs that apply there. |
| get_jurisdictionA | Returns the full record for a single jurisdiction including the list of regulations that apply there and population context. Pass ids like 'eu', 'uk', 'us', 'us_ca', 'us_va', 'ca'. |
| list_document_typesA | Returns the list of the 7 compliance documents tracked: privacy_policy, terms_of_service, cookie_policy, gdpr_notice, ccpa_notice, ai_use_policy, dpa. Each carries audience, mandatory_under (which regulations require it), and typical_sections. |
| get_document_typeA | Returns the full record for a single document type — typical sections, audience, and which regulations mandate it. Pass ids like 'privacy_policy', 'dpa', 'ai_use_policy'. |
| list_data_subject_rightsA | Returns the list of the 8 canonical data-subject rights and the regulations that grant each: access, rectification, erasure, portability, restriction, objection, opt_out_sale_or_sharing, automated_decision_making. |
| get_data_subject_rightA | Returns the full record for a single data subject right. Pass ids like 'erasure', 'portability', 'opt_out_sale_or_sharing'. |
| documents_for_regulationA | Given a regulation id, returns every document type that regulation requires (or optionally permits), with the required clauses for each. Use this when a user asks 'what documents do I need for X?'. |
| regulations_for_documentA | Given a document type id, returns every regulation that mandates or permits that document, with required clauses for each. Use this when a user asks 'which laws require a Privacy Policy / DPA / Cookie Policy?'. |
| compliance_checklistA | Returns the specific required-clauses checklist for a (regulation, document_type) pair, plus primary-source URLs and contextual notes. Most useful tool for 'what do I need in my Privacy Policy under GDPR?' style queries. |
| applicable_regulationsB | Given a jurisdiction id, returns every regulation that applies there, plus the required and optional documents for each. Use this when a user asks 'I serve customers in California — what privacy laws apply?'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| regulations | |
| jurisdictions | |
| document_types | |
| data_subject_rights | |
| matrix |
TDQS
Scored across 12 tools
Each tool targets a distinct aspect of compliance reference: listing and fetching jurisdictions, regulations, document types, data subject rights, and cross-referencing them. Descriptions clearly differentiate overlapping functionalities like applicable_regulations vs. documents_for_regulation.
Tool names follow a consistent pattern: 'get_' for single records, 'list_' for collections, and descriptive noun phrases for cross-reference tools. Minor deviation with 'applicable_regulations' and 'compliance_checklist' not following the verb prefix, but still readable.
12 tools cover the domain comprehensively without being excessive. Each tool serves a clear purpose, and the count is appropriate for a compliance reference server.
The tool surface provides full coverage for a read-only compliance reference: discovering regulations by jurisdiction, obtaining checklists, listing required documents, and retrieving details. No obvious gaps for the stated purpose.