StackLégal
REMOTE · STACKLEGAL.EU
GDPR provider fiches and a static cookie scan before consent.
Available components
Last scanned (59 minutes ago)
Scores higher than 82% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 331 tokens (~110/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 0
- Tool “list_providers” rewrote its description, which is the text the model reads security
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://stacklegal.eu/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stacklegal.eu | CN=YR1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | RSA 2048 | SHA256-RSA | 5e7802525ba6da8cea0620b16842b226c06 |
| SANs: stacklegal.eu | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of stacklegal.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| stacklegal.eu. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stacklegal.eu/api/mcp | Verified | 200 | |
| http (plaintext) | http://stacklegal.eu/api/mcp | HTTPS enforced | 308 | https://stacklegal.eu/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_provider Get a provider ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Optional shipped locale. Omit for French. Slugs do not change with language. |
| slug_or_name | string | yes | Canonical slug, alias, or exact provider name as shown on the fiche. |
No output schema declared.
No examples provided.
list_providers List providers ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Optional slugs or aliases. Omit for the full catalog. |
| lang | string | – | Optional shipped locale. Omit for French. |
No output schema declared.
No examples provided.
scan_site Scan a site before consent ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http or https URL on port 80 or 443, with no username in the address. |
No output schema declared.
No examples provided.
How do I install the StackLégal MCP server?
StackLégal is a hosted endpoint at https://stacklegal.eu/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · stacklegal.eu
claude mcp add --transport http eu-stacklegal-catalog 'https://stacklegal.eu/api/mcp'
What is the StackLégal MCP server?
StackLégal is an MCP server listed in the public MCP registry as eu.stacklegal/catalog. GDPR provider fiches and a static cookie scan before consent. This page covers its hosted endpoint (https://stacklegal.eu/api/mcp).
Is the StackLégal MCP server safe to use?
StackLégal scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the StackLégal MCP server expose?
StackLégal exposes 3 tools: get_provider, list_providers, scan_site. Their descriptions and schemas cost roughly 331 tokens of context every time the server is loaded.
Does the StackLégal MCP server require authentication?
No. We connected to StackLégal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the StackLégal MCP server still maintained?
StackLégal is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.