mcp-registry/io.github.vdineshk/ai-compliance-monitor · v1.0.0
As of 2026-10-21 05:32 UTC, the Vdineshk Ai Compliance Monitor MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Regulatory intelligence for AI agents across jurisdictions
Claude Code
claude mcp add --transport http vdineshk-ai-compliance-monitor-mcp-serve https://ai-compliance-monitor.sgdata.workers.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"vdineshk-ai-compliance-monitor-mcp-serve": {
"type": "http",
"url": "https://ai-compliance-monitor.sgdata.workers.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.vdineshk%2Fai-compliance-monitor/fixes
{
"name": "check_deadline",
"description": "Returns upcoming and recent compliance deadlines with enforcement dates, penalty information, and related obligations. Use this to understand time-sensitive compliance requirements.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"months_ahead": {
"type": "number",
"description": "Number of months ahead to look for upcoming deadlines. Default: 12"
},
"include_passed": {
"type": "boolean",
"description": "Whether to include deadlines that have already passed. Default: false"
},
"jurisdiction_code": {
"type": "string",
"description": "Optional jurisdiction code to filter by. Examples: EU, SG, US-CO"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_obligations",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"use_case"
],
"properties": {
"use_case": {
"type": "string",
"description": "The AI agent use case to check. Examples: hiring_screening, credit_scoring, customer_service, content_moderation, medical_triage, autonomous_coding, financial_trading"
},
"jurisdiction_code": {
"type": "string",
"description": "Optional jurisdiction code to filter by. Examples: EU, SG, US-CO. Omit to get all jurisdictions."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "compare_jurisdictions",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"category"
],
"properties": {
"category": {
"type": "string",
"description": "The obligation category to compare. Options: transparency, record_keeping, human_oversight, risk_assessment, incident_reporting, data_governance, monitoring, audit"
},
"jurisdictions": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional list of jurisdiction codes to compare. Default: all available. Examples: [\"EU\", \"SG\", \"US-CO\"]"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.vdineshk/ai-compliance-monitor"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.vdineshk/ai-compliance-monitor"}) over MCP.
compare_jurisdictions ~212 tokenscheck_obligations ~206 tokensget_regulation_articles ~192 tokenscheck_deadline ~179 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.vdineshk%2Fai-compliance-monitor?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.vdineshk%2Fai-compliance-monitor?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.vdineshk%2Fai-compliance-monitor.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.vdineshk%2Fai-compliance-monitor.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.vdineshk%2Fai-compliance-monitor?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9dbd529416c71978…, first seen 2026-10-17, included at leaf 931 of 37,390. Version history · verify what your client received.
Compare: most reliable data servers · most reliable knowledge servers · most reliable retrieval servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 05:32 UTC, the Vdineshk Ai Compliance Monitor MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Vdineshk Ai Compliance Monitor MCP server advertises 4 tools, including check_deadline, check_obligations, compare_jurisdictions, get_regulation_articles.
Point your MCP client at this streamable-http endpoint: https://ai-compliance-monitor.sgdata.workers.dev/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.