_ registry / mcp streamable-http · checked 55m ago

stacklegal

https://stacklegal.eu

Registry code: 6a177f52375bd87b

api record

GDPR provider fiches and a static cookie scan before consent.

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

endpoint
https://stacklegal.eu/api/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 stacklegal live?
Yes — it answered the hub's last check (checked 55m ago). It answered 100% of checks over the last 30 days.
Is stacklegal free to use?
Yes — the hub reached it with no key and no payment.
What tools does stacklegal have?
3 tools: get_provider, scan_site, list_providers.
Is stacklegal 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
496ms

last good check

priced tools
0

of 3 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

_ what it can do 3 tools
1 open 2 never probed 1 of 3 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.

  • list_providers open 55m ago

    List StackLégal provider fiches. Same payload as GET /api/v1/providers. Pass ids to request specific slugs, 73 at most, in that order. Omit ids for the full catalog. Unknown slugs are returned in unknown and the rest still succeeds. lang defaults to French.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional slugs or aliases. Omit for the full catalog."
        },
        "lang": {
          "type": "string",
          "description": "Optional shipped locale. Omit for French."
        }
      }
    }
    arguments 17 lines
  • get_provider unknown 55m ago

    Look up one StackLégal provider fiche by canonical slug, alias (for example ga), or exact catalog name. Returns the same object as GET /api/v1/providers/{slug}. A name match is not a legal qualification. lang defaults to French.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug_or_name"
      ],
      "properties": {
        "lang": {
          "type": "string",
          "description": "Optional shipped locale. Omit for French. Slugs do not change with language."
        },
        "slug_or_name": {
          "type": "string",
          "description": "Canonical slug, alias, or exact provider name as shown on the fiche."
        }
      }
    }
    arguments 17 lines
  • scan_site unknown 55m ago

    Fetch one public URL once, without a consent cookie, and report trackers present on the first HTML response and Set-Cookie headers. JavaScript is not executed. Each tracker includes a provider slug when the scanner catalog maps it to a fiche, and the result links to the StackLégal scanner page. This is not a legal qualification. The address and the caller IP are not stored. Limited to a few scans per 10 minutes.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public http or https URL on port 80 or 443, with no username in the address."
        }
      }
    }
    arguments 13 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 6a177f52375bd87b.

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

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.