English Français العربية

io.github.juanisidoro/securecode

Registre officiel Outils de développement

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

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @securecode/mcp-server
Claude Code 
claude mcp add securecode -- npx -y @securecode/mcp-server@0.15.2
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "securecode": {
            "command": "npx",
            "args": [
                "-y",
                "@securecode/mcp-server@0.15.2"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. @securecode/mcp-server
  2. Quick Start
  3. What It Does
  4. Tools
  5. MCP Access Rules
  6. Session Lock
  7. How It Works
  8. SDK
  9. Links
  10. Requirements
  11. License

@securecode/mcp-server

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

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

Requirements

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

License

MIT

Questions fréquentes

Qu'est-ce que io.github.juanisidoro/securecode ?

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

Comment installer io.github.juanisidoro/securecode ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add securecode -- npx -y @securecode/mcp-server@0.15.2. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.juanisidoro/securecode ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.juanisidoro/securecode est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.juanisidoro/securecode ?

Il est publié par juanisidoro. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.