Prophetkey Mcp

io.github.LBZ558Published by GitHub account LBZ558v1.2.1Updated Oct 25, 2026

ProphetKey MCP bridge - encrypted local-first API key vault for AI agents, keys never exposed

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local bridge to ProphetKey, an encrypted local-first API key vault, letting an assistant use stored keys without exposing them.

What you can do
Connects an assistant to a locally running ProphetKey vault over a local proxy port, so stored API keys can be used by agents without being revealed to them. The bridge is described as encrypted and local-first, with keys never exposed. The manifest lists no individual tools, so the exact operations available are not documented in the supplied material.
When to use it
Useful when you keep API keys in ProphetKey and want an AI assistant to work with those keys while keeping the raw values out of the conversation and model context.
Requirements
Runs as a local process on the user's machine via the npm package prophetkey-mcp over stdio, so Node.js is needed. Requires a ProphetKey bearer token supplied through the PROPHETKEY_MCP_TOKEN environment variable, obtained from ProphetKey Settings under MCP Server. A local proxy port can be set with PROPHETKEY_MCP_PORT, defaulting to 1421. Desktop only.
Before you install
The server needs a bearer token in PROPHETKEY_MCP_TOKEN; treat it as a secret and keep it out of shared configuration. It acts as a bridge to a vault holding API keys, so review what the assistant can do with those keys before connecting. No tools are listed, so verify the actual capabilities before relying on it.

Installation

In SourceWeft

  1. Open Prophetkey Mcp 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.

Tools

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

Version history

1
  1. v1.2.1LatestSep 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.