How are secrets provided to commands?

secretctl injects selected secrets as environment variables when running a command.

Can an AI agent see the injected secret values?

The MCP workflow is designed to return command results without exposing plaintext secrets, and command output is automatically sanitized.

What encryption does secretctl use?

It uses AES-256-GCM for encryption and Argon2id for key derivation.

Secretctl

secrets-managementsecuritymcpdeveloper-tools

Local secrets manager that injects encrypted credentials into commands while sanitizing output returned to AI agents.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.

Manual Client & Custom JSON ConfigExpand JSON ▾

No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for forest6511/secretctl, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.

Overview

secretctl stores secrets locally and injects them into command environments without exposing plaintext values to the AI agent. Its MCP integration lets agents run commands and receive sanitized results. Use it when coding agents need access to credentials such as API keys or cloud credentials without placing them in chat history.

Use cases

Store API keys in an encrypted local vault

Inject credentials into AWS or other CLI commands

Run deployment scripts without exposing secrets in shell history

Sanitize command output that contains secret values

Track secret metadata, expiration dates, and tags

Key features

AES-256-GCM encryption at rest

Argon2id key derivation

SQLite-based local storage

MCP integration for AI-safe command execution

Automatic output sanitization

Metadata, expiration, tags, and audit logging

Capabilities & Tool Schemas

Inspect callable tools, capabilities, and parameters exposed to AI agents by Secretctl.

Extracted Tool Capabilities

AES-256-GCM encryption at rest

Argon2id key derivation

SQLite-based local storage

MCP integration for AI-safe command execution

Automatic output sanitization

Metadata, expiration, tags, and audit logging

Documentation Overview

secretctl

Stop pasting API keys into AI chat.

When you paste sk-proj-xxx into Claude Code, that secret is now in your conversation history, Anthropic's logs, and potentially exposed to prompt injection attacks.

secretctl fixes this. Your AI gets command results, never secret values.

secretctl demo

The Problem

Every day, developers paste secrets into AI coding assistants:

Code

You: "Help me debug this AWS error"
You: "Here's my config: AWS_ACCESS_KEY_ID=AKIA..."

This is a security incident waiting to happen.

Secrets in conversation history
Secrets in cloud logs
Secrets exposed to prompt injection
No way to rotate or revoke

The Solution

secretctl injects secrets as environment variables. Your AI runs commands and sees results, but never sees the actual credentials.

Single binary — No servers, no configuration, no subscription
Local-first — Secrets never leave your machine
MCP integration — Works with Claude Code out of the box
Defense in depth — AES-256-GCM + Argon2id + output sanitization

Code

# That's it. You're done.
secretctl init
secretctl set API_KEY
secretctl get API_KEY

Why Local-First & AI-Safe?

Your secrets, your machine — No cloud sync, no third-party servers, no subscription fees. Your credentials stay on your device, period.
AI agents don't need plaintext — When Claude runs aws s3 ls, it needs the result, not your AWS keys. secretctl injects credentials directly into commands—AI never sees them.
Defense in depth — AES-256-GCM encryption at rest, Argon2id key derivation, MCP policy controls, and automatic output sanitization. Multiple layers, not a single point of failure.

mermaid

flowchart LR
    subgraph Flow["How It Works"]
        AI["🤖 AI Agent<br/>(Claude)"]
        MCP["🔐 secretctl<br/>MCP Server"]
        CMD["⚡ Command<br/>(aws, etc)"]

        AI -->|"1. Run aws s3 ls<br/>with aws/*"| MCP
        MCP -->|"2. Inject secrets<br/>as env vars"| CMD
        CMD -->|"3. Execute"| MCP
        MCP -->|"4. Sanitized output<br/>[REDACTED]"| AI
    end

    AI ~~~ NOTE["✓ Gets command results<br/>✗ Never sees secret values"]

Installation

From Source

bash

# Requires Go 1.24+
git clone https://github.com/forest6511/secretctl.git
cd secretctl
go build -o secretctl ./cmd/secretctl

Binary Releases

Download the latest release from GitHub Releases.

CLI:

secretctl-linux-amd64 — Linux (x86_64)
secretctl-linux-arm64 — Linux (ARM64)
secretctl-darwin-amd64 — macOS (Intel)
secretctl-darwin-arm64 — macOS (Apple Silicon)
secretctl-windows-amd64.exe — Windows (x86_64)

Desktop App:

secretctl-desktop-macos — macOS (Universal)
secretctl-desktop-linux — Linux (AppImage)
secretctl-desktop-windows.exe — Windows (Installer)

Verify Downloads

bash

# Download checksums.txt and verify
sha256sum -c checksums.txt

macOS: Gatekeeper Warning

macOS may show a security warning for unsigned apps. To allow:

bash

# Option 1: Remove quarantine attribute
xattr -d com.apple.quarantine secretctl-darwin-arm64

# Option 2: Right-click the app and select "Open"

Windows: SmartScreen Warning

Windows SmartScreen may show a warning. To allow:

Click "More info"
Click "Run anyway"

Quick Start

1. Initialize your vault

bash

secretctl init
# Enter your master password (min 8 characters)

2. Store a secret

bash

echo "sk-your-api-key" | secretctl set OPENAI_API_KEY

3. Retrieve a secret

bash

secretctl get OPENAI_API_KEY

4. List all secrets

bash

secretctl list

5. Delete a secret

bash

secretctl delete OPENAI_API_KEY

Features

Core

AES-256-GCM encryption — Industry-standard authenticated encryption
Argon2id key derivation — Memory-hard protection against brute force
SQLite storage — Reliable, portable, no external dependencies
Audit logging — HMAC-chained logs for tamper detection
AI-safe by design — MCP integration never exposes plaintext secrets to AI agents

Metadata Support

bash

# Add notes and tags to secrets
secretctl set DB_PASSWORD --notes="Production database" --tags="prod,db"

# Add URL reference
secretctl set API_KEY --url="https://console.example.com/api-keys"

# Set expiration
secretctl set TEMP_TOKEN --expires="30d"

# Filter by tag
secretctl list --tag=prod

# Show expiring secrets
secretctl list --expiring=7d

# View full metadata
secretctl get API_KEY --show-metadata

Run Commands with Secrets

Inject secrets as environment variables without exposing them in your shell history:

bash

# Run a command with a single secret
secretctl run -k API_KEY -- curl -H "Authorization: Bearer $API_KEY" https://api.example.com

# Use wildcards to inject multiple secrets
# Pattern aws/* matches aws/access_key, aws/secret_key (single level)
secretctl run -k "aws/*" -- aws s3 ls

# Output is automatically sanitized to prevent secret leakage
secretctl run -k DB_PASSWORD -- ./deploy.sh
# If deploy.sh prints DB_PASSWORD, it appears as [REDACTED:DB_PASSWORD]

# With timeout and prefix
secretctl run -k API_KEY --timeout=30s --env-prefix=APP_ -- ./app

Note: Output sanitization uses exact string matching. Encoded secrets (Base64, hex) or partial matches are not detected.

Export Secrets

Export secrets for use with Docker, CI/CD, or other tools:

server.ts

# Export as .env file (default)
secretctl export -o .env

# Export specific keys as JSON
secretctl export --format=json -k "db/*" -o config.json

# Export to stdout for piping
secretctl export --format=json | jq '.DB_HOST'

Import Secrets

Import secrets from existing .env or JSON files:

server.ts

# Import from .env file
secretctl import .env

# Import from JSON file
secretctl import config.json

# Preview what would be imported (dry run)
secretctl import .env --dry-run

# Handle conflicts: skip, overwrite, or error
secretctl import .env --on-conflict=skip
secretctl import .env --on-conflict=overwrite

Generate Passwords

Create secure random passwords:

bash

# Generate a 24-character password (default)
secretctl generate

# Generate a 32-character password without symbols
secretctl generate -l 32 --no-symbols

# Generate multiple passwords
secretctl generate -n 5

Backup and Restore

Create encrypted backups and restore your vault:

bash

# Create encrypted backup
secretctl backup -o vault-backup.enc

# Create backup with audit logs
secretctl backup -o full-backup.enc --with-audit

# Verify backup integrity
secretctl restore vault-backup.enc --verify-only

# Restore to a new vault (dry run first)
secretctl restore vault-backup.enc --dry-run

# Restore with conflict handling
secretctl restore vault-backup.enc --on-conflict=skip    # Skip existing keys
secretctl restore vault-backup.enc --on-conflict=overwrite  # Overwrite existing

# Use key file instead of password (for automation)
secretctl backup -o backup.enc --key-file=backup.key
secretctl restore backup.enc --key-file=backup.key

Security: Backups are encrypted with AES-256-GCM using a fresh salt. The HMAC-SHA256 integrity check detects any tampering.

Audit Log

server.ts

# View recent audit events
secretctl audit list --limit=50

# Verify log integrity
secretctl audit verify

