Veridion Nexus

io.github.Brano80Published by GitHub account Brano80v1.0.9Updated Oct 24, 2026

Veridion Nexus MCP server - GDPR Art. 44-49 runtime compliance for AI agents

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Local MCP server that adds runtime GDPR Art. 44-49 cross-border data transfer compliance checks for AI agents.

What you can do
  • The listing gives no tool list, so capabilities are inferred from the description only.
  • It is described as providing runtime compliance for AI agents under GDPR Articles 44-49, the rules on transfers of personal data outside the EU/EEA.
  • It runs as a local stdio process that an assistant connects to, and authenticates to the Veridion Nexus service with an API key.
  • No further detail on specific checks, outputs or workflows is published.
When to use it
Consider it when an assistant handles personal data and you want transfer-compliance checks applied while it works, rather than only in a later audit. It is a narrow, single-purpose server, so it is only worth adding if GDPR cross-border transfer rules are relevant to your use case.
Requirements
Runs as a local process over stdio, installed from the npm package veridion-nexus-mcp, so a Node.js runtime is needed. Requires an API key supplied in the environment variable VERIDION_NEXUS_API_KEY. Desktop only; no web executable. Network access to the Veridion Nexus service is implied by the API key.
Before you install
The server requires a secret API key (VERIDION_NEXUS_API_KEY); keep it out of shared configuration and logs. Data the assistant processes may be sent to the Veridion Nexus service for checking, so confirm what leaves your machine. No tool list, README or instructions are published, so the exact behaviour and any write actions cannot be verified before installing.

Installation

In SourceWeft

  1. Open Veridion Nexus in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.9LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.