Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "ai-compliance-monitor": {
      "type": "http",
      "url": "https://ai-compliance-monitor.sgdata.workers.dev/mcp"
    }
  }
}

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

[mcp_servers.ai-compliance-monitor]
url = "https://ai-compliance-monitor.sgdata.workers.dev/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-compliance-monitor": {
      "type": "remote",
      "url": "https://ai-compliance-monitor.sgdata.workers.dev/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "ai-compliance-monitor": {
      "type": "http",
      "url": "https://ai-compliance-monitor.sgdata.workers.dev/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=ai-compliance-monitor&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYWktY29tcGxpYW5jZS1tb25pdG9yLnNnZGF0YS53b3JrZXJzLmRldi9tY3AifQ%3D%3D"
}

{
  "servers": {
    "ai-compliance-monitor": {
      "type": "http",
      "url": "https://ai-compliance-monitor.sgdata.workers.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "ai-compliance-monitor": {
      "httpUrl": "https://ai-compliance-monitor.sgdata.workers.dev/mcp"
    }
  }
}

extensions:
  "ai-compliance-monitor":
    enabled: true
    name: "ai-compliance-monitor"
    type: streamable_http
    uri: "https://ai-compliance-monitor.sgdata.workers.dev/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2024-11-05; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene71 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: compare_jurisdictions (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_obligations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_regulation_articles (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
pass
tools.token_costabout 670 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

4 tools, about 670 tokens to load them all · tool set cadc8c249a90 · checked 2026-10-19 12:00 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 83 / 100

provenance80

liveness99

freshness45

hygiene100

+repository +namespace-matches-repo +reachable +uptime-97% -stale-192d

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://ai-compliance-monitor.sgdata.workers.dev/mcp` streamable-http	none	yes	97%	140 ms	2024-11-05	2026-10-19

Tools (4)

`check_deadline`	Returns upcoming and recent compliance deadlines with enforcement dates, penalty information, and related obligations. Use this to understand time-sensitive compliance requirements.
`check_obligations`	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.
`compare_jurisdictions`	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_articles`	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.

Schemas: list_tools.

Similar MCP servers

More from io.github.vdineshk

Official server.json

{
  "name": "io.github.vdineshk/ai-compliance-monitor",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json",
  "remotes": [
    {
      "url": "https://ai-compliance-monitor.sgdata.workers.dev/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "repository": {
    "url": "https://github.com/vdineshk/ai-compliance-monitor",
    "source": "github"
  },
  "description": "Regulatory intelligence for AI agents across jurisdictions"
}