Skip to main content
Glama

Related Servers

Alternatives to Encryptor MCP

Related Servers

  • A
    license
    A
    quality
    D
    maintenance
    Enables AI memory persistence and secure credential management via vault tools for MCP-compatible clients like Claude Desktop, Cursor, and VS Code.
    12
    9 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to persistently remember user preferences and context through client-side encrypted vaults, ensuring memory is portable and private across different MCP clients.
    1
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables agents to access a shared portable vault for memory, skills, and API credentials through MCP, so tools can store and retrieve memories, read versioned skill playbooks, and make server-side API calls without exposing secret keys.
    Apache 2.0
  • A
    license
    A
    quality
    C
    maintenance
    Enables AI agents to access a local-first personal context and memory layer through MCP tools for bootstrapping user context, semantically searching Markdown vault knowledge, reading files, listing topics, and adding controlled memories. It provides deterministic context retrieval, provenance-cited vector search, and secure vault operations while keeping data local and model-independent.
    6
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI coding tools to securely manage secrets via MCP tools for vault operations, diagnostics, and cloud sync, ensuring real keys never enter the LLM context.
    20
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents and development tools to interact with Obsidian vaults via MCP, providing direct filesystem access for reading, writing, searching, and managing notes without requiring Obsidian to be running.
    Apache 2.0

TDQS

A4.2/5.0

Scored across 23 tools

Disambiguation5/5

Each tool targets a distinct action or resource, and the descriptions explicitly cross-reference adjacent tools (find vs list_folder, undo vs restore_version, locate vs decrypt_name). Even where concepts are close, the boundaries are clear enough for an agent to choose correctly.

Naming Consistency3/5

All names are snake_case, but the conventions are mixed: imperative verbs (lock, move, find, trash), noun phrases (vaults, versions, file_info, control_center), and verb_noun names (list_folder, read_file, restore_version). They remain readable, but the pattern is not predictable.

Tool Count3/5

23 tools is above the typical well-scoped 3-15 range and feels heavy for a single server. The domain is complex—vault lifecycle, file operations, trash, versions, and security—so many tools earn their place, but the surface is still borderline large.

Completeness5/5

The tool set covers vault discovery/unlock/lock, file reading/writing/appending, folder and move/copy operations, trash lifecycle, undo, versions/restore, search/locate/decrypt, health checks, and change history. No obvious agent-facing lifecycle gap remains; vault creation and some user approvals are appropriately handled outside the chat.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues