Consent Audit Eu

io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.2Updated Oct 24, 2026

Finds the analytics, pixels, fonts and embeds that fire before your cookie banner is answered - in t

The publisher's own server: audit.domains - Domain Valuation

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Local MCP server that reportedly detects analytics, pixels, fonts and embeds firing before a cookie banner is answered.

What you can do
  • The manifest lists no tools, so the exact operations are not documented.
  • The registry description says it finds analytics, pixels, fonts and embeds that fire before a cookie banner is answered.
  • The README does not describe the server at all; it is a short note about VS Code themes by the same maker.
When to use it
Possibly when you want an assistant to check a site's consent behavior, such as tags loading before the banner is answered. The available evidence is too thin to confirm what it actually does.
Requirements
Runs as a local process over stdio, started with npx from the npm package. No authentication, environment variables or headers are declared. Desktop-only; not executable on the web.
Before you install
The README content does not match the described purpose, so the package's real behavior is unverified. No tools are listed, and no credentials or data-handling details are given; review the package before running it.

Installation

In SourceWeft

  1. Open Consent Audit Eu in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.2LatestSep 19, 2026
  2. v0.1.1Sep 18, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Audit integrations