ConsentLayer

com.consentlayerPublished by consentlayer.comOfficial publisherv0.1.1Updated Oct 24, 2026

Cookie consent for GDPR/CCPA: scan sites for trackers, configure consent banners, get install code.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server for cookie consent compliance that lets an assistant scan sites for trackers, configure consent banners and retrieve install code.

What you can do
Scan websites for trackers as part of GDPR/CCPA cookie consent work. Configure consent banners for a site. Retrieve install code for adding the consent setup to a site. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when an assistant is helping with GDPR or CCPA cookie consent: auditing a site's trackers, setting up a consent banner, or getting the code to install it.
Requirements
A remote endpoint at api.consentlayer.com over streamable HTTP. OAuth authentication is required, so a ConsentLayer account and an OAuth-capable client are needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access to a ConsentLayer account, so review the scopes requested. Configuring banners and generating install code changes site consent settings, and scanning submits site details to a third-party service.

Installation

In SourceWeft

  1. Open ConsentLayer in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.consentlayer%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "consentlayer": {
      "type": "http",
      "url": "https://api.consentlayer.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.