Skip to main content
Glama
WeberG619

NeverOnce

by WeberG619
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to NeverOnce

No user-submitted related servers found.

    Related Servers

    • AI Diary MCP Server

      pangxianggang
      A
      license
      Not graded
      quality
      C
      maintenance
      A private, local-first MCP server that gives any AI long-term memory — its own diary. Zero models, zero network, zero subscription; smarter search than Notion, running entirely on your machine.
      MIT

    • kontexta

      safiyu
      A
      license
      A
      quality
      A
      maintenance
      A local-first MCP server that gives AI coding agents persistent memory and controlled commands. Features a git-backed markdown knowledge vault with FTS5 search, surgical section edits, token-aware context budgeting, and a sandboxed command engine with human approval gates. Works with Claude Code, Cursor, Copilot, Gemini, and more.
      4
      58
      316 npm
      1
      Apache 2.0
    • dakera-mcp by Dakera-AI

      dakera-mcpofficial

      Dakera-AI
      F
      license
      A
      quality
      B
      maintenance
      Self-hosted MCP-native agent memory server. Gives AI agents persistent, decay-weighted memory via 83 MCP tools — no cloud, full control. RocksDB+HNSW backend. Works with Claude Code, Cursor, and any MCP-compatible agent.
      14
      8
      -

    • apex-memory

      JJerryChoi
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory for AI coding agents. Enables agents to save and recall decisions, patterns, bugs, and context across sessions via an MCP server with local SQLite storage.
      4 npm
      2
      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.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: store vs correct are differentiated by intent (general memory vs correction), and recall vs check serve different workflows (searching vs pre-flight verification). Minor ambiguity exists between store and correct since both write memories with similar arguments, but the correction semantics are explicit.

    Naming Consistency4/5

    Tool names are mostly single-word imperative verbs (store, correct, recall, check, forget), which is a clear and predictable pattern. Two deviations: 'helped' is past tense rather than imperative, and 'stats' is a noun rather than a verb, creating minor inconsistency.

    Tool Count5/5

    Seven tools is well-scoped for a memory store: write, special write, read/search, preflight check, feedback, delete, and stats. Each tool serves a distinct operational need without redundancy or bloat.

    Completeness4/5

    The core memory lifecycle is covered: store, search, correct, provide feedback, delete, and inspect. Minor gaps exist, such as no direct memory content editing or namespace management, but the feedback and correction mechanisms fill most practical needs.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources