Skip to content

Testez votre tracking MCP server

eu.dhsdigital/testez-votre-trackingdhsdigital.eustreamable-httpv1.9.55Scanned

Free website tracking audit, no account needed: GTM, GA4, Meta Pixel, Consent Mode v2, server-side

1 tool: 1 only read.

Tools: 0 delete, 0 irreversible, 0 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Testez votre tracking MCP server can do

The Testez votre tracking MCP server is published by dhsdigital.eu, a domain the MCP Registry verified. It has 1 tool. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool brings in text other people can write (tester_tracking); 1 tool can send data out of your system (tester_tracking).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.9.55.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

1 tool

Only reads 1Show 1 read-only tool
  • tester_trackingAnalyse 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.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "analyse": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "analyse" and "web": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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/

    Annotations the server declares

    • title: Tester le tracking d’un site
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:53 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Posture changes

  1. Nov 13, 2026
    • RFC 9728 protected resource metadata: https://dhsdigital.eu/.well-known/oauth-protected-resource to none
    • Authorization servers: https://dhsdigital.eu to none
    • Dynamic client registration: no to not observed
    • Client ID metadata documents: yes to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: https://dhsdigital.eu/.well-known/oauth-protected-resource -> none; Authorization servers: https://dhsdigital.eu -> none; Dynamic client registration: no -> not observed (and 1 m…View diff
    • RFC 9728 protected resource metadata: https://dhsdigital.eu/.well-known/oauth-protected-resource to none
    • Authorization servers: https://dhsdigital.eu to none
    • Dynamic client registration: no to not observed
    • Client ID metadata documents: yes to not observed

Install

Pinned to version 1.9.55. Values in angle brackets are yours to fill in.

claude mcp add --transport http testez-votre-tracking https://dhsdigital.eu/wp-json/dhs-audit/v1/mcp
claude mcp add --transport http testez-votre-tracking https://dhsdigital.eu/wp-json/dhs-audit/v1/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__testez-votre-tracking__tester_tracking"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as testez-votre-tracking. Review it before you use it.

Capability tags behind 1 rule
  • mcp__testez-votre-tracking__tester_tracking untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/eu.dhsdigital/testez-votre-tracking/verify?hash=47e64df4b4c6a5e03411ba05e3063d6f7f49ad50996f3bf91ce222ef31dedf27" | jq -e '.changed == false'

Pinned hash 47e64df4b4c6, from Nov 16, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/eu.dhsdigital/testez-votre-tracking/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for eu.dhsdigital/testez-votre-tracking
[![Anlyon Radar](https://radar.anlyon.com/badge/eu.dhsdigital/testez-votre-tracking.svg)](https://radar.anlyon.com/servers/eu.dhsdigital/testez-votre-tracking)

Source: MCP Registry · repository. Synced Nov 16, 2026, 15:17 UTC.

Testez votre tracking MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Testez votre tracking MCP server safe?

No scan can promise that. What its definitions show: 1 tool, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Testez votre tracking MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Testez votre tracking MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Testez votre tracking MCP server have?

1 tool: 1 read. tester_tracking.

Does the Testez votre tracking MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Testez votre tracking MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): tester_tracking.

Has the Testez votre tracking MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.