Skip to main content
Glama
iamredmh

volta-mcp-server

by iamredmh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to volta-mcp-server

No user-submitted related servers found.

    Related Servers

    • SecureNote.link MCP Server

      jackalterman
      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
      -

    • zKettle

      benderterminal
      A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted, zero-knowledge encrypted, self-destructing secrets for secure agent-to-agent coordination
      3
      AGPL 3.0

    • hydrate-dehydrate-mcp

      slidingbox
      A
      license
      A
      quality
      F
      maintenance
      Hand a secret to another agent as an encrypted, pay-per-read token delivered exactly once, leaving no copy behind. Also pre-flights an x402 endpoint before your agent pays it. Runs locally over stdio and encrypts in your own process, so there is no hosted version to hand your plaintext to.
      2
      3
      137 npm
      ISC

    • vnsh-mcp

      raullenchai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables sharing and reading encrypted files (text, images, logs) for AI workflows, with automatic 24-hour expiration and host-blind security.
      19 npm
      157
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources