Skip to main content
Glama
volta-mcp-server

volta-mcp-server

by iamredmh

Related Servers

Alternatives to volta-mcp-server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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
      -
    • A
      license
      A
      quality
      B
      maintenance
      Lets AI agents encrypt a password, API key, or note locally, pay a small USDC fee over x402 on Base, and share a single-use link that can be opened exactly once and is destroyed on read. Reading is free, expiring unread secrets are cleaned up, and the server only ever stores ciphertext.
      10
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted, zero-knowledge encrypted, self-destructing secrets for secure agent-to-agent coordination
      3
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents a shared, encrypted workspace they can create, list, read, update, version-history, restore, renew and share via a single link that multiple agents and people can read and write. Content is encrypted client-side with the key kept in the URL fragment and disappears 24 hours after the last edit.
      7 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create, read, update, list, and restore shared encrypted workspaces and one-shot links that both people and other agents can open and edit through a single URL. Content is encrypted client-side, version-checked on write to prevent clobbering, and expires 24 hours after the last edit.
      7 npm
      MIT

    TDQS

    A4.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The tools have clearly distinct purposes with no functional overlap: one creates secure notes while the other consumes them. An agent can easily distinguish between generating a new URL versus retrieving and destroying an existing note.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern using snake_case (create_volta_note, read_volta_note), with identical resource naming ('volta_note') and parallel grammatical structure.

    Tool Count4/5

    While two tools falls slightly below the typical optimal range, it is reasonable for this narrowly scoped one-time secret service where only creation and retrieval operations are relevant to the security model.

    Completeness4/5

    The tools cover the essential lifecycle (create and read-once-destroy) for secure note sharing. Minor potential gaps include missing expiration configuration or metadata retrieval, though these may be intentionally excluded for security.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive