Official description7 sourcesMCP servers8d ago

juanisidoro/securecode-mcp

Encrypted secrets vault f

View on GitHub ↗Direct link · no redirect page

Config template (adjust for your client)

claude mcp add securecode-mcp -- npx -y securecode-mcp

A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.

Star count: 1 ★ · juanisidoro/securecode-mcp · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source: collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history: first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score: score 703 · 1 ★ · 7 sources · mcp

FAQ (answers come from our records)

How do I install it?

We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.

Who is it for?

We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

repository juanisidoro/securecode-mcp；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.

Third-party quality signals

@securecode/mcp-server

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

MCP Server for SecureCodeHQ. Lets Claude Code access your secrets securely without ever seeing them.
Quick Start
Then tell Claude Code:
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
| Tool | What it does |
|------|-------------|
| onboard | Guided setup: signup, import, API key, config, SDK |
| get-secret | Get a secret (injected to file by default, reveal: true to show to AI) |
| list-secrets | List all secrets with tags and expiry status |
| create-secret | Create a new secret |
| update-secret | Update value, description, or tags |
| delete-secret | Delete a secret |
| renew-secret | Renew expired secrets or change TTL |
| import-env | Import .env via secure web window (values never pass through AI) |
| export-env | Export secrets as .env or CSV |
| get-status | Check plan, usage, and MCP server version |
| wake-session | Unlock session with optional scope and auto-sleep timer |
| sleep-session | Lock session and clean injected files |
| session-status | Check session state and time remaining |
| byebye | Lock session + clean all secrets from disk |
| get-active-rules | List active MCP access rules (read-only) |
| security-check | Post-setup security hardening checks |
| help | Docs: 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.
| Action | Effect |
|--------|--------|
| Block Always | Secret only accessible from the dashboard |
| Require Confirmation | Agent must acknowledge before accessing |
| Require Session | Requires active session (wake-session) |
| Block Models | Only allows specific AI models |
| Notify | Sends email on access (non-blocking) |
Session Lock
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