GDPR provider fiches and a static cookie scan before consent.
Connect Remote server
claude mcp add --transport http catalog https://stacklegal.eu/api/mcp
{
"mcpServers": {
"catalog": {
"url": "https://stacklegal.eu/api/mcp"
}
}
}
{
"servers": {
"catalog": {
"type": "http",
"url": "https://stacklegal.eu/api/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://stacklegal.eu/api/mcp
Tools 3 found in our last check
get_providerLook 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.
list_providersList 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_siteFetch 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ég…
Details
| Endpoint | https://stacklegal.eu/api/mcp (Streamable HTTP) |
| First published | 14 Oct 2026 |
| Last updated | 14 Oct 2026 |
| Registry name | eu.stacklegal/catalog |
More security servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
