_ registry / mcp http-sse · checked 1h ago

mcp-typescript server on vercel

https://powerquant.dk

Registry code: 3a37950a67133f42

api record

Read-only EU AI Act tools: Annex III scope, Article 50 check, sourced facts, sha256 verify. Free.

from a public catalogue that lists it, not from the operator

endpoint
https://powerquant.dk/api/mcp
protocol
http-sse ·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 mcp-typescript server on vercel live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is mcp-typescript server on vercel free to use?
Yes — the hub reached it with no key and no payment.
What tools does mcp-typescript server on vercel have?
4 tools: eu_ai_act_facts, verify_deliverable, ai_act_scope_check, art50_transparency_check.
Is mcp-typescript server on vercel 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
100%

90 days 100%· all time 100%

latency
251ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ 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.

  • eu_ai_act_facts unknown never probed

    Slå verificerede EU AI Act/NIS2/Digital Omnibus-fakta op i PowerQuants kildedokumenterede faktabase (kun rækker med status=verified; hver med kilde-URL og verifikationsdato). Input: emne/nøgleord, fx 'art 50', 'omnibus', 'annex iii', 'nis2'. (Verified EU AI Act regulatory facts lookup.)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Emne eller nøgleord at søge efter"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • verify_deliverable unknown never probed

    Verify a PowerQuant deliverable by sha256: signature, issue date, reviewer and whether a regulatory change since issue affects it. Input: the 64-hex sha256 from the document footer or the powerquant.dk/verify/<sha> link. Read-only, no personal data; unknown hash returns found:false. (Verificér en PowerQuant-leverance på sha256: signatur, udstedelsesdato, reviewer og om en regelændring siden udstedelsen påvirker den.)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "sha"
      ],
      "properties": {
        "sha": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "sha256 of the deliverable — 64 hex characters, from the document footer or the /verify/<sha> link"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • ai_act_scope_check unknown 1h ago

    Deterministisk screening af et AI-system/use-case mod EU AI Act: Annex III (høj-risiko-kategorier), Art 5 (forbudt praksis) og Art 50 (transparenssignaler). Regelbaseret nøgleordsscreening — ingen LLM. Output: vurdering, begrundelse, relevante artikler, frister og kildelinks. Generel information, ikke juridisk rådgivning. (Deterministic EU AI Act Annex III scope screening, Danish output.)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "description"
      ],
      "properties": {
        "sector": {
          "type": "string",
          "maxLength": 200,
          "description": "Valgfrit: sektor, fx HR, fintech, energi"
        },
        "purpose": {
          "type": "string",
          "maxLength": 500,
          "description": "Valgfrit: formål med systemet"
        },
        "description": {
          "type": "string",
          "maxLength": 4000,
          "minLength": 10,
          "description": "Beskrivelse af AI-systemet eller use-casen (dansk eller engelsk)"
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • art50_transparency_check unknown 1h ago

    Tjek hvilke EU AI Act Artikel 50-transparenskrav der rammer jeres AI-flader: chatbot/AI-assistent, AI-genereret indhold (tekst/billede/lyd/video), deepfake-risiko og emotion/biometri. Output: konkrete krav, frister (2026-08-02; Art 50(2)-watermarking-grace 2026-12-02 kun for legacy-systemer), tjekliste og kildelinks. Deterministisk, ingen LLM. (EU AI Act Article 50 transparency check, Danish output.)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "chatbot"
      ],
      "properties": {
        "chatbot": {
          "type": "boolean",
          "description": "Har I en chatbot/AI-assistent, der interagerer med brugere?"
        },
        "deepfake_risk": {
          "type": "boolean",
          "description": "Genererer/manipulerer I medieindhold, der kan fremstå ægte (deepfakes)?"
        },
        "ai_generated_content": {
          "type": "array",
          "items": {
            "enum": [
              "tekst",
              "billede",
              "lyd",
              "video",
              "text",
              "image",
              "audio"
            ],
            "type": "string"
          },
          "maxItems": 8,
          "description": "Typer af AI-genereret indhold I udgiver (tom hvis ingen)"
        },
        "emotion_or_biometric": {
          "type": "boolean",
          "description": "Kører I følelsesgenkendelse eller biometrisk kategorisering?"
        }
      },
      "additionalProperties": false
    }
    arguments 39 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 3a37950a67133f42.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3a37950a67133f42/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/3a37950a67133f42/badge.svg)](https://brick.blue/agent/3a37950a67133f42?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.