io.github.secureprivacy/secure-privacy-mcp

Name: io.github.secureprivacy/secure-privacy-mcp
Author: io.github.secureprivacy

MCPcommunity

v1.1.1io.github.secureprivacyUnknownUpdated 10mo agonpm GitHub

An MCP server that automatically integrate GDPR-compliant cookie consent banners into websites

A remote Model Context Protocol (MCP) server that enables AI agents like Claude Desktop, GitHub Copilot, and Cursor to automatically integrate GDPR-compliant cookie consent banners into websites with a single command. Built on Cloudflare Workers, this MCP server provides a one-click solution for implementing Secure Privacy's cookie consent management platform, handling domain registration,…

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

10mo agoLast update

Package

Authorio.github.secureprivacy

LicenseUnknown

Version1.1.1

Sourcemcp-registry

npmsecure-privacy-mcp

GitHubsecureprivacy/secure-privacy-mcp.git

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies60 resolved · 2 with advisories

Tool surface1 tool · none privileged

Security scan⚠ Warnings (6)v1.1.1 · 3mo agoHow well does this scan work?

HIGH@modelcontextprotocol/sdk@1.23.0@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse HIGH@modelcontextprotocol/sdk@1.23.0Anthropic's MCP TypeScript SDK has a ReDoS vulnerability HIGH@modelcontextprotocol/sdk@1.23.0Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default MODERATEagents@0.2.35Cloudflare Agents is Vulnerable to Reflected Cross-Site Scripting in the AI Playground's OAuth callback handler+2 more — run forge verify secure-privacy-mcp

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

1 tool · none privileged

Statically extracted from the published packagev1.1.1 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

install_secure_privacy_bannerNo description published

This tool published no description. Forge does not invent one.

0 of 1 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keywords

mcp

Alternatives

Comparing tool surfaces…

io.github.secureprivacy/secure-privacy-mcp

Tools

Tools exposed

No dependency coverage