Agent Module

Created By
Agent Module3 months ago
Agent-native knowledge infrastructure for EU AI Act compliance. 21 validated ethics modules — deterministic logic gates, specific statutory citations, structured for autonomous agent retrieval. Free trial available via the get_trial_key tool (no key required to start). Covers Art. 5 prohibited practices, Art. 9 risk management, Art. 27 FRIA, Art. 43 conformity assessment, Art. 72 post-market monitoring, GPAI obligations (Art. 53/55), and more. Built for the August 2026 EU AI Act enforcement deadline.
Overview

Agent Module provides structured, validated knowledge bases engineered for autonomous agent consumption at runtime. Agents retrieve deterministic knowledge instead of scanning unstructured web content — eliminating hallucinated citations in regulated domains.

Current vertical: EU AI Act Ethics — 21 modules

Coverage includes:

Art. 5 — Prohibited AI practices (€35M penalty tier)

Art. 9 — Risk management systems

Art. 27 — Fundamental Rights Impact Assessment (FRIA)

Art. 43 — Conformity assessment

Art. 72 — Post-market monitoring

Art. 53/55 — GPAI model obligations Getting started — no key required:

Call get_trial_key to receive a 24-hour trial key with 500 calls. All 21 modules accessible immediately.

Authentication: X-AM-Key header

August 2, 2026 — EU AI Act high-risk AI obligations become enforceable. Built for that deadline.

Pricing: Free trial → $19/mo Inaugural cohort (grandfathered for life).

Server Config

{
  "mcpServers": {
    "agent-module": {
      "url": "https://api.agent-module.dev/mcp",
      "transport": "http",
      "headers": {
        "X-AM-Key": "<YOUR_AM_KEY>"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
Agent Module
Star
-
Language
-
License
-
Category
Homepage

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago