EU AI Act compliance for AI agents, grounded in Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744 (Digital Omnibus, in force 27 July 2026). Operative law is the default in every answer; pending changes are opt-in and labelled by source status. Ten deterministic tools, no LLM in the loop, so the same input always returns the same output. euaiact_assess_system takes one normalized system profile and returns separate legal-classification, impact and implementation-readiness blocks with field-level provenance. euaiact_classify_system returns a risk tier (prohibited, high-risk, limited, minimal) from free text or structured signals, naming both the signals it matched and the ones it still needs. The rest cover Annex III and Annex IV, provider and deployer obligations, the Art. 6(3) exception including the profiling carve-out, GPAI systemic risk at the Art. 51 threshold of 10^25 FLOPs, penalties, deadlines, and article lookup with stable EUR-Lex citations. Five resources and
EU AI Act Compliance is a remote MCP server published at mcp.lexbeam.com. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 410 ms, placing it among the faster endpoints. It offers a narrow, focused set of 10 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
euaiact_classify_system — Truncated description cuts off critical output details.euaiact_check_deadlines — Incomplete explanation of 'include_pending_omnibus' parameter.euaiact_get_article — Unclear handling of unsupported article requests.Risk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/lexbeam-software-eu-ai-act)<a href="https://mcpmetrics.io/servers/lexbeam-software-eu-ai-act"><img src="https://mcpmetrics.io/badge/lexbeam-software/eu-ai-act/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 13:13:33 | Legacy | 400 | 447 | 200 | 444 | 2025-11-25 |
| 2026-09-11 11:20:19 | Legacy | 400 | 458 | 200 | 459 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 402 | 200 | 403 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 400 | 375 | 200 | 377 | 2025-11-25 |
| 2026-09-11 05:44:28 | Legacy | 400 | 410 | 200 | 397 | 2025-11-25 |
| 2026-09-11 03:50:39 | Legacy | 400 | 422 | 200 | 429 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 326 | 401 | 339 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.