# io.github.vdineshk/ai-compliance-monitor (remote · ai-compliance-monitor.sgdata.workers.dev)

Regulatory intelligence for AI agents across jurisdictions

- Trust score: 59/100 (low)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `ai-compliance-monitor.sgdata.workers.dev`: 59/100 (this document), [markdown](https://verifymcp.io/servers/vdineshk-ai-compliance-monitor/ai-compliance-monitor.md), [page](https://verifymcp.io/servers/vdineshk-ai-compliance-monitor/ai-compliance-monitor)

## Channel facts

- Endpoint: `https://ai-compliance-monitor.sgdata.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 465 tokens (~116/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

```bash
openclaw mcp add vdineshk-ai-compliance-monitor --url https://ai-compliance-monitor.sgdata.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vdineshk-ai-compliance-monitor:
    url: "https://ai-compliance-monitor.sgdata.workers.dev/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 57, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 59, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (4)

### `check_obligations` (~128 tokens)

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.

Input parameters:

- `jurisdiction_code` (string): Optional jurisdiction code to filter by. Examples: EU, SG, US-CO. Omit to get all jurisdictions.
- `use_case` (string, required): The AI agent use case to check. Examples: hiring_screening, credit_scoring, customer_service, content_moderation, medical_triage, autonomous_coding, financial_trading

### `get_regulation_articles` (~111 tokens)

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.

Input parameters:

- `category` (string): Optional filter by obligation category. Options: transparency, record_keeping, human_oversight, risk_assessment, incident_reporting, data_governance, monitoring, audit
- `regulation_id` (string, required): The regulation identifier. Options: eu-ai-act, sg-imda-agentic, co-ai-act

### `check_deadline` (~103 tokens)

Returns upcoming and recent compliance deadlines with enforcement dates, penalty information, and related obligations. Use this to understand time-sensitive compliance requirements.

Input parameters:

- `include_passed` (boolean): Whether to include deadlines that have already passed. Default: false
- `jurisdiction_code` (string): Optional jurisdiction code to filter by. Examples: EU, SG, US-CO
- `months_ahead` (number): Number of months ahead to look for upcoming deadlines. Default: 12

### `compare_jurisdictions` (~123 tokens)

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.

Input parameters:

- `category` (string, required): The obligation category to compare. Options: transparency, record_keeping, human_oversight, risk_assessment, incident_reporting, data_governance, monitoring, audit
- `jurisdictions` (array): Optional list of jurisdiction codes to compare. Default: all available. Examples: ["EU", "SG", "US-CO"]

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vdineshk-ai-compliance-monitor/ai-compliance-monitor#diagnostics

## Score history

- 2026-08-03: 59
- 2026-08-02: 58
- 2026-08-01: 58
- 2026-07-31: 57
- 2026-07-30: 59
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://ai-compliance-monitor.sgdata.workers.dev/mcp
- Repository: https://github.com/vdineshk/ai-compliance-monitor
- Changelog RSS feed: https://verifymcp.io/servers/vdineshk-ai-compliance-monitor/ai-compliance-monitor/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/vdineshk-ai-compliance-monitor/ai-compliance-monitor/changelog.json
- HTML version of this page: https://verifymcp.io/servers/vdineshk-ai-compliance-monitor/ai-compliance-monitor