io.github.vdineshk/ai-compliance-monitor
REMOTE · AI-COMPLIANCE-MONITOR.SGDATA.WORKERS.DEV
Regulatory intelligence for AI agents across jurisdictions
Available components
Last scanned (16 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 465 tokens (~116/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://ai-compliance-monitor.sgdata.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sgdata.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6565455d59659af7096782912eec6256cc5 |
| SANs: *.sgdata.workers.dev, sgdata.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ai-compliance-monitor.sgdata.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai-compliance-monitor.sgdata.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://ai-compliance-monitor.sgdata.workers.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_deadline ~103
Returns upcoming and recent compliance deadlines with enforcement dates, penalty information, and related obligations. Use this to understand time-sensitive compliance requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
check_obligations ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction_code | string | – | Optional jurisdiction code to filter by. Examples: EU, SG, US-CO. Omit to get all jurisdictions. |
| use_case | string | yes | The AI agent use case to check. Examples: hiring_screening, credit_scoring, customer_service, content_moderation, medical_triage, autonomous_coding, financial_trading |
No output schema declared.
No examples provided.
compare_jurisdictions ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | 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"] |
No output schema declared.
No examples provided.
get_regulation_articles ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional filter by obligation category. Options: transparency, record_keeping, human_oversight, risk_assessment, incident_reporting, data_governance, monitoring, audit |
| regulation_id | string | yes | The regulation identifier. Options: eu-ai-act, sg-imda-agentic, co-ai-act |
No output schema declared.
No examples provided.
How do I install the io.github.vdineshk/ai-compliance-monitor MCP server?
io.github.vdineshk/ai-compliance-monitor is a hosted endpoint at https://ai-compliance-monitor.sgdata.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ai-compliance-monitor.sgdata.workers.dev
claude mcp add --transport http vdineshk-ai-compliance-monitor 'https://ai-compliance-monitor.sgdata.workers.dev/mcp'
What is the io.github.vdineshk/ai-compliance-monitor MCP server?
io.github.vdineshk/ai-compliance-monitor is an MCP server listed in the public MCP registry as io.github.vdineshk/ai-compliance-monitor. Regulatory intelligence for AI agents across jurisdictions. This page covers its hosted endpoint (https://ai-compliance-monitor.sgdata.workers.dev/mcp).
Is the io.github.vdineshk/ai-compliance-monitor MCP server safe to use?
io.github.vdineshk/ai-compliance-monitor scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.vdineshk/ai-compliance-monitor MCP server expose?
io.github.vdineshk/ai-compliance-monitor exposes 4 tools: check_obligations, get_regulation_articles, check_deadline, compare_jurisdictions. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.
Does the io.github.vdineshk/ai-compliance-monitor MCP server require authentication?
No. We connected to io.github.vdineshk/ai-compliance-monitor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.vdineshk/ai-compliance-monitor MCP server still maintained?
io.github.vdineshk/ai-compliance-monitor is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.vdineshk/ai-compliance-monitor MCP server?
VerifyMCP ran 12 checks on io.github.vdineshk/ai-compliance-monitor, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.vdineshk/ai-compliance-monitor: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.