mcp server
AI Act Radar
EU AI Act obligations and updates from ten official sources, incl. the national layer.
Description as published by the maintainer. Source
- version 0.1.0
- active
active — Most recent push to the repository was 2026-08-04.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_obligation_for_role(role, risk_category)- 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. Required: role, risk_category.
lookup_article(article)- 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. Required: article.
query_ai_act_updates(limit, since, until, topics, source_id, severity_min)- 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_since(since, topics, language)- 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. Required: since.
Last successful function declaration observed on . Source: https://mcp.aiactradar.com/mcp/v1. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.aiactradar.com/mcp/v1.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-04 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-04 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-08-04 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.aiactradar.com | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | mcp.aiactradar.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json