Legacy Shield

io.github.stephenballot-aiPublished by GitHub account stephenballot-aiv1.0.3Updated Oct 24, 2026

Zero-knowledge encrypted vault for AI agents. EU-hosted persistent storage.

VerifiedSTDIODesktop onlyFiles & StorageSecurity & Monitoring

Overview

AI-generated overview

Lets an AI assistant list files and read file metadata in a zero-knowledge encrypted vault hosted in the EU.

What you can do
This MCP server connects an assistant to a LegacyShield zero-knowledge encrypted vault over stdio. It exposes tools to list what is stored in the vault (list_vault_files) and to retrieve encryption headers and file information (get_file_metadata). It is a read-and-inspect bridge between the assistant's reasoning and the user's encrypted persistence.
When to use it
Worth adding when an assistant needs to see which files exist in a LegacyShield vault or inspect their metadata and encryption headers. It is not for reading file contents, since only listing and metadata tools are described.
Requirements
Runs as a local process on the user's machine via the npm package @legacy-shield/mcp-server over stdio, so Node.js is needed. Requires the environment variables LEGACY_SHIELD_API_URL and LEGACY_SHIELD_API_KEY; the API key starts with ls_ and is obtained by registering an agent with the provider. Network access to the LegacyShield API is required. Desktop only.
Before you install
The server requires the secret LEGACY_SHIELD_API_KEY, which grants access to the vault; store it securely and avoid exposing it in logs or shared configuration. Vault contents and metadata are sent to the provider's EU-hosted API, so the assistant's queries leave the local machine. No write, delete, or payment tools are described.

Installation

In SourceWeft

  1. Open Legacy Shield 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

LegacyShield MCP Server 🦞

This is a Model Context Protocol (MCP) server that allows AI agents (like Claude) to interact directly with the LegacyShield Zero-Knowledge Vault.

Features

  • list_vault_files: Let agents see what's in the vault.
  • get_file_metadata: Retrieve encryption headers and file info.

Usage for Agents

Agents use this server via stdio to bridge the gap between their reasoning and your encrypted persistence.

Configuration

Requires:

  • `LEGACY_SHIELD_API_URL`
  • `LEGACY_SHIELD_API_KEY` (generated via `POST /agents/register`)

Source: packages/mcp-server/README.md at commit b26233b

Tools

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

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

40% 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
  • License10 pts

    Declare a license in the repository or the registry entry.