Sovereign AI Act MCP
REMOTE · WWW.REGULATORYAI.EU · 2 COMPONENTS
Classify any AI system under the EU AI Act: risk tier + binding Articles, verbatim from the law.
Available components
Last scanned (14 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Security
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 350 tokens (~70/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 25% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 60. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 43 to 53. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 +1
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Oct 2026 · Probed https://www.regulatoryai.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.regulatoryai.eu | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4b694e6ee92e458d13b81fd9743b6d15 |
| SANs: www.regulatoryai.eu | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.regulatoryai.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| regulatoryai.eu. | absent | 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://www.regulatoryai.eu/mcp | Verified | 200 | |
| http (plaintext) | http://www.regulatoryai.eu/mcp | HTTPS enforced | 301 | https://www.regulatoryai.eu/mcp |
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 →
classify_ai_system ~98
Classify an AI system under the EU AI Act (Regulation (EU) 2024/1689): risk tier (prohibited/high_risk/limited/minimal) + Annex III category + binding Articles, grounded verbatim in the law. Use whenever asked if an AI system is high-risk/prohibited or what obligations apply.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Plain-language description of the AI system. |
| language | string | – | – |
No output schema declared.
No examples provided.
get_compliance_deadlines ~29
Canonical EU AI Act application dates (post Digital-Omnibus) + fine tiers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_article ~53
Verbatim text of an original EU AI Act Article (1–113) or inserted Article 4a, 60a or 75a–75d.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| number | – | yes | – |
No output schema declared.
No examples provided.
review_feature ~127
EU AI Act CO-PILOT review for builders: pass a feature, spec or behaviour you are about to ship and get a ship/caution/stop signal (OK / TRANSPARENCY / REVIEW REQUIRED / STOP), the binding Articles, the obligations that apply, red flags and concrete next steps — grounded verbatim in Regulation (EU) 2024/1689. Use proactively while designing or coding an AI feature, before it ships.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The AI feature, spec or behaviour you are about to build/ship. |
| language | string | – | – |
No output schema declared.
No examples provided.
search_eu_ai_act ~43
Full-text search across the EU AI Act corpus (Articles, Recitals, Annexes).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Sovereign AI Act MCP server?
Sovereign AI Act MCP is a hosted endpoint at https://www.regulatoryai.eu/mcp, 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 · www.regulatoryai.eu
claude mcp add --transport http eu-regulatoryai-sovereign-ai-act-mcp 'https://www.regulatoryai.eu/mcp'
What is the Sovereign AI Act MCP server?
Sovereign AI Act MCP is listed in the public MCP registry as eu.regulatoryai/sovereign-ai-act-mcp. Classify any AI system under the EU AI Act: risk tier + binding Articles, verbatim from the law. This page covers its hosted endpoint (https://www.regulatoryai.eu/mcp).
Is the Sovereign AI Act MCP server safe to use?
Sovereign AI Act MCP scores 74 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 Sovereign AI Act MCP server expose?
Sovereign AI Act MCP exposes 5 tools: classify_ai_system, lookup_article, search_eu_ai_act, get_compliance_deadlines, review_feature. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.
Does the Sovereign AI Act MCP server require authentication?
No. We connected to Sovereign AI Act MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sovereign AI Act MCP server still maintained?
Sovereign AI Act MCP is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.