SecureCode
Related Servers
Alternatives to SecureCode
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to use locally encrypted, multi-tenant credentials by running commands with injected secrets, writing .env files, materializing files, and making HTTP requests, while scrubbing values from all output so they never enter the chat. Also supports sealed retrieval and saving through native dialogs or an auto-clearing clipboard, role-based credential selection, versioning, rollback, archiving, and a full audit log.16 npmMIT
- AlicenseAqualityDmaintenanceEncrypted token store for Claude Code sessions, providing MCP tools for secure secret management with macOS Keychain integration, per-project allowlists, and native dialog input.611 npm6Cryptographic Autonomy 1.0 (Combined Work Exception)
- AlicenseNot gradedqualityBmaintenanceEncrypted secrets management MCP server for AI agents, enabling secure storage, retrieval, rotation, and auditing of API keys and credentials with AES-128 encryption.MIT
- AlicenseAqualityDmaintenanceEncrypted secrets vault that blinds AI agents to API keys. Stores secrets in AES-256-GCM encrypted SQLite vault, resolves them at runtime via MCP values never appear in LLM conversation transcripts. Sandbox .env files with deterministic fakes.754 npm3MIT
- AlicenseAqualityBmaintenanceLocal AES-256-GCM encrypted vault for AI agents. Resolve {{PLACEHOLDER}} secrets in prompts at runtime — LLMs never see real API keys. Argon2id key derivation, zero cloud.262 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to securely manage API keys and secrets via the MCP protocol, with encrypted storage at rest and a simple CLI and Python SDK.1MIT
TDQS
Scored across 17 tools
Most tools have distinct purposes, but some potential confusion exists between 'byebye' and 'sleep-session' (both end sessions) and 'get-secret' and 'list-secrets' (both retrieve secret info). Descriptions help clarify differences, but overlap in session management and secret retrieval could cause misselection.
Tools follow a consistent verb-noun pattern (e.g., create-secret, delete-secret, update-secret) with clear, descriptive names. Minor deviations include 'byebye' (informal) and 'onboard' (single word), but overall naming is predictable and readable.
17 tools is slightly high but reasonable for a secrets management domain, covering operations like CRUD for secrets, session control, onboarding, and security checks. It feels comprehensive without being overly bloated, though some tools like 'help' and 'get-status' might be borderline essential.
The toolset provides complete coverage for secrets management: full CRUD (create, get, list, update, delete, renew), session lifecycle (sleep, wake, status), onboarding, import/export, security analysis, and documentation. No obvious gaps exist for the stated purpose, enabling agents to handle end-to-end workflows.