Developer · Remote MCP server
ConsentLayer
Cookie consent for GDPR/CCPA: scan sites for trackers, configure consent banners, get install code.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.consentlayer/mcp- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-03
- Updated
- 2026-07-03
- Publisher
- com.consentlayer
- Namespace
- Namespace verified by the MCP Registry via the domain consentlayer.com · how
- Website
- consentlayer.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.consentlayer.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect ConsentLayer
ConsentLayer is a remote MCP server: there is nothing to install. Its endpoint is https://api.consentlayer.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Connectivity IndexMachine-readable FCC pre-diligence corpus for multifamily broadband infrastructure scenarios. | Remote · HTTPLive check: ✗ no handshake |
| ConnectWise Control MCPManage ConnectWise Control (ScreenConnect) remote support and access sessions from one CLI or agent. | Local · stdio |
| ConsensusCoordination for AI coding agents: declare plans, catch design conflicts early, share team memory. | Remote · HTTPLive check: ✗ no handshake |
| Consent Proof Record LintReads the consent record your code stored and names every proof field GDPR Article 7(1) needs and yo. | Local · stdio |
| Constitution LintStatic linter for CLAUDE.md-style agent constitution files: 10 operational-guardrail checks. | Remote · HTTPLive check: ✓ handshake |
| Constitution LintStatic linter for CLAUDE.md-style agent constitution files: 10 operational-guardrail checks. | Remote · HTTPLive check: ✓ handshake |
| Constraints RegistryPolicy-as-code guardrails for AI coding agents, validated via OPA, Conftest, Checkov & Semgrep. | Local · stdio |
| Contabo (VPS) MCP ServerContabo API (v1.0.0) as MCP tools for cloud provisioning, and management. Powered by HAPI MCP server. | Remote · HTTPLive check: ✗ no handshake |