SourceVault Gateway

ai.sourcevaultPublished by sourcevault.aiv1.67.0Updated Oct 26, 2026

Governed access to private code for coding agents: policy, redaction, audit chain, provenance.

The publisher's own server: Source

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP gateway that gives coding agents governed, policy-checked access to private code, with redaction, an audit chain and provenance.

What you can do
  • No tool list is published, so capabilities come from the description only.
  • Gives a coding agent governed access to private source code, subject to policy checks.
  • Applies redaction and records an audit chain for the access it mediates.
  • Tracks provenance of the code and results the agent works with.
  • Attributes calls to a named agent token so activity can be traced.
When to use it
Worth adding when a coding agent needs to read private repositories and you want policy enforcement, redaction and an auditable record of what it accessed, rather than giving the agent direct repository access.
Requirements
Runs as a local desktop process over stdio, installed from an mcpb package. A named agent token in SOURCEVAULT_AGENT_TOKEN, minted with the sourcevault agent mint command, is needed for attributed calls. SOURCEVAULT_STATE_DIR is only needed for a non-default install location.
Before you install
The server asks for an agent token secret (SOURCEVAULT_AGENT_TOKEN); treat it as a credential and keep it out of shared configuration. Without it, calls are unattributed, which weakens the audit trail. It mediates access to private code, so review the policy and redaction rules before relying on it.

Installation

In SourceWeft

  1. Open SourceVault Gateway 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 started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

2
  1. v1.67.0LatestOct 26, 2026
  2. v1.66.0Oct 25, 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 Source integrations