dev.agent-module/mcp

MCPcommunitylive
v0.9.9dev.agent-moduleUnknownUpdated 6mo agoGitHub

Deterministic compliance and vertical knowledge bases for autonomous agents. Free 24hr trial.

EU AI Act compliance logic for autonomous agents — retrievable during runtime. If you're building with AI, you need to know the EU AI Act. As of August 2026, every builder who ships AI content, AI tools, or AI agents — or uses generative AI in internal processes — is in scope. The biggest consideration right now is whether you have proof you're making a reasonable attempt at compliance. Agent…

Endpoint healthlive
checked 10 days ago · 132ms
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 →
2GitHub stars
6mo agoLast update
Package
Authordev.agent-module
LicenseUnknown
Version0.9.9
Sourcemcp-registry
GitHubAgentModule/mcp
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 surface—
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

No tool declarations found in the source3mo ago

Forge read 1 source file from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

EU AI Act compliance logic for autonomous agents — retrievable during runtime. If you're building with AI, you need to know the EU AI Act. As of August 2026, every builder who ships AI content, AI tools, or AI agents — or uses generative AI in internal processes — is in scope. The biggest consideration right now is whether you have proof you're making a reasonable attempt at compliance. Agent Module is a live, structured compliance resource. With it, your agents can: Retrieve applicable ethics…

Keywords
mcp
Alternatives
Comparing tool surfaces…

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.