# Export audit logs
secretctl audit export --format=csv -o audit.csv

# Prune old logs (preview first)
secretctl audit prune --older-than=12m --dry-run

AI-Safe Access

secretctl implements AI-Safe Access — a security principle where AI agents never receive plaintext secrets.

Unlike traditional secret managers that might expose credentials directly to AI, secretctl uses a fundamentally different approach:

mermaid

flowchart LR
    subgraph "Traditional Approach ❌"
        AI1[AI Agent] -->|"get secret"| SM1[Secret Manager]
        SM1 -->|"plaintext: sk-xxx..."| AI1
    end

    subgraph "AI-Safe Access ✅"
        AI2[AI Agent] -->|"run command"| SM2[secretctl]
        SM2 -->|"inject env vars"| CMD[Command]
        CMD -->|"sanitized output"| SM2
        SM2 -->|"[REDACTED]"| AI2
    end

This follows the "Access Without Exposure" philosophy used by industry leaders like 1Password and HashiCorp Vault.

AI Integration (MCP Server)

secretctl includes an MCP server for secure integration with AI coding assistants like Claude Code:

bash

# Start MCP server (requires SECRETCTL_PASSWORD)
SECRETCTL_PASSWORD=your-password secretctl mcp-server

Available MCP Tools:

secret_list — List secret keys with metadata (no values exposed)
secret_exists — Check if a secret exists with metadata
secret_get_masked — Get masked value (e.g., ****WXYZ)
secret_run — Execute commands with secrets as environment variables
secret_list_fields — List field names for multi-field secrets (no values)
secret_get_field — Get non-sensitive field values only
secret_run_with_bindings — Execute with predefined environment bindings

Read the full README →View source on GitHub →

Related MCP Servers

View all in Security View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

7mo ago

Most recent push to the default branch.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Secretctl

