Skip to main content
Glama
Sign In
RelayVault

RelayVault

by ranjitmani61
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to RelayVault

No user-submitted related servers found.

    Related Servers

    • connect

      grossmargin
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables teams to securely store and retrieve credentials, view decrypted secrets or live OAuth tokens, and connect to third-party MCP servers through a unified MCP endpoint.
      MIT

    • Purse

      anantha99
      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

    • Phantom Secrets MCP Server

      ashlrai
      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
    • tasqr-mcp

      tasqr-mcpofficial

      tasqrai
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage task state through MCP, including creating, updating, and tracking tasks, with support for client-side encryption and secure local credential storage.
      21 npm
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool maps to a distinct lifecycle action: write a checkpoint, read/restore one, and enumerate history. 'Commit checkpoint' vs 'checkout handoff' could sound similar at a glance, but the descriptions make the write/read split unambiguous.

    Naming Consistency5/5

    All three follow the same relayvault_ + verb_noun pattern (commit_checkpoint, checkout_handoff, list_history). The namespaced prefix is applied uniformly and verb choice is predictable.

    Tool Count4/5

    Three tools is thin but matches the narrow save/load/list domain of a checkpoint vault. Every tool earns its place; nothing extraneous is present.

    Completeness3/5

    The core write/read/list cycle is covered, but there is no delete/expire operation for stale checkpoints and no way to inspect or rehydrate the redacted placeholder tokens. Agents can work around these gaps, but lifecycle coverage is only partial.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources