
Holster MCP
com.nautaaiPublished by nautaai.comv0.1.1Updated Oct 24, 2026
Local-first secret scanning, rotation, vault, and audit-log tools for AI agents.
Overview
Local-first MCP server that lets an AI assistant scan repositories for secrets, check gitignore coverage, get rotation playbooks, and manage a local credential.
- What you can do
- Scan a repository path for exposed secrets and report file, line, secret kind and severity, with a depth limit on the scan. Check a repository's gitignore for missing or unsafe patterns and get a suggested append. Retrieve provider-specific credential rotation playbooks with steps, time estimates and warnings. Add secrets to a local vault and rotate vault entries for supported providers, with the old entry marked superseded. Query the local audit log of vault actions by provider, account and time window.
- When to use it
- Useful when you want an assistant to audit a codebase for leaked credentials before committing or publishing, tighten gitignore rules, or walk through rotating a compromised key while keeping secrets in a local vault rather than in chat or shell history.
- Requirements
- Runs as a local process on the user's machine, installed from PyPI (holster-mcp) and started with the holster-mcp command or via uvx. Needs a bundled or discoverable holster-doctor binary; platform wheels are provided for macOS ARM and Linux x86_64 only. Paid vault and audit tools require a Holster license and a local vault configured by argument, HOLSTER_VAULT_PATH or a config file.
Installation
In SourceWeft
- Open Holster MCP in the dashboard and add it to a workspace.
- 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
Holster MCP
Holster MCP exposes local Holster Doctor checks to MCP-compatible agents. The server is local-first: free tools shell out to the bundled holster-doctor binary and never send repository contents to a network service.
Install
From PyPI:
Development install:
Runtime command:
MCP client config:
See the main Holster README for vault and holster-cli release binary installation.
License: MIT for the MCP package.
Binary Resolution
The server locates holster-doctor in this order:
HOLSTER_DOCTOR_BIN- Packaged wheel binary at
holster_mcp/bin/holster-doctor holster-doctoronPATH- Repo-local
target/release/holster-doctor - Repo-local
target/debug/holster-doctor
Free Tools
holster.scan_repo
Input:
Output:
holster.check_gitignore
Input:
Output:
holster.rotation_playbook
Input:
Output:
Platform Wheels
Day 1 wheels are built for:
- macOS ARM (
aarch64-apple-darwin) - Linux x86_64 (
x86_64-unknown-linux-gnu)
The wheels bundle the platform's holster-doctor binary and are intentionally not universal.
Paid Tools
Paid tools are local-only wrappers around holster-cli and are gated by a Holster license.
License Configuration
License lookup order:
license_keyargument passed to a paid MCP toolHOLSTER_LICENSE_KEY~/.holster/config.toml
Supported config.toml shapes:
or:
License cache:
If no license is configured, the first paid-tool call creates a local 7-day trial key with prefix holster_trial_.
Vault Configuration
Vault path lookup order:
- explicit tool argument where supported
HOLSTER_VAULT_PATH~/.holster/config.toml
holster.vault_add
Input:
Output:
The secret value is never placed in CLI argv, logs, or structured error output.
holster.vault_rotate
Day 2 supports github and stripe.
Without new_secret, the tool returns the provider playbook and waits for the human to rotate/paste the replacement:
With new_secret, the replacement is added to the local vault and the old entry is marked superseded when the installed CLI supports that command.
holster.audit_log
Input:
Output:
License Architecture
The background poller refreshes cached live licenses every 10 minutes after a paid tool validates. There is no webhook receiver in Day 2 and no telemetry in V1.
Source: mcp/README.md at commit bd70dbf
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% 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