io.github.vdineshk/ai-compliance-monitor

MCPcommunitylive
v1.0.0io.github.vdineshkUnknownUpdated 5mo agoGitHub

Regulatory intelligence for AI agents across jurisdictions

Structured regulatory intelligence for AI agents operating across jurisdictions. The first MCP server purpose-built for AI agent compliance. Check obligations, deadlines, and cross-jurisdiction requirements for the EU AI Act, Singapore IMDA Agentic AI Framework, and Colorado AI Act. AI agents operating across borders face a fragmented regulatory landscape. The EU AI Act requires automatic logging…

Endpoint healthlive
checked 6 days ago · 220ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.vdineshk
LicenseUnknown
Version1.0.0
Sourcemcp-registry
GitHubvdineshk/ai-compliance-monitor
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface4 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

check_obligationsNo description published

This tool published no description. Forge does not invent one.

get_regulation_articlesNo description published

This tool published no description. Forge does not invent one.

check_deadlineNo description published

This tool published no description. Forge does not invent one.

compare_jurisdictionsNo description published

This tool published no description. Forge does not invent one.

0 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Structured regulatory intelligence for AI agents operating across jurisdictions. The first MCP server purpose-built for AI agent compliance. Check obligations, deadlines, and cross-jurisdiction requirements for the EU AI Act, Singapore IMDA Agentic AI Framework, and Colorado AI Act. AI agents operating across borders face a fragmented regulatory landscape. The EU AI Act requires automatic logging (Article 12). Singapore's IMDA framework mandates escalation protocols. Colorado demands impact…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

4 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.