seekrit (local crypto plane)

dev.seekritPublished by seekrit.devv0.8.5Updated Oct 27, 2026

Zero-knowledge secrets manager — local crypto-plane MCP server: decrypts and injects secrets.

The publisher's own server: seekrit — secrets for agents

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Local stdio MCP server that acts as a zero-knowledge secrets manager's crypto plane, decrypting and injecting secrets for an assistant.

What you can do
  • Decrypt and inject secrets into the assistant's work through a local crypto plane, per the registry description.
  • Retrieve secrets with a get_secret tool, which needs the token's private-key passphrase when authenticating with a token.
  • Run commands with a run_command tool, which likewise requires the passphrase for decryption under token authentication.
  • Authenticate either with machine (M2M) client credentials or with an existing service or admin token.
  • Point the server at the hosted seekrit API or at an overridden API base URL.
When to use it
Worth adding when an assistant needs to work with stored secrets locally, decrypting them on the user's machine and injecting them into tasks such as running commands, rather than pasting credentials into prompts.
Requirements
Runs as a local process over stdio, installed from the npm package @seekrit/mcp (Node.js). Desktop only; no web execution. Needs either SEEKRIT_CLIENT_ID plus SEEKRIT_CLIENT_SECRET, or an existing SEEKRIT_TOKEN; SEEKRIT_PASSPHRASE is required for decrypting tools when using a token. SEEKRIT_API_URL optionally overrides the default hosted API. Network access to the seekrit API.
Before you install
The server handles live credentials: SEEKRIT_CLIENT_SECRET, SEEKRIT_TOKEN and SEEKRIT_PASSPHRASE are secrets, and the passphrase unlocks the token's private key. Tools such as get_secret and run_command decrypt secrets and can execute commands, so an assistant could expose or misuse credentials; scope the token and review command execution. Secret material and API requests go to the seekrit service at the configured API URL.

Installation

In SourceWeft

  1. Open seekrit (local crypto plane) 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

2
  1. v0.8.5LatestSep 20, 2026
  2. v0.8.1Sep 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.

Other Seekrit integrations