EU AI Act Compliance
https://server.smithery.ai/lexbeam-software/eu-ai-act/mcpEU 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 four prompts included. Sparse input fails closed: the server answers "undetermined" and names the decisive missing facts instead of guessing a classification. No API key, no telemetry, two runtime dependencies; installed locally it makes no network calls. MIT licensed. A first-pass technical output, not legal advice and not certification. By Lexbeam Software.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (4268 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 13.06/15 | 27/31 probes succeeded over 30 days (87%). |
| Tool declaration | 10/10 | Lists 10 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 75% of peers
- This listing 84 · peer median 81
- Latency
- Faster than 16% of peers
- This listing 720 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/lexbeam-software/eu-ai-act/mcp
curl -X POST https://server.smithery.ai/lexbeam-software/eu-ai-act/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'