Back to Browse

Securecode MCP Server

Developer ToolsModerate6.8MCP RegistryLocal
Free

Server data from the Official MCP Registry

Secrets vault for Claude Code with audit logs, access rules, and AES-256 encryption.

About

Secrets vault for Claude Code with audit logs, access rules, and AES-256 encryption.

Security Report

6.8
Moderate6.8Moderate Risk

Valid MCP server (2 strong, 4 medium validity signals). 3 known CVEs in dependencies (0 critical, 2 high severity) ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry.

3 files analyzed · 4 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-juanisidoro-securecode": {
      "args": [
        "-y",
        "@securecode/mcp-server"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

@securecode/mcp-server

MCP Server for SecureCodeHQ. Lets Claude Code access your secrets securely without ever seeing them.

SecureCode MCP server

Quick Start

claude mcp add securecode -- npx -y @securecode/mcp-server

Then tell Claude Code:

Set up SecureCode in this project

The onboard tool walks you through account creation, secret import, and configuration. Takes about 2 minutes.

What It Does

Your secrets (API keys, tokens, passwords) are encrypted with AES-256 and stored in SecureCode. Claude Code accesses them via MCP, but the actual values never appear in the chat.

When Claude reads a secret, the value is written to a local file on your machine. The AI gets the file path but never sees the raw value. This is inject mode, the default.

Tools

ToolWhat it does
onboardGuided setup: signup, import, API key, config, SDK
get-secretGet a secret (injected to file by default, reveal: true to show to AI)
list-secretsList all secrets with tags and expiry status
create-secretCreate a new secret
update-secretUpdate value, description, or tags
delete-secretDelete a secret
renew-secretRenew expired secrets or change TTL
import-envImport .env via secure web window (values never pass through AI)
export-envExport secrets as .env or CSV
get-statusCheck plan, usage, and MCP server version
wake-sessionUnlock session with optional scope and auto-sleep timer
sleep-sessionLock session and clean injected files
session-statusCheck session state and time remaining
byebyeLock session + clean all secrets from disk
get-active-rulesList active MCP access rules (read-only)
security-checkPost-setup security hardening checks
helpDocs: tools, SDK, sessions, rules, troubleshooting

MCP Access Rules

Control how AI agents access your secrets with tag-based policies. Created from the dashboard, enforced server-side.

ActionEffect
Block AlwaysSecret only accessible from the dashboard
Require ConfirmationAgent must acknowledge before accessing
Require SessionRequires active session (wake-session)
Block ModelsOnly allows specific AI models
NotifySends email on access (non-blocking)

Session Lock

You: "Wake my session for acme staging"
Claude: Session unlocked. Only acme/staging secrets accessible.

You: "byebye"
Claude: Session locked & secrets cleaned from disk.

Sessions auto-sleep after configurable inactivity (default: 2 hours).

How It Works

  • Secret values are written to a local file, the AI never sees them (inject mode)
  • Explicit reveal: true returns value to AI (audited)
  • Injected files are removed on sleep, byebye, or process exit
  • Multiple Claude Code instances don't collide (hash based on API key + PID)
  • Encrypted with AES-256-GCM using envelope encryption (Cloud KMS)
  • Every access is logged with AI model, IP, machine identity, and timestamp
  • Runs locally via stdio transport, secrets never pass through third parties
  • Device approval required on first use from each machine

SDK

The companion SDK lets your app load secrets at runtime:

npm install @securecode/sdk
import { loadEnv } from '@securecode/sdk';
await loadEnv(); // all secrets loaded into process.env

SDK on npm

Links

Requirements

  • Node.js >= 18
  • A SecureCodeHQ account (free tier: 50 secrets, 10K accesses/month)

License

MIT

Reviews

No reviews yet

Be the first to review this server!