passkey-mcp
Related Servers
Alternatives to passkey-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI agents to securely store and manage encrypted secrets locally while using them indirectly through environment-variable injection or file writes, so plaintext values never enter the agent's context.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to fetch API keys and tokens on demand from an encrypted local vault instead of pasting them into chats, and to scan project folders for plaintext secrets. It also manages credential entries with templates, rotation tracking, usage logs, backups, and .env export.MIT
- AlicenseAqualityFmaintenanceA GitHub-native secrets manager that allows AI assistants to securely manage, generate, and validate credentials without exposing sensitive values in conversation history. It supports secret scanning, environment diffing, and secure command execution by injecting masked variables directly into the runtime environment.81 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to securely inject API keys and secrets into environment files, configs, or commands without the agent ever seeing the secret values.3 npmMIT
- 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.3 npmMIT
- 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 5 tools
Each tool has a distinct role: listing entries, exploring fields, showing status, running diagnostics, and updating configs. passkey_status and passkey_doctor both touch on security posture, but descriptions clarify that one is a quick status check while the other is a detailed diagnostic. No two tools are truly interchangeable.
All tools share the passkey_ prefix, making the set cohesive. However, the suffix pattern is mixed: passkey_list is verb-like, while passkey_fields, passkey_status, and passkey_doctor are noun-like, and passkey_wrap_server is verb_noun. The prefix provides enough consistency that the naming is still predictable.
Five tools is a well-scoped set for the domain of passkey management for MCP servers. Each tool addresses a clear need without redundancy or bloat, and the count is solidly within the ideal 3-15 range.
The tool surface covers the key workflows: discovering entries, inspecting fields, assessing security status, diagnosing issues, and applying the wrapper. Missing operations like creating or deleting passkey entries are likely out of scope since passkey itself manages those. The only minor gap is the lack of an 'unwrap' or 'revert' operation, but the core purpose is well covered.