StackLégal MCP Server

by stacklegal Your server? Claim it

not responding

StackLégal is listed as active in the registry but did not answer our last check. It exposes 3 tools.

GDPR provider fiches and a static cookie scan before consent.

Uptime history 25 days of history · worst day 0%

25 days agonow

1.1%

Uptime 24h

1 of 91 checks

Tools

read from the server

1435 ms

Response time

average over 24h

open, no key

Access

streamable-http

StackLégal does not always answer

Over the last week it answered 6.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add catalog --transport http https://stacklegal.eu/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://stacklegal.eu/api/mcp

~/.codex/config.toml

[mcp_servers.catalog]
url = "https://stacklegal.eu/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "catalog": {
      "url": "https://stacklegal.eu/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "catalog": {
      "type": "http",
      "url": "https://stacklegal.eu/api/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

provider

get_provider

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.

providers

list_providers

List StackLégal provider fiches. Same payload as GET /api/v1/providers. Pass ids to request specific slugs, 81 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.

scan

scan_site

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.

Endpoints

URL	Transport	State	Latency	Checked
https://stacklegal.eu/api/mcp	streamable-http	answering	28 ms	11 min ago

Alternatives to StackLégal

same job, measured the same way

PrivacyPill

by lovable-privacy-pill-consent-studio

GDPR cookie banners with Consent Mode v2, plus a free scan of what loads before consent.

9 tools answering

ConsentStack

by consentstack

Set up GDPR and CCPA cookie consent: create a site, publish a banner, scan and categorize trackers.

answering

ConsentLayer

by consentlayer

Cookie consent for GDPR/CCPA: scan sites for trackers, configure consent banners, get install code.

answering

Consentio cookie consent

by getconsentio

GDPR cookie banner with Consent Mode v2: install snippet, cookie scan and site management.

8 tools answering

Katla

by katla

GDPR/CCPA cookie consent: scan sites for cookies, track consent rates, generate privacy policies.

answering

Cookie Compliance

by cookie-compliance

Add a cookie consent banner that blocks trackers before consent and records proof of consent.

8 tools answering

MCP Cookie Consent Audit

by mambabuilt

Audit a site's cookie consent from the EU: trackers before consent, reject, after reject, GPC.

248 installs/wk local only

SkillTriage

by moorai

Scan AI agent skills, MCP server packages and MCP configs before you install them. Static analysis.

4 tools answering

StackLégal — questions

Answers built from our own checks of this server.

What can StackLégal do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_provider, list_providers, scan_site. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is StackLégal working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 1 of 91 checks got a reply (1.1%), average response time 1435 ms. The bar chart above shows every period we have measured.

The registry lists StackLégal as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect StackLégal?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does StackLégal need an API key?

No. StackLégal completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is StackLégal?

It answers our handshake in 1435 ms on average, which is faster than 1% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.