Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Holster MCP

by nauta-aiversion 0.1.1i★ –iRuns on your computer
Registry namecom.nautaai/holster-mcp

Install

Overview

Description from the maker (original English)

Local-first secret scanning, rotation, vault, and audit-log tools for AI agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "holster": {
      "command": "uvx",
      "args": [
        "holster-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add holster -- uvx holster-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "holster": {
      "command": "uvx",
      "args": [
        "holster-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "holster": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "holster-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain nautaai.com (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 18939 servers in this category
  • Published to the registry more recently than 8% of the other 18939 servers in this category
  • Basic checks equal to or better than 100% of the other 18939 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Holster MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Beefi

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated 4 days ago

Runs in the cloud✓ desktopcommander.app

Beefi

US public company data from SEC EDGAR: financials, insider trades, 13F holdings, filings and macro.

by capaxelabsEarlyUpdated today

Runs in the cloud✓ beefi.ai

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

pip install holster-mcp

Development install:

cd /path/to/holster/mcp

python3.11 -m pip install -e '.[dev]'

Runtime command:

holster-mcp

MCP client config:

{

"mcpServers": { "holster": { "command": "uvx", "args": ["holster-mcp"] } } }

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:

  1. HOLSTER_DOCTOR_BIN
  2. Packaged wheel binary at holster_mcp/bin/holster-doctor
  3. holster-doctor on PATH
  4. Repo-local target/release/holster-doctor
  5. Repo-local target/debug/holster-doctor

Free Tools

holster.scan_repo

Input:

{"path": "/absolute/repo/path", "depth": 3}

Output:

{

"ok": true, "scanned_files": 15, "findings": [ { "file": "src/main.py", "line": 12, "secret_kind": "openai_api_key", "severity": "error", "suggestion": "Rotate this key and move it into a local vault." } ] }

holster.check_gitignore

Input:

{"path": "/absolute/repo/path"}

Output:

{

"ok": true, "missing_patterns": [".env.local"], "existing_safe": [".env"], "existing_unsafe": [], "suggested_append": ".env.local\n*.pem" }

holster.rotation_playbook

Input:

{"provider": "github"}

Output:

{

"ok": true, "provider": "github", "steps": ["Create a replacement token...", "Update local consumers...", "Revoke the old token..."], "estimated_minutes": 15, "warnings": ["Do not revoke the old credential until the replacement has been verified."] }

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:

  1. license_key argument passed to a paid MCP tool
  2. HOLSTER_LICENSE_KEY
  3. ~/.holster/config.toml

Supported config.toml shapes:

license_key = "holster_live_ABCDEFGHIJKLMNOPQRSTUVWX"

vault_path = "/absolute/path/to/holster-vault.db"

or:

[license]

key = "holster_live_ABCDEFGHIJKLMNOPQRSTUVWX"

[vault] path = "/absolute/path/to/holster-vault.db"

License cache:

~/.holster/licenses.db

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:

  1. explicit tool argument where supported
  2. HOLSTER_VAULT_PATH
  3. ~/.holster/config.toml
holster.vault_add

Input:

{

"provider": "github", "account": "nauta-ai", "secret": "user-pasted-secret", "label": "primary" }

Output:

{"ok": true, "vault_entry_id": "123e4567-e89b-12d3-a456-426614174000", "error": null}

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:

{

"provider": "github", "account": "nauta-ai", "vault_entry_id": "old-id" }

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:

{"provider": "github", "account": "nauta-ai", "since_days": 30}

Output:

{"ok": true, "events": [{"ts": "...", "action": "add", "provider": "github", "account": "nauta-ai", "ok": true}]}

License Architecture

flowchart TD

A["Paid MCP tool call"] --> B["Resolve license key from arg/env/config"] B --> C{"Key present?"} C -- "No" --> D["Create local 7-day trial in ~/.holster/licenses.db"] C -- "Yes" --> E["Read ~/.holster/licenses.db"] D --> F{"Trial valid?"} E --> G{"Cached license valid?"} G -- "Valid" --> H["Dispatch paid tool"] G -- "Expired but within 7-day grace" --> I["Dispatch with license_warning"] G -- "Missing/stale live key" --> J["Stripe refresh: Customer.retrieve + Subscription.list"] J -- "Active" --> K["Update cache valid_until + last_checked"] J -- "Inactive/error/no API key" --> L["Return license_required_or_expired"] F -- "Valid" --> H F -- "Expired" --> L K --> H I --> H H --> M["Local holster-cli subprocess"]

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.

Ask PopNx