Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AI Act Radar

REMOTE · MCP.AIACTRADAR.COM

EU AI Act obligations and updates from 22 official EU and national sources. No key needed.

+6 this week 76 Trust /100

Last scanned (17 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 831 tokens (~207/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 18 Nov 26 +6
    • Authorization: unverified → partial ▲ security
    • Tool “get_obligation_for_role” rewrote its description, which is the text the model reads security
    • Tool “lookup_article” rewrote its description, which is the text the model reads security
    • Tool “query_ai_act_updates” rewrote its description, which is the text the model reads security
    • Tool “summarize_changes_since” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 83% → 92% ▲ functional
    • Schema quality: good → excellent functional
    • Server version: 0.2.0 → 0.2.2 functional
    • Server version: 0.1.0 → 0.2.0 functional
    • “query_ai_act_updates” reworded the description of “limit” cosmetic
    • “query_ai_act_updates” reworded the description of “since” cosmetic
    • “query_ai_act_updates” reworded the description of “source_id” cosmetic
    • “query_ai_act_updates” reworded the description of “topics” cosmetic
    • “query_ai_act_updates” reworded the description of “until” cosmetic
    • “summarize_changes_since” reworded the description of “since” cosmetic
    • “lookup_article” reworded the description of “article” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 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
Diagnostics

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 21 Nov 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=YE2,O=Let's Encrypt,C=US 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA384 6b34ce33db85077669bca6229a684b0df56
SANs: *.aiactradar.com, aiactradar.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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. DS published 19718 13 Verified
aiactradar.com. No DS 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
MCP tools · 4 exposed · ~831 tokens

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 →

Tool Tokens
get_obligation_for_role ~88

Look up the AI Act obligations for a specific role and AI-system risk category. Returns the relevant articles, deadlines, official sources and the most recent events for the primary article. This is informational, not legal advice.

NameTypeReqDescription
risk_categorystringyesThe AI Act risk classification of the system you offer or use.
rolestringyesThe AI Act role you operate as.

No output schema declared.

No examples provided.

lookup_article ~168

Look up a reference to Regulation (EU) 2024/1689 (e.g. "Art. 53(1)(d)", "Annex III", "Recital 60") and return related events plus the EUR-Lex URL. Matches whole references: "Art. 5" finds Art. 5 and Art. 5(1)(b), never Art. 50. References the Regulation does not have (Art. 1 to 113, Annex I to XIII, Recital 1 to 180) return known: false and no EUR-Lex link.

NameTypeReqDescription
articlestringyesArticle identifier, e.g. "Art. 53", "Art. 53(1)(d)", "Annex III", "Recital 60".

No output schema declared.

No examples provided.

query_ai_act_updates ~432

Query EU AI Act regulatory updates from primary sources, newest first. Filters (date range, source, topics, severity) apply to the whole register before limit. Every event has the same shape in all tools: id, source_id, event_type, severity, topics, title_en, title_de, summary_en, summary_de, url_official, url_kind ("official", or "secondary" where no official publication was found), ai_act_articles (array), version, published_at (ISO 8601).

NameTypeReqDescription
limitinteger–Without a key at most 10.
severity_minstring–Minimum severity. Optional.
sincestring–ISO 8601 date or timestamp, e.g. "2026-11-01" or "2026-11-01T00:00:00Z". Only events published at or after this. Optional.
source_idstring–Source id. 22 active sources: aiboard, aioffice, bfdi, bnetza, bsi, cen, cnil, codeofpractice, curia, cz-ctu, digitalstrategy, dsk, ec-spoc, edpb, etsi, eurlex, fra, lv-ptac, nl-algoritmeregister, nl…
topicsarray–Events with at least one of these topics. Fixed taxonomy, see https://docs.aiactradar.com/concepts/topics/. Optional.
untilstring–ISO 8601 date or timestamp, e.g. "2026-11-01" or "2026-11-01T00:00:00Z". Only events published at or before this. Optional.

No output schema declared.

No examples provided.

summarize_changes_since ~143

Generate a structured digest of AI Act regulatory changes since a given date, grouped by severity, in English or German. Useful for weekly compliance reviews or audit prep. Returns Markdown plus event_count (events in the digest) and total_matching. Without a key the digest holds the 10 most severe events.

NameTypeReqDescription
languagestring––
sincestringyesISO 8601 date or timestamp, e.g. "2026-11-01" or "2026-11-01T00:00:00Z". The digest covers everything from this date forward. Required.
topicsarray–Restrict digest to these topics. Optional.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http com-aiactradar-ai-act-radar 'https://mcp.aiactradar.com/mcp/v1'
Common questions

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 22 official EU and national sources. No key needed. 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 76 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 831 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AI Act Radar MCP server?

VerifyMCP ran 12 checks on AI Act Radar, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about AI Act Radar: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.