Skip to content

io.github.vdineshk/ai-compliance-monitor

by vdineshk · remote · no sign-in to list tools · v1.0.0 · published by GitHub user vdineshk

Regulatory intelligence for AI agents across jurisdictions

Changes · 1
CompareRegistry entry

4 tools: 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http ai-compliance-monitor https://ai-compliance-monitor.sgdata.workers.dev/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 1Claude Code: ask
  • check_obligationsGiven an AI agent use case and optional jurisdiction, returns all applicable regulatory obligations with evidence requirements, enforcement dates, and penalty information.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Given an AI agent use case and optional jurisdiction, returns all applicable regulatory obligations with evidence requirements, enforcement dates, and penalty information. Use this to understand what compliance requirements apply to a specific type of AI agent.
Only reads 3Claude Code: allow
  • check_deadlineReturns upcoming and recent compliance deadlines with enforcement dates, penalty information, and related obligations.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Returns upcoming and recent compliance deadlines with enforcement dates, penalty information, and related obligations. Use this to understand time-sensitive compliance requirements.
  • compare_jurisdictionsSide-by-side comparison of regulatory obligations across jurisdictions for a given compliance category.No findings

    Why it is in this group

    • The name "compare_jurisdictions" says "compare": a word for reading.
    Description, as the server wrote it
    Side-by-side comparison of regulatory obligations across jurisdictions for a given compliance category. Shows equivalent, overlapping, stricter, and weaker mappings between regulations. Use this to understand how requirements differ across borders.
  • get_regulation_articlesReturns structured, machine-readable regulation details including specific articles, obligation classifications, risk levels, and evidence requirements.No findings

    Why it is in this group

    • The name "get_regulation_articles" says "get": a word for reading.
    Description, as the server wrote it
    Returns structured, machine-readable regulation details including specific articles, obligation classifications, risk levels, and evidence requirements. Use this to understand the detailed requirements of a specific regulation.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ai-compliance-monitor https://ai-compliance-monitor.sgdata.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ai-compliance-monitor__get_regulation_articles",
      "mcp__ai-compliance-monitor__check_deadline",
      "mcp__ai-compliance-monitor__compare_jurisdictions"
    ],
    "ask": [
      "mcp__ai-compliance-monitor__check_obligations"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as ai-compliance-monitor. Review it before you use it.