GDPRWise

eu.gdprwisePublished by gdprwise.euOfficial publisherv1.0.0Updated Oct 29, 2026

GDPR compliance for SMEs: query and update your processing register, vendors and compliance items

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote GDPR compliance server for SMEs that lets an assistant query and update a processing register, vendors and compliance items.

What you can do
  • Query the processing register of processing activities.
  • Look up and update vendor records.
  • Review and update compliance items.
  • All actions run against the user's GDPRWise account through a hosted endpoint.
When to use it
Useful for small and medium businesses that already keep their GDPR administration in GDPRWise and want an assistant to look up or maintain register entries, vendors and compliance tasks without switching tools.
Requirements
A remote MCP endpoint at api.gdprwise.eu over streamable HTTP; OAuth authentication is required, so a GDPRWise account with access to the relevant organisation is needed. No environment variables or headers are declared.
Before you install
The server can change compliance records, including the processing register, vendors and compliance items, so review edits before confirming. It handles GDPR-related business data held in a third-party service; access is granted through OAuth, so check which account and organisation the connection is authorised for.

Installation

In SourceWeft

  1. Open GDPRWise 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/eu.gdprwise%2Fgdprwise/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": {
    "gdprwise": {
      "type": "http",
      "url": "https://api.gdprwise.eu/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. v1.0.0LatestOct 29, 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.