ncrypted-mcp
Related Servers
Alternatives to ncrypted-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceShare encrypted, self-destructing secrets from your AI agent. Zero-knowledge E2E encryption. Agent-blind input sources (env:, file:, dotenv:) keep secrets out of LLM context.413 npm1MIT
- AlicenseAqualityDmaintenanceCreate and read burn-after-read encrypted notes. AES-256-GCM E2E encryption with self-destructing URLs for secure credential handoff between users and AI agents.258 npm1MIT
- AlicenseAqualityFmaintenanceHand a secret to another agent as an encrypted, pay-per-read token delivered exactly once, leaving no copy behind. Also pre-flights an x402 endpoint before your agent pays it. Runs locally over stdio and encrypts in your own process, so there is no hosted version to hand your plaintext to.3137 npmISC
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to create end-to-end encrypted, self-destructing notes that can be securely shared via a one-click link, ensuring secrets are never stored in plain text in chat history.1-
- AlicenseNot gradedqualityBmaintenanceSelf-hosted, zero-knowledge encrypted, self-destructing secrets for secure agent-to-agent coordination3AGPL 3.0
- AlicenseAqualityBmaintenanceLets an AI agent request API keys and passwords from a human through an end-to-end encrypted one-time link and pass them to exactly one command or file, without the value ever entering the agent's context. Can also send secrets as self-destructing links.3AGPL 3.0
TDQS
Scored across 10 tools
Each tool has a very clear and distinct purpose, even when functions overlap (e.g., reading a secret vs. storing it in an environment variable). The descriptions clearly delineate the use case for every function.
The naming convention is extremely consistent, following a clear snake_case pattern preceded by the 'ncrypted_' namespace. This predictability allows for immediate identification of tool function.
With 10 tools, the set is perfectly scoped for its complex purpose of managing encrypted secrets. It avoids both bloat and critical functional gaps.
The tool surface provides comprehensive coverage of the secret lifecycle, including creation, reading, consumption (local/remote storage), status tracking, and billing setup. There are no obvious functional dead ends.