No. The README describes it as local-first, with no cloud sync or third-party server.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/forest6511-secretctl?style=directory)](https://allmcps.com/mcp/forest6511-secretctl)

HTML Embed

<a href="https://allmcps.com/mcp/forest6511-secretctl"><img src="https://allmcps.com/api/badge/forest6511-secretctl?style=directory" alt="Secretctl on AllMCPs" /></a>

Technical Specs & Signals

CategorySecurity

PricingFree

10/10 checks healthy over the last 33d

43Quality signal: Fair · 43/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools20/30

Adoption & activity2/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🔒 Security →Best MCP servers for Security →Alternatives to Secretctl →Install in Claude Desktop Install in Cursor Install in VS Code

Secretctl

secrets-managementsecuritymcpdeveloper-tools

Local secrets manager that injects encrypted credentials into commands while sanitizing output returned to AI agents.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Manual Client & Custom JSON ConfigExpand JSON ▾

Overview

Use cases

Store API keys in an encrypted local vault

Inject credentials into AWS or other CLI commands

Run deployment scripts without exposing secrets in shell history

Sanitize command output that contains secret values

Track secret metadata, expiration dates, and tags

Key features

AES-256-GCM encryption at rest

Argon2id key derivation

SQLite-based local storage

MCP integration for AI-safe command execution

Automatic output sanitization

Metadata, expiration, tags, and audit logging

Capabilities & Tool Schemas

Inspect callable tools, capabilities, and parameters exposed to AI agents by Secretctl.

Extracted Tool Capabilities

AES-256-GCM encryption at rest

Argon2id key derivation

SQLite-based local storage

MCP integration for AI-safe command execution

Automatic output sanitization

Metadata, expiration, tags, and audit logging

Documentation Overview

secretctl

Stop pasting API keys into AI chat.

When you paste sk-proj-xxx into Claude Code, that secret is now in your conversation history, Anthropic's logs, and potentially exposed to prompt injection attacks.

secretctl fixes this. Your AI gets command results, never secret values.

secretctl demo

The Problem

Every day, developers paste secrets into AI coding assistants:

Code

You: "Help me debug this AWS error"
You: "Here's my config: AWS_ACCESS_KEY_ID=AKIA..."

This is a security incident waiting to happen.

Secrets in conversation history
Secrets in cloud logs
Secrets exposed to prompt injection
No way to rotate or revoke

The Solution

secretctl injects secrets as environment variables. Your AI runs commands and sees results, but never sees the actual credentials.

Single binary — No servers, no configuration, no subscription
Local-first — Secrets never leave your machine
MCP integration — Works with Claude Code out of the box
Defense in depth — AES-256-GCM + Argon2id + output sanitization

Code

# That's it. You're done.
secretctl init
secretctl set API_KEY
secretctl get API_KEY

Why Local-First & AI-Safe?

Your secrets, your machine — No cloud sync, no third-party servers, no subscription fees. Your credentials stay on your device, period.
AI agents don't need plaintext — When Claude runs aws s3 ls, it needs the result, not your AWS keys. secretctl injects credentials directly into commands—AI never sees them.
Defense in depth — AES-256-GCM encryption at rest, Argon2id key derivation, MCP policy controls, and automatic output sanitization. Multiple layers, not a single point of failure.

mermaid

flowchart LR
    subgraph Flow["How It Works"]
        AI["🤖 AI Agent<br/>(Claude)"]
        MCP["🔐 secretctl<br/>MCP Server"]
        CMD["⚡ Command<br/>(aws, etc)"]

        AI -->|"1. Run aws s3 ls<br/>with aws/*"| MCP
        MCP -->|"2. Inject secrets<br/>as env vars"| CMD
        CMD -->|"3. Execute"| MCP
        MCP -->|"4. Sanitized output<br/>[REDACTED]"| AI
    end

    AI ~~~ NOTE["✓ Gets command results<br/>✗ Never sees secret values"]

Installation

From Source

bash

# Requires Go 1.24+
git clone https://github.com/forest6511/secretctl.git
cd secretctl
go build -o secretctl ./cmd/secretctl

Binary Releases

Download the latest release from GitHub Releases.

CLI:

secretctl-linux-amd64 — Linux (x86_64)
secretctl-linux-arm64 — Linux (ARM64)
secretctl-darwin-amd64 — macOS (Intel)
secretctl-darwin-arm64 — macOS (Apple Silicon)
secretctl-windows-amd64.exe — Windows (x86_64)

Desktop App:

secretctl-desktop-macos — macOS (Universal)
secretctl-desktop-linux — Linux (AppImage)
secretctl-desktop-windows.exe — Windows (Installer)

Verify Downloads

bash

# Download checksums.txt and verify
sha256sum -c checksums.txt

macOS: Gatekeeper Warning

macOS may show a security warning for unsigned apps. To allow:

bash

# Option 1: Remove quarantine attribute
xattr -d com.apple.quarantine secretctl-darwin-arm64

# Option 2: Right-click the app and select "Open"

Windows: SmartScreen Warning

Windows SmartScreen may show a warning. To allow:

Click "More info"
Click "Run anyway"

Quick Start

1. Initialize your vault

bash

secretctl init
# Enter your master password (min 8 characters)

2. Store a secret

bash

echo "sk-your-api-key" | secretctl set OPENAI_API_KEY

3. Retrieve a secret

bash

secretctl get OPENAI_API_KEY

4. List all secrets

bash

secretctl list

5. Delete a secret

bash

secretctl delete OPENAI_API_KEY

Features

Core

AES-256-GCM encryption — Industry-standard authenticated encryption
Argon2id key derivation — Memory-hard protection against brute force
SQLite storage — Reliable, portable, no external dependencies
Audit logging — HMAC-chained logs for tamper detection
AI-safe by design — MCP integration never exposes plaintext secrets to AI agents

Metadata Support

bash

# Add notes and tags to secrets
secretctl set DB_PASSWORD --notes="Production database" --tags="prod,db"

# Add URL reference
secretctl set API_KEY --url="https://console.example.com/api-keys"

# Set expiration
secretctl set TEMP_TOKEN --expires="30d"

# Filter by tag
secretctl list --tag=prod

# Show expiring secrets
secretctl list --expiring=7d

# View full metadata
secretctl get API_KEY --show-metadata

Run Commands with Secrets

Inject secrets as environment variables without exposing them in your shell history:

bash

# Run a command with a single secret
secretctl run -k API_KEY -- curl -H "Authorization: Bearer $API_KEY" https://api.example.com

# Use wildcards to inject multiple secrets
# Pattern aws/* matches aws/access_key, aws/secret_key (single level)
secretctl run -k "aws/*" -- aws s3 ls

# Output is automatically sanitized to prevent secret leakage
secretctl run -k DB_PASSWORD -- ./deploy.sh
# If deploy.sh prints DB_PASSWORD, it appears as [REDACTED:DB_PASSWORD]

# With timeout and prefix
secretctl run -k API_KEY --timeout=30s --env-prefix=APP_ -- ./app

Note: Output sanitization uses exact string matching. Encoded secrets (Base64, hex) or partial matches are not detected.

Export Secrets

Export secrets for use with Docker, CI/CD, or other tools:

server.ts

# Export as .env file (default)
secretctl export -o .env

# Export specific keys as JSON
secretctl export --format=json -k "db/*" -o config.json

# Export to stdout for piping
secretctl export --format=json | jq '.DB_HOST'

Import Secrets

Import secrets from existing .env or JSON files:

server.ts

# Import from .env file
secretctl import .env

# Import from JSON file
secretctl import config.json

# Preview what would be imported (dry run)
secretctl import .env --dry-run

# Handle conflicts: skip, overwrite, or error
secretctl import .env --on-conflict=skip
secretctl import .env --on-conflict=overwrite

Generate Passwords

Create secure random passwords:

bash

# Generate a 24-character password (default)
secretctl generate

# Generate a 32-character password without symbols
secretctl generate -l 32 --no-symbols

# Generate multiple passwords
secretctl generate -n 5

Backup and Restore

Create encrypted backups and restore your vault:

bash

# Create encrypted backup
secretctl backup -o vault-backup.enc

# Create backup with audit logs
secretctl backup -o full-backup.enc --with-audit

# Verify backup integrity
secretctl restore vault-backup.enc --verify-only

# Restore to a new vault (dry run first)
secretctl restore vault-backup.enc --dry-run

# Restore with conflict handling
secretctl restore vault-backup.enc --on-conflict=skip    # Skip existing keys
secretctl restore vault-backup.enc --on-conflict=overwrite  # Overwrite existing

# Use key file instead of password (for automation)
secretctl backup -o backup.enc --key-file=backup.key
secretctl restore backup.enc --key-file=backup.key

Security: Backups are encrypted with AES-256-GCM using a fresh salt. The HMAC-SHA256 integrity check detects any tampering.

Audit Log

server.ts

# View recent audit events
secretctl audit list --limit=50

# Verify log integrity
secretctl audit verify

# Export audit logs
secretctl audit export --format=csv -o audit.csv

# Prune old logs (preview first)
secretctl audit prune --older-than=12m --dry-run

AI-Safe Access

secretctl implements AI-Safe Access — a security principle where AI agents never receive plaintext secrets.

Unlike traditional secret managers that might expose credentials directly to AI, secretctl uses a fundamentally different approach:

mermaid

flowchart LR
    subgraph "Traditional Approach ❌"
        AI1[AI Agent] -->|"get secret"| SM1[Secret Manager]
        SM1 -->|"plaintext: sk-xxx..."| AI1
    end

    subgraph "AI-Safe Access ✅"
        AI2[AI Agent] -->|"run command"| SM2[secretctl]
        SM2 -->|"inject env vars"| CMD[Command]
        CMD -->|"sanitized output"| SM2
        SM2 -->|"[REDACTED]"| AI2
    end

This follows the "Access Without Exposure" philosophy used by industry leaders like 1Password and HashiCorp Vault.

AI Integration (MCP Server)

secretctl includes an MCP server for secure integration with AI coding assistants like Claude Code:

bash

# Start MCP server (requires SECRETCTL_PASSWORD)
SECRETCTL_PASSWORD=your-password secretctl mcp-server

Available MCP Tools:

secret_list — List secret keys with metadata (no values exposed)
secret_exists — Check if a secret exists with metadata
secret_get_masked — Get masked value (e.g., ****WXYZ)
secret_run — Execute commands with secrets as environment variables
secret_list_fields — List field names for multi-field secrets (no values)
secret_get_field — Get non-sensitive field values only
secret_run_with_bindings — Execute with predefined environment bindings

Read the full README →View source on GitHub →

Related MCP Servers

View all in Security View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

7mo ago

Most recent push to the default branch.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Secretctl

No. The README describes it as local-first, with no cloud sync or third-party server.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/forest6511-secretctl?style=directory)](https://allmcps.com/mcp/forest6511-secretctl)

HTML Embed

<a href="https://allmcps.com/mcp/forest6511-secretctl"><img src="https://allmcps.com/api/badge/forest6511-secretctl?style=directory" alt="Secretctl on AllMCPs" /></a>

Technical Specs & Signals

CategorySecurity

PricingFree

10/10 checks healthy over the last 33d

43Quality signal: Fair · 43/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools20/30

Adoption & activity2/15

Community engagement0/10

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🔒 Security →Best MCP servers for Security →Alternatives to Secretctl →Install in Claude Desktop Install in Cursor Install in VS Code