AppLock
Related Servers
Alternatives to AppLock
No user-submitted related servers found.
Related Servers
- 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.64 npm6Cryptographic Autonomy 1.0 (Combined Work Exception)
- AlicenseAqualityDmaintenanceSecrets vault for Claude Code. Encrypt API keys, tokens and passwords with AES-256. Full audit logs, MCP access rules, and zero-knowledge mode. Secrets never appear in chat.1733 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables macOS users to securely connect AI assistants such as Notion AI, Claude, and Cursor to their local files and terminal through an MCP server protected by a Bearer token and Cloudflare Tunnel.-
- AlicenseAqualityDmaintenanceLocal MCP server for macOS that scans AI coding tool history (Claude Code, Cursor, Copilot, Cline, Codex, Gemini CLI) for leaked secrets. Finds API keys in chat transcripts, redacts with sieve:// placeholders, and runs commands with Keychain-injected secrets - no plaintext values ever returned.91MIT
- AlicenseNot gradedqualityCmaintenanceGives ChatGPT Web hands on your Mac — files, git, terminal, browser, and windows via MCP, with outbound-only tunnel and delete protection.1MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to retain persistent, searchable memory and versioned vaults, spawn and recall named agents with state and audit history, run automations, monitors, and deep research, and execute on-chain and web tasks across sessions. It can be installed alongside Claude Code, Cursor, Windsurf, Zed, Hermes, and other MCP clients, with vault and memory optionally run entirely on the user's machine.45131 npmMIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct target and action: local sessions (hide_session, list_sessions), browser chats (hide_browser_chat, list_browser_chats), and vault contents (list_hidden, read_hidden, restore_hidden). The list/unlock/lock/status tools are also unambiguous, so an agent can easily select the right operation.
Names are consistently snake_case and mostly follow a verb_noun pattern (hide_session, list_browser_chats, unlock_vault). The only deviation is applock_status, which is noun_status rather than verb_noun, but it remains readable and predictable.
The 10 tools sit comfortably in the ideal 3–15 range for a focused privacy/locking utility. Each tool corresponds to a distinct operation, and there is no obvious redundancy or missing essential operation.
The set covers the full hide/list/read/restore/unlock/lock lifecycle for local sessions and browser chats, plus status reporting. Minor gaps exist: no permanent delete from vault, no search/filter for hidden items, and read_hidden appears limited to local sessions, but core workflows are covered.