MCP.Market

AI Act Radar MCP server

online · 100% uptime
by aiactradar.com·com.aiactradar/ai-act-radar·v0.1.0
No reviews yet

EU AI Act obligations and updates from ten official sources, incl. the national layer.

B81/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B81/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed AI Act Radar yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

AI Act Radar tools (4)

write = sends, deletes, buys or posts
  • get_obligation_for_roleFree

    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.

  • lookup_articleFree

    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.

  • query_ai_act_updatesFree

    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.

  • summarize_changes_sinceFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 388ms20/20
  • Tool poisoning4 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 51 days ago12/15
  • Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How AI Act Radar compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
81/100
higher than 62% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
115 ms
faster than 80% of 30,031 servers

What its tools let an agent do: 4 read

Install AI Act Radar in Claude Code, Cursor or VS Code

claude mcp add --transport http ai-act-radar https://mcp.aiactradar.com/mcp/v1
Add to Cursor

What the publisher says

From the AI Act Radar repository's README, as published. We do not edit it. Read it on GitHub

aiactradar-examples

Reference webhook receivers for AI Act Radar. Each subdirectory is a self-contained, runnable example for one platform.

What every receiver does

  1. Reads the raw request body (signature is over the bytes, not the parsed JSON).
  2. Verifies X-AIAR-Timestamp is within 300 seconds of now.
  3. Verifies X-AIAR-Signature (v1=) using HMAC-SHA-256 over . in constant time.
  4. Checks an idempotency key (event.id) before doing real work — retries are normal.
  5. Returns 2xx within 5 seconds; otherwise the dispatcher retries with exponential backoff.

The verification is identical across platforms; only the platform glue differs.

Examples

Try it without signing up

Each example has a test.sh that signs a sample event with a local secret and posts it to the running receiver. You can run the full loop on your laptop in under five minutes:

cd cloudflare-workers
cp .dev.vars.example .dev.vars   # set AIA_SECRET to anything
npm install && npm run dev       # starts http://localhost:8787
# in another terminal:
bash test.sh                     # posts a signed sample event

Going to production

  • Store AIA_SECRET in your platform's secret manager. Never commit it.
  • Rotate the secret in the AI Act Radar dashboard at least every 90 days.
  • Subscribe to the dispatcher's webhook health channel — bounced deliveries surface there before customers notice.
  • Idempotency stores need a TTL of at least 7 days; the dispatcher retries up to 24h.

License

MIT.

AI Act Radar is operated by ligea GmbH, Karlsruhe. Information only — not legal advice.

Nothing above is checked by us. What we check is on the safety report.

AI Act Radar: common questions

Is AI Act Radar MCP server safe?
Mostly: it is graded B (81/100). Read the AI Act Radar safety report
How do I install AI Act Radar?
It runs remotely at mcp.aiactradar.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does AI Act Radar need an API key?
Yes. The registry entry asks for Authorization.
Is AI Act Radar maintained?
The last commit was 92 days ago (2026-08-04). The latest release is v0.1.0.
Is AI Act Radar up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does AI Act Radar compare with other MCP servers?
safety score 81/100 (higher than 62% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.