sovereign-ai-act
Registry code: f2c0955392bc0395
Classify any AI system under the EU AI Act: risk tier + binding Articles, verbatim from the law.
from a public catalogue that lists it, not from the operator
- endpoint
- https://www.regulatoryai.eu/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is sovereign-ai-act live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is sovereign-ai-act free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does sovereign-ai-act have?
- 5 tools: lookup_article, search_eu_ai_act, review_feature, classify_ai_system, get_compliance_deadlines.
- Is sovereign-ai-act safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.4%· all time 99.4%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- classify an ai system under the eu ai act
- look up an eu ai act article
- get eu ai act compliance deadlines
- review a product feature for ai act compliance
- search the eu ai act text
- takes → gives
- text → data, text
- tools
- 5 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_compliance_deadlines reads open 5h ago
Canonical EU AI Act application dates (post Digital-Omnibus) + fine tiers.
{ "type": "object", "properties": {} }arguments 4 lineslookup_article reads unknown 5h ago
Verbatim text of an original EU AI Act Article (1–113) or inserted Article 4a, 60a or 75a–75d.
{ "type": "object", "required": [ "number" ], "properties": { "number": { "oneOf": [ { "type": "integer", "maximum": 113, "minimum": 1 }, { "enum": [ "4a", "60a", "75a", "75b", "75c", "75d" ], "type": "string" } ] }, "language": { "type": "string", "default": "en" } } }arguments 32 linessearch_eu_ai_act reads unknown 5h ago
Full-text search across the EU AI Act corpus (Articles, Recitals, Annexes).
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string" }, "language": { "type": "string", "default": "en" } } }arguments 15 linesreview_feature reads unknown never probed
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.
{ "type": "object", "required": [ "input" ], "properties": { "input": { "type": "string", "description": "The AI feature, spec or behaviour you are about to build/ship." }, "language": { "type": "string", "default": "en" } } }arguments 16 linesclassify_ai_system reads unknown never probed
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.
{ "type": "object", "required": [ "description" ], "properties": { "language": { "type": "string", "default": "en" }, "description": { "type": "string", "description": "Plain-language description of the AI system." } } }arguments 16 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf2c0955392bc0395.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f2c0955392bc0395/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f2c0955392bc0395?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.