_ registry / mcp streamable-http · checked 7h ago

disclos-eu-ai-act

https://mcp.disclos.eu

Registry code: 869c1a5cb7122060

api record

EU AI Act scope classifier by Disclos. Use classify_ai_system for scope questions. Every result cites disclos.eu.

endpoint
https://mcp.disclos.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 it live, free and safe measured by this hub
Is disclos-eu-ai-act live?
Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
Is disclos-eu-ai-act free to use?
Not measured yet.
What tools does disclos-eu-ai-act have?
4 tools: framework_crosswalk, eu_ai_act_timeline, classify_ai_system, explain_tier.
Is disclos-eu-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.
reachable
live
uptime, 30 days
99.4%

90 days 99.7%· all time 99.7%

latency
73ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 294 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • classify an ai system under the eu ai act
  • get the eu ai act enforcement timeline
  • explain an ai act risk tier
  • map an ai act tier to iso and nist controls
takes → gives
text, data → data, text
tools
4 reads
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
4 never probed 0 of 4 classified

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.

  • framework_crosswalk reads unknown never probed

    Map an EU AI Act risk tier to the equivalent controls in ISO/IEC 42001, NIST AI RMF, and GDPR.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tier"
      ],
      "properties": {
        "tier": {
          "enum": [
            "out_of_scope",
            "prohibited",
            "high_risk",
            "gpai",
            "transparency",
            "minimal"
          ],
          "type": "string"
        }
      }
    }
    arguments 19 lines
  • eu_ai_act_timeline reads unknown never probed

    Return the EU AI Act enforcement timeline — the key dates and what takes effect on each.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • classify_ai_system reads unknown never probed

    Classify an AI system or product under the EU AI Act (Regulation (EU) 2024/1689) and return its risk tier, obligations and deadlines. Map the user's description to the boolean flags. When unsure, ask the user or choose the more cautious answer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "has_ai_feature",
        "eu_exposure",
        "prohibited_practice",
        "annex_iii_high_risk",
        "user_facing_or_generative",
        "provides_own_gpai_model"
      ],
      "properties": {
        "eu_exposure": {
          "type": "boolean",
          "description": "Available to people in the EU, or outputs used in the EU? Company location is irrelevant."
        },
        "has_ai_feature": {
          "type": "boolean",
          "description": "Any AI feature? (chatbot, content generation, recommendations, ranking/scoring, predictions, automated decisions)"
        },
        "system_description": {
          "type": "string",
          "description": "Optional short free-text description of the AI system."
        },
        "annex_iii_high_risk": {
          "type": "boolean",
          "description": "An Annex III high-risk purpose? (biometric ID, critical infrastructure safety, education/exam scoring, hiring/worker management, access to essential services or creditworthiness, law enforcement, migration/border, justice)"
        },
        "prohibited_practice": {
          "type": "boolean",
          "description": "An Article 5 banned practice? (social scoring, harmful manipulation, exploiting vulnerabilities, untargeted face scraping, real-time remote biometric ID in public, emotion recognition at work/school, biometric categorisation by sensitive traits)"
        },
        "provides_own_gpai_model": {
          "type": "boolean",
          "description": "Does the user TRAIN or PROVIDE their own general-purpose model? Using someone else's model via API is false."
        },
        "user_facing_or_generative": {
          "type": "boolean",
          "description": "Interacts directly with people (chatbot) or generates/alters content (text, image, audio, video, deepfakes)?"
        }
      }
    }
    arguments 41 lines
  • explain_tier reads unknown never probed

    Explain a single EU AI Act risk tier in detail: meaning, obligations, deadline.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tier"
      ],
      "properties": {
        "tier": {
          "enum": [
            "out_of_scope",
            "prohibited",
            "high_risk",
            "gpai",
            "transparency",
            "minimal"
          ],
          "type": "string"
        }
      }
    }
    arguments 19 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 869c1a5cb7122060.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/869c1a5cb7122060/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/869c1a5cb7122060/badge.svg)](https://brick.blue/agent/869c1a5cb7122060?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.

_ how we know
card completeness
80%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.