Testez votre tracking
REMOTE · DHSDIGITAL.EU
Free website tracking audit, no account needed: GTM, GA4, Meta Pixel, Consent Mode v2, server-side
Available components
Last scanned (23 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Marketing and SEO
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 Security83
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 436 tokens (~436/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.9.26 → 1.9.27 functional
- Server version: 1.9.25 → 1.9.26 functional
- 12 Oct 26 72
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 17 Oct 2026 · Probed https://dhsdigital.eu/wp-json/dhs-audit/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dhsdigital.eu | CN=YR1,O=Let's Encrypt,C=US | 18 Aug 2026 | 16 Nov 2026 | RSA 4096 | SHA256-RSA | 61e4c032f6f0db6929c88d9071ec683ddad |
| SANs: dhsdigital.eu, www.dhsdigital.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 secure
Validation of dhsdigital.eu. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| dhsdigital.eu. | present | 9767 | 8 | Verified |
| dhsdigital.eu. | Verified address RRset verified with the apex keys |
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=15768000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dhsdigital.eu/wp-json/dhs-audit/v1/mcp | Verified | 200 | |
| http (plaintext) | http://dhsdigital.eu/wp-json/dhs-audit/v1/mcp | HTTPS enforced | 301 | https://dhsdigital.eu/wp-json/dhs-audit/v1/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 →
tester_tracking Tester le tracking d’un site (website tracking audit) ~344
Analyse en lecture seule la configuration observable du tracking marketing d’un site web, à partir de la page demandée et de ses conteneurs Google Tag Manager publics. Retourne un score indicatif sur 100, les risques de configuration, les correctifs et les limites de la vérification externe pour Google Tag Manager, GA4, Google Ads, Meta, TikTok, Pinterest, la bannière cookies, le Consent Mode v2 et le tracking server-side (Stape, Addingwell…). Aucun accès aux comptes Google, Meta ou autres, ni clé : l’analyse part de l’adresse publique du site. N’exécute pas le site et ne vérifie ni les événements d’achat ni la réception des données par les plateformes. Outil « Testez votre tracking », édité par DHS Digital. Cas d’usage : test, audit ou vérification du tracking d’un site précis, à la demande de l’utilisateur. English: read-only website tracking audit / tracking checker (Google Tag Manager, GA4, Google Ads conversion tags, Meta Pixel, TikTok, cookie banner, Consent Mode v2, server-side tagging with Stape or Addingwell); no account access, OAuth or API key needed, it works from the public URL; French-language report with a score out of 100. Documentation : https://dhsdigital.eu/tracking/assistants-ia/
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | synthese : note et 3 priorités ; complet (par défaut) : les 13 points, ce qui est en place et les limites |
| url | string | yes | Adresse du site à tester (domaine ou URL), par exemple www.exemple.fr |
| Name | Type | Req | Description |
|---|---|---|---|
| analyse_le | string | – | – |
| autres_points | array | – | En synthèse : points détectés au-delà des 3 premières actions |
| confiance | object | – | – |
| deja_en_place | array | – | – |
| familles | array | – | – |
| http_status | integer | – | – |
| limites | array | – | – |
| message | string | – | – |
| non_verifiable | array | – | – |
| note | string|null | – | – |
| ordre_actions | array | – | – |
| par_ou_commencer | string | – | – |
| points_a_corriger | array | – | – |
| raison | string | – | Motif d’une analyse non concluante (unreachable, blocked, js_rendered, thin_page, http_error, deadline) |
| rapport_complet | string | yes | URL du rapport complet correspondant au site analysé |
| score | integer|null | – | – |
| site | string | – | – |
| site_de_l_editeur | boolean | – | – |
| sites_lies | array | – | – |
| source | string | yes | – |
| statut | string | yes | ok, inconclusive, invalid, limited, busy… |
No examples provided.
How do I install the Testez votre tracking MCP server?
Testez votre tracking is a hosted endpoint at https://dhsdigital.eu/wp-json/dhs-audit/v1/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 · dhsdigital.eu
claude mcp add --transport http eu-dhsdigital-testez-votre-tracking 'https://dhsdigital.eu/wp-json/dhs-audit/v1/mcp'
What is the Testez votre tracking MCP server?
Testez votre tracking is an MCP server listed in the public MCP registry as eu.dhsdigital/testez-votre-tracking. Free website tracking audit, no account needed: GTM, GA4, Meta Pixel, Consent Mode v2, server-side. This page covers its hosted endpoint (https://dhsdigital.eu/wp-json/dhs-audit/v1/mcp).
Is the Testez votre tracking MCP server safe to use?
Testez votre tracking scores 74 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 Testez votre tracking MCP server expose?
Testez votre tracking exposes 1 tool: tester_tracking. Their descriptions and schemas cost roughly 344 tokens of context every time the server is loaded.
Does the Testez votre tracking MCP server require authentication?
No. We connected to Testez votre tracking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Testez votre tracking MCP server still maintained?
Testez votre tracking is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.