SanctumAI — Credential Vault for AI Agents

io.github.jwgalePublished by GitHub account jwgalev0.3.2Updated Oct 24, 2026

Credential vault for AI agents — encrypted storage, lease-based access, CRP support.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local credential vault MCP server that gives an AI assistant encrypted storage and lease-based access to secrets.

What you can do
SanctumAI is a credential vault exposed as a local MCP server. According to its registry description, it provides encrypted storage for credentials, lease-based access control, and CRP support. It runs as a local process on the user's machine over stdio, so the assistant can request credentials from the vault rather than holding them directly.
When to use it
Worth considering when an assistant needs to work with credentials or secrets and you want them kept in an encrypted local vault with time-limited, lease-based access instead of being pasted into prompts or config files. It is a desktop-only tool, so it suits individual workstations rather than shared or headless servers.
Requirements
Runs locally as an npm package (@sanctumai/mcp-server) over stdio, so Node.js is needed. The vault passphrase is supplied through the SANCTUM_PASSPHRASE environment variable for automated or headless operation; if it is not set, the vault must be unlocked interactively or through the web UI. The vault directory is set by SANCTUM_VAULT_PATH and defaults to ~/.sanctum. Desktop only.
Before you install
The server handles credentials, so the vault passphrase in SANCTUM_PASSPHRASE is itself a sensitive secret and should not be exposed in logs, shell history, or shared configuration. Access is granted through leases, so review what the assistant can retrieve and for how long. The manifest lists no tools, so the exact read and write behavior of the vault cannot be verified from the supplied material.

Installation

In SourceWeft

  1. Open SanctumAI — Credential Vault for AI Agents 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. v0.3.2LatestSep 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.