Labsco
MCP SERVER

Compliance MCP

by leviai-ai

Look up AI regulations, deadlines and risk profiles across six jurisdictions — from a local dataset, no API calls.

Regulatory Compliance & AI Governance
Summary
Local data means fast and offline — and only as current as the last commit.

Shipping the regulations as JSON removes an API dependency and a key, which is a real convenience, but it also means the deadlines you get are the ones someone wrote down rather than a live feed. That is a reasonable trade for orientation work — comparing how two jurisdictions treat a use case, or seeing what is due next — and the wrong basis for a filing decision. Check the repository's recency before leaning on a date.

What it is

A server carrying a curated dataset of AI regulations and their compliance timelines, covering the EU, US, UK, Canada, China and Singapore. Everything ships as local JSON files, so there is no external API and no key: the tools query bundled data on regulations, deadlines, risk templates and recent policy movement.

What you get
  • `get_regulations` filters by jurisdiction, category — privacy, safety, transparency, governance — status, or free text
  • `compliance_calendar` returns upcoming deadlines with priority levels, looking 365 days ahead by default
  • `regulation_summary` gives one regulation's requirements and timeline by id, such as `eu-ai-act`, `ccpa` or `nist-ai-framework`
  • `risk_assessment` scores a use case — healthcare diagnosis, hiring screening, content moderation and others — across several jurisdictions, with a free-text option for cases outside the templates
  • `policy_updates` tracks recent regulatory movement, filtered by jurisdiction, regulation, impact level or how far back to look
  • `jurisdiction_compare` puts several jurisdictions side by side, optionally focused on privacy, safety, transparency, penalties or timelines
  • Regulations covered include the EU AI Act, CCPA/CPRA, the NIST AI Framework, the UK draft legislation, Canada's AIDA and China's algorithm provisions
Requirements

Nothing external — no account, no key, no network calls at query time. Clone, `npm install`, `npm run build`, then point your client at `node` with `build/index.js`. Package `@leviai/compliance-mcp`, version 1.0.1. Because the dataset is bundled and curated by hand, its currency is whatever the repository was last updated to; treat it as reference material rather than legal advice.

Setup effort

One command — npx -y @leviai/compliance-mcp