Connect AI Act Radar and your agent gets 4 tools, among them get_obligation_for_role, lookup_article, query_ai_act_updates. It answers at https://mcp.aiactradar.com/mcp/v1 over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
EU AI Act obligations and updates from ten official sources, incl. the national layer.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_obligation_for_role | Look up the AI Act obligations for a specific role and AI-system risk category. Returns the relevant articles, recent guidance updates, and applicable templates. This is informational, not legal advice. Inputs: role, risk_category |
lookup_article | Look up a specific AI Act article (e.g. "Art. 53(1)(d)" or "Annex III") and return all related events from our pipeline plus the official EUR-Lex URL. Inputs: article |
query_ai_act_updates | Query EU AI Act regulatory updates from primary sources. Returns structured events with titles, summaries, severity, topics and source URLs. Optionally filter by date range, source, topics, or severity. Use this when you need recent or hist Inputs: since, until, source_id, topics, severity_min, limit |
summarize_changes_since | Generate a structured digest of all AI Act regulatory changes since a given date, grouped by topic and severity. Useful for weekly compliance reviews or audit prep. Returns Markdown. Inputs: since, topics, language |
Every block below points at https://mcp.aiactradar.com/mcp/v1. Pick your client and copy.
claude mcp add --transport http ai-act-radar https://mcp.aiactradar.com/mcp/v1
{
"mcpServers": {
"ai-act-radar": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.aiactradar.com/mcp/v1"]
}
}
}{
"mcpServers": {
"ai-act-radar": {
"url": "https://mcp.aiactradar.com/mcp/v1"
}
}
}{
"servers": {
"ai-act-radar": {
"type": "http",
"url": "https://mcp.aiactradar.com/mcp/v1"
}
}
}{
"context_servers": {
"ai-act-radar": {
"url": "https://mcp.aiactradar.com/mcp/v1"
}
}
}{
"mcpServers": {
"ai-act-radar": {
"serverUrl": "https://mcp.aiactradar.com/mcp/v1"
}
}
}{
"mcpServers": {
"ai-act-radar": {
"url": "https://mcp.aiactradar.com/mcp/v1"
}
}
}name: AI Act Radar
version: 0.0.1
schema: v1
mcpServers:
- name: AI Act Radar
type: streamable-http
url: https://mcp.aiactradar.com/mcp/v1{
"mcpServers": {
"ai-act-radar": {
"httpUrl": "https://mcp.aiactradar.com/mcp/v1"
}
}
}{
"mcpServers": {
"ai-act-radar": {
"type": "http",
"url": "https://mcp.aiactradar.com/mcp/v1"
}
}
}{
"mcpServers": {
"ai-act-radar": {
"url": "https://mcp.aiactradar.com/mcp/v1"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.aiactradar.com%2Fmcp%2Fv1&type=streamable_http&id=ai-act-radar&name=AI%20Act%20Radar
It answered our last check on 17 October 2026 in 177 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by aiactradar.com and served from mcp.aiactradar.com, the vendor's own domain: https://mcp.aiactradar.com/mcp/v1.
4, as returned by the server's own tools/list on 9 September 2026: get_obligation_for_role, lookup_article, query_ai_act_updates, summarize_changes_since.
It answered our last check on 17 October 2026 in 177 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.aiactradar.com/mcp/v1. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.aiactradar. Endpoint host: mcp.aiactradar.com. ARD identifier: urn:air:com.aiactradar:mcp:ai-act-radar.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.