Skip to main content
Glama
johnnyclem

hypervault-mcp

by johnnyclem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to hypervault-mcp

No user-submitted related servers found.

    Related Servers

    • domainagent-mcp

      mswat
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for domainagent.dev, enabling AI agents to search, register, deploy, host, and manage domains with USDC payment on Base via x402. Supports static site deployment via Cloudflare Pages and DNS management.
      11 npm
      MIT

    • brewpage-mcp

      kochetkov-ma
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for BrewPage, a free no-signup hosting service. Lets AI agents publish HTML, Markdown, JSON, files, or a full multi-file static site and get a public URL instantly via a REST API.
      3
      Apache 2.0
    • wundervault by wundervault

      wundervaultofficial

      wundervault
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Wundervault zero-knowledge secret management. Exposes vault secrets to AI agents via the Model Context Protocol — secrets are decrypted server-side and never returned to the agent in plaintext.
      1
      63 npm
      2
      AGPL 3.0

    • hive-mcp-morph

      srotzin
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the HiveMorph polymorphic agent runtime, exposing audit log, identity index, supermodel directory, brood carousel, and approval queue with x402 micropayments.
      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

    A3.8/5.0

    Scored across 37 tools

    Disambiguation4/5

    Tools cluster into distinct domains (artifact groups, artifacts, memory wiki, task boards) with clear separations between them. A few potential confusions exist, such as `mind_branch` versus `mind_branches` and `memory_history` versus `mind_log`, but the descriptions resolve these ambiguities.

    Naming Consistency2/5

    Naming conventions vary widely across the tool set. Some tools use verb_noun (`create_artifact_group`, `read_artifact`, `delete_vault_item`), others use noun_verb (`mind_diff`, `tasklist_get`), and a few are bare verbs (`memorize`, `recall`) or phrasal (`save_to_hypervault`), making it hard to predict a tool's name.

    Tool Count2/5

    With 37 tools, the server covers a broad multi-domain platform (artifacts, memories, task boards, vanity subdomains), but the count exceeds the typical well-scoped range. Each domain individually is reasonable, but combined it feels heavy and could overwhelm an agent.

    Completeness4/5

    The tool surface is highly complete across its domains: artifact groups support full lifecycle, memories support create/read/update/delete/history/revert and branching/merging, and task boards cover creation, listing, reading, summary, task creation/update/claim/complete. Minor gaps exist (e.g., no explicit task board deletion, no artifact metadata update), but they are workable.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources