MCP server
AI Act Radar exposes its data through the Model Context Protocol (MCP) so AI agents can query EU AI Act updates as a tool, not as a data dump.
Endpoint: https://mcp.aiactradar.com/mcp/v1
Discovery: GET /.well-known/mcp.json
Auth: Authorization: Bearer aiactr_… (same key as the REST API)
Why MCP and not just REST
If you operate an AI agent — Claude, Cursor, Continue, an in-house assistant — you don't want to plumb HTTP calls through prompts. You want the agent to ask "what changed in GPAI obligations last week?" and have the answer arrive as structured tool output.
Tools we expose
| Tool | Returns |
|---|---|
query_ai_act_updates | Filtered events (since, source, topics, severity) |
get_obligation_for_role | Articles + obligations for (role × risk-category) |
summarize_changes_since | Markdown digest grouped by severity |
lookup_article | Events that reference a specific Article / Annex / Recital |
See tool reference for input schemas.
Setup guides
- Cursor
- Claude Desktop
- Continue.dev (coming soon)
- Custom JSON-RPC 2.0 client — protocol version
2024-11-05
Disclaimer
Every tool response carries a disclaimer field. The MCP
server is a data layer. It does not provide legal advice, and your agent
should reflect that downstream.