mcp server
ai-compliance-monitor
Regulatory intelligence for AI agents across jurisdictions
Description as published by the maintainer. Source
- version 1.0.0
- slowing
slowing — Registry entry last updated 2026-04-10.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_deadline(months_ahead, include_passed, jurisdiction_code)- Returns upcoming and recent compliance deadlines with enforcement dates, penalty information, and related obligations. Use this to understand time-sensitive compliance requirements.
check_obligations(use_case, jurisdiction_code)- 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. Required: use_case.
compare_jurisdictions(category, 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. Required: category.
get_regulation_articles(category, regulation_id)- 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. Required: regulation_id.
Last successful function declaration observed on . Source: https://ai-compliance-monitor.sgdata.workers.dev/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://ai-compliance-monitor.sgdata.workers.dev/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-04-10 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-04-10 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | ai-compliance-monitor.sgdata.workers.dev | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | ai-compliance-monitor.sgdata.workers.dev |
Where to get it
Also from vdineshk
-
io.github.vdineshk/dominion-observatory
Runtime behavioral trust scoring for MCP servers. Check reliability before calling unknown tools.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json