Remote MCP · Endpoint

EU AI Act Explorer MCP server

No. EU AI Act Explorer answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://mcp.euaiactlaw.com/mcp

The last check completed an MCP handshake.

Registry name
com.euaiactlaw/eu-ai-act-explorer
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
46 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only EU AI Act (Reg. 2024/1689 as amended) answers, citing official sources
Listing
From the official MCP registry (active).
Recent checks of EU AI Act Explorer
CheckedResultHandshake
39 minutes agoHandshake completed46 ms
3 days agoHandshake completed803 ms
13 days agoHandshake completed107 ms
13 days agoHandshake completed116 ms
15 days agoHandshake completed84 ms
16 days agoHandshake completed92 ms
17 days agoHandshake completed88 ms
18 days agoHandshake completed59 ms
18 days agoHandshake completed60 ms
20 days agoHandshake completed104 ms
22 days agoHandshake completed63 ms
25 days agoHandshake completed99 ms
27 days agoHandshake completed57 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with EU AI Act Explorer and makes no claim about it beyond what these checks measured.