# AI Act Radar (remote · mcp.aiactradar.com)

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

- Trust score: 56/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-09

## Components

- remote · `mcp.aiactradar.com`: 56/100 (this document), [markdown](https://verifymcp.io/servers/com-aiactradar-ai-act-radar/mcp-v1.md), [page](https://verifymcp.io/servers/com-aiactradar-ai-act-radar/mcp-v1)

## Channel facts

- Endpoint: `https://mcp.aiactradar.com/mcp/v1`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-09.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 470 tokens (~117/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-aiactradar-ai-act-radar https://mcp.aiactradar.com/mcp/v1
```

### Codex

```toml
[mcp_servers.com-aiactradar-ai-act-radar]
url = "https://mcp.aiactradar.com/mcp/v1"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-aiactradar-ai-act-radar": {
      "type": "remote",
      "url": "https://mcp.aiactradar.com/mcp/v1",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-aiactradar-ai-act-radar --url https://mcp.aiactradar.com/mcp/v1 --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-aiactradar-ai-act-radar:
    url: "https://mcp.aiactradar.com/mcp/v1"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-09 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-07 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-06 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-05 (score 53, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-04 (score 53)

First indexed and scored.

## MCP tools (4)

### `query_ai_act_updates` (~213 tokens)

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.

Input parameters:

- `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.

### `get_obligation_for_role` (~82 tokens)

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.

Input parameters:

- `risk_category` (string, required): The AI Act risk classification of the system you offer or use.
- `role` (string, required): The AI Act role you operate as.

### `summarize_changes_since` (~85 tokens)

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.

Input parameters:

- `language` (string)
- `since` (string, required): ISO 8601 date; the digest covers everything from this date forward.
- `topics` (array): Restrict digest to these topics. Optional.

### `lookup_article` (~90 tokens)

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.

Input parameters:

- `article` (string, required): Article identifier — e.g. "Art. 53", "Art. 53(1)(d)", "Annex III", "Recital 60".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-aiactradar-ai-act-radar/mcp-v1#diagnostics

## Score history

- 2026-08-09: 56
- 2026-08-08: 55
- 2026-08-07: 55
- 2026-08-06: 54
- 2026-08-05: 53
- 2026-08-04: 53

## Links

- Remote endpoint: https://mcp.aiactradar.com/mcp/v1
- Authorisation metadata: https://mcp.aiactradar.com/.well-known/oauth-protected-resource/mcp/v1
- Repository: https://github.com/ligea-gmbh/aiactradar-examples
- Website: https://aiactradar.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-aiactradar-ai-act-radar/mcp-v1.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-aiactradar-ai-act-radar/mcp-v1.json
- HTML version of this page: https://verifymcp.io/servers/com-aiactradar-ai-act-radar/mcp-v1