Dastra

eu.dastraPublished by dastra.euOfficial publisherv1.0.0Updated Oct 29, 2026

GDPR & privacy compliance: records of processing, data breaches, DSRs, risks, audits, AI systems.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote Dastra MCP server that lets an assistant work with GDPR and privacy compliance records: processing activities, breaches, DSRs, risks, audits and AI…

What you can do
  • Work with records of processing activities and other GDPR compliance registers.
  • Handle data subject requests (DSRs) and data breach records.
  • Manage risk and audit entries.
  • Track AI systems within the privacy compliance scope.
  • No tool list is published, so exact operations are not documented.
When to use it
Useful when an assistant should help a privacy or compliance team that already keeps its GDPR records in Dastra, for example to look up or update processing records, breaches, DSRs, risks or audits.
Requirements
A remote endpoint at api.dastra.eu reached over streamable HTTP. OAuth authentication is required, so a Dastra account with the appropriate access is needed. No environment variables or headers are declared.
Before you install
The server handles sensitive compliance data such as data breaches and data subject requests, and OAuth grants access to that account. No tool list is published, so it is unclear which operations read or change records; confirm write behavior before use.

Installation

In SourceWeft

  1. Open Dastra 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.dastra%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": {
    "dastra": {
      "type": "http",
      "url": "https://api.dastra.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

72% 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

    Publish an icon in the registry entry.

  • Documentation15 pts
  • 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.