AI Act Radar
REMOTE · MCP.AIACTRADAR.COM · SCANNED SEP 28
EU AI Act obligations and updates from ten official sources, incl. the national layer.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 470 tokens (~117/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the AI Act Radar MCP server?
AI Act Radar is a hosted endpoint at https://mcp.aiactradar.com/mcp/v1, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.aiactradar.com
claude mcp add --transport http com-aiactradar-ai-act-radar 'https://mcp.aiactradar.com/mcp/v1'
{
"mcpServers": {
"com-aiactradar-ai-act-radar": {
"url": "https://mcp.aiactradar.com/mcp/v1"
}
}
} {
"servers": {
"com-aiactradar-ai-act-radar": {
"type": "http",
"url": "https://mcp.aiactradar.com/mcp/v1"
}
}
} [mcp_servers.com-aiactradar-ai-act-radar] url = "https://mcp.aiactradar.com/mcp/v1"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-aiactradar-ai-act-radar": {
"type": "remote",
"url": "https://mcp.aiactradar.com/mcp/v1",
"enabled": true
}
}
} openclaw mcp add com-aiactradar-ai-act-radar --url 'https://mcp.aiactradar.com/mcp/v1' --transport streamable-http
mcp_servers:
com-aiactradar-ai-act-radar:
url: "https://mcp.aiactradar.com/mcp/v1" {
"McpServers": {
"com-aiactradar-ai-act-radar": {
"Transport": "http",
"Url": "https://mcp.aiactradar.com/mcp/v1"
}
}
} assistant mcp add com-aiactradar-ai-act-radar -t streamable-http -u 'https://mcp.aiactradar.com/mcp/v1'
{
"mcpServers": {
"com-aiactradar-ai-act-radar": {
"type": "http",
"url": "https://mcp.aiactradar.com/mcp/v1"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Sept 26 0
- Stability: 0.97 → pass security
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://mcp.aiactradar.com/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aiactradar.com | CN=YE1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6bc2b717853c83aab5c9dcd76644231e8a5 |
| SANs: *.aiactradar.com, aiactradar.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.aiactradar.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aiactradar.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.aiactradar.com/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://mcp.aiactradar.com/mcp/v1 | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_obligation_for_role ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| risk_category | string | yes | The AI Act risk classification of the system you offer or use. |
| role | string | yes | The AI Act role you operate as. |
No output schema declared.
No examples provided.
lookup_article ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| article | string | yes | Article identifier — e.g. "Art. 53", "Art. 53(1)(d)", "Annex III", "Recital 60". |
No output schema declared.
No examples provided.
query_ai_act_updates ~213
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 historical regulatory changes affecting AI builders, GPAI providers, or deployers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| severity_min | string | – | Minimum severity. Optional. |
| since | string | – | ISO 8601 timestamp; only events published after this. Optional. |
| source_id | string | – | One of: eurlex, aioffice, aiboard, codeofpractice, haveyoursay, cen, bnetza, bfdi, bsi, cnil, nl-algoritmeregister, oecdai. Optional. |
| topics | array | – | Topic taxonomy. e.g. ["gpai","transparency","high-risk"]. Optional. |
| until | string | – | ISO 8601 timestamp; only events published before this. Optional. |
No output schema declared.
No examples provided.
summarize_changes_since ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| since | string | yes | ISO 8601 date; the digest covers everything from this date forward. |
| topics | array | – | Restrict digest to these topics. Optional. |
No output schema declared.
No examples provided.
What is the AI Act Radar MCP server?
AI Act Radar is an MCP server listed in the public MCP registry as com.aiactradar/ai-act-radar. EU AI Act obligations and updates from ten official sources, incl. the national layer. This page covers its hosted endpoint (https://mcp.aiactradar.com/mcp/v1).
Is the AI Act Radar MCP server safe to use?
AI Act Radar scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AI Act Radar MCP server expose?
AI Act Radar exposes 4 tools: query_ai_act_updates, get_obligation_for_role, summarize_changes_since, lookup_article. Their descriptions and schemas cost roughly 470 tokens of context every time the server is loaded.
Does the AI Act Radar MCP server require authentication?
No. We connected to AI Act Radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI Act Radar MCP server still maintained?
AI Act Radar is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.