sovereign-ai-act-mcp

MCPcommunitylive
v1.4.0Dominion Intelligence ABMITUpdated 5d agonpmGitHub

MCP server exposing Leo — the deterministic EU AI Act classifier (Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744) — as tools for AI agents. Every answer cites the law verbatim.

Endpoint healthlive
checked 4 days ago · 131ms
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, 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 →
67Downloads/wk
5d agoLast update
Package
AuthorDominion Intelligence AB
LicenseMIT
Version1.4.0
Sourcenpm+mcp-registry
npmsovereign-ai-act-mcp
GitHubsaidbazyar/sovereign-ai-act-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface4 tools · none privileged
Security scan✓ Cleanv1.4.0 · todayHow well does this scan work?
EvalsNone
IndexedSep 24, 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 packagev1.4.0 · 9h 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.

classify_ai_systemClassify an AI system under the EU AI Act (Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744). Give a plain-language description of

Classify an AI system under the EU AI Act (Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744). Give a plain-language description of

No input schema was published for this tool.

lookup_articleReturn the verbatim text of one specific EU AI Act Article (1–113), exactly as published in the Official

Return the verbatim text of one specific EU AI Act Article (1–113), exactly as published in the Official

No input schema was published for this tool.

search_eu_ai_actFull-text keyword search across the entire EU AI Act corpus — all Articles (1–113), Recitals (1–180) and

Full-text keyword search across the entire EU AI Act corpus — all Articles (1–113), Recitals (1–180) and

No input schema was published for this tool.

get_compliance_deadlinesReturn the canonical EU AI Act application timeline (the staggered dates each obligation starts to apply,

Return the canonical EU AI Act application timeline (the staggered dates each obligation starts to apply,

No input schema was published for this tool.

4 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

MCP server exposing Leo — the deterministic EU AI Act classifier (Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744) — as tools for AI agents. Every answer cites the law verbatim.

Keywords
mcpmodel-context-protocoleu-ai-actai-actcomplianceregulationeuropegdprclaudellm
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.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-28 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.