Skip to main content
Glama
Sign In
hypernmnesia-mcp-viz

hypernmnesia-mcp-viz

by cdeust
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hypernmnesia-mcp-viz

No user-submitted related servers found.

    Related Servers

    • Booboo

      jessymariau
      A
      license
      A
      quality
      C
      maintenance
      Open-source operational brain that fuses an AI system's agents, memory, knowledge and automations into one rooted, privacy-walled graph, served over MCP with stats, search, node dossiers, neighbors and pathfinding. The same snapshot also renders up to a million nodes in a 3D browser view.
      8
      1
      MIT

    • Threadnote

      threadnote
      A
      license
      B
      quality
      A
      maintenance
      Local-first engineering memory and code-graph tools for coding agents. Supports private session handoffs, code-cited knowledge, repository graph inspection, and optional Git-backed team sharing.
      25
      23 npm
      29
      AGPL 3.0

    • obsidian-local-mcp

      lasheralberto
      F
      license
      B
      quality
      B
      maintenance
      Turns local code repositories into a queryable dependency graph built from AST parsing and git co-edit history, then exposes it alongside an Obsidian vault as persistent memory. Enables context retrieval, impact analysis of proposed changes, and curation of durable prose knowledge through full-text search and Personalized PageRank classification—all fully offline without API keys or embeddings.
      30
      -
    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

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are unmistakably distinct: one launches the bundled browser visualization with side effects, the other returns JSON graph data for a custom client. The descriptions even provide explicit contrasts, so an agent should not confuse them.

    Naming Consistency5/5

    Both names follow the same lowercase snake_case verb_noun pattern: open_visualization and get_methodology_graph. The verb choice maps cleanly to each tool's behavior (open vs. get).

    Tool Count3/5

    Two tools is at the thin end of the scale, though each is broad and covers a distinct access path (human-facing UI vs. JSON data). The descriptions reference list_domains and get_causal_chain, which are not exposed here, making the set feel like a slice of a larger system.

    Completeness4/5

    The core visualization workflows are covered: launch the full browser UI and fetch the methodology graph as JSON for a custom client. Minor gaps include no JSON endpoints for the other bundled views and no explicit stop/status API, though auto-shutdown mitigates the latter.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources