get_regulationsLABSCO 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_regulationsfilters by jurisdiction, category — privacy, safety, transparency, governance — status, or free textcompliance_calendarreturns upcoming deadlines with priority levels, looking 365 days ahead by defaultregulation_summarygives one regulation's requirements and timeline by id, such aseu-ai-act,ccpaornist-ai-frameworkrisk_assessmentscores a use case — healthcare diagnosis, hiring screening, content moderation and others — across several jurisdictions, with a free-text option for cases outside the templatespolicy_updatestracks recent regulatory movement, filtered by jurisdiction, regulation, impact level or how far back to lookjurisdiction_compareputs 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
USE CASES
Checking what is due next
Pull upcoming deadlines by jurisdiction with priority levels rather than trawling regulator sites.
Sizing the risk of a new AI feature
Assess the use case across the markets you ship into and read the differences.
Getting the shape of one regulation
Ask for the summary by id and read the requirements and timeline in one place.
Catching up on what changed
Filter recent policy movement by impact level over the last month.
6 tools
Listed in project docs. Your client may show a different list.
compliance_calendarregulation_summaryrisk_assessmentpolicy_updatesjurisdiction_compareBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
npx -y @leviai/compliance-mcpMCP Clients
Claude Desktop
{
"mcpServers": {
"compliance-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_COMPLIANCE_MCP>/build/index.js"
]
}
}
}