HCC
Related Servers
Alternatives to HCC
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP-native persistent memory layer for AI agents across Claude Code, Cursor, VS Code, and OpenClaw. Powered by hybrid vector search, BM25, and cross-encoder reranking with a published 73.1% LoCoMo benchmark accuracy.84Apache 2.0
- AlicenseNot gradedqualityDmaintenancePersistent, semantically-searchable memory for AI agents using local PostgreSQL, pgvector, and Ollama embeddings, exposed via MCP with hybrid retrieval, knowledge graph, and auto-recall hook.3 npmMIT
- FlicenseNot gradedqualityFmaintenanceCognitive memory system for AI agents with 129 MCP tools. Persistent 6-tier hierarchical memory (working→short-term→long-term→semantic), Ebbinghaus forgetting curves, dream consolidation, hybrid retrieval (BM25+RRF), goal tracking, emotional recall, knowledge graphs, and a 26-job consciousness daemon. Works with Claude Code, Cursor, and any MCP client.-
- AlicenseAqualityBmaintenanceLocal-first memory for Claude Code and any MCP client: hybrid vector + keyword search and a bi-temporal knowledge graph in one SQLite file. Local embeddings, no API key, $0/token.5159 npm1PolyForm Noncommercial 1.0.0
- FlicenseNot gradedqualityBmaintenancePersistent semantic memory MCP server for AI agents with hybrid search, LLM scoring, and decay engine, fully local.2-
- AlicenseAqualityAmaintenancePersistent memory MCP server for AI coding agents (Claude Code, Codex, Gemini CLI). Hybrid retrieval (vector + BM25), cross-encoder reranking, knowledge graph, session checkpoint/resume, and multi-scope isolation. Local-first with LanceDB.30200 npm15MIT
TDQS
Scored across 8 tools
Store, delete, and evaluate are clearly distinct, but there are four retrieval-oriented tools (search_memories, semantic_search, hybrid_search, recall) with overlapping purposes. The descriptions help differentiate them, but an agent could easily pick the wrong one when simply trying to find relevant memories.
Several tools follow a verb_noun pattern (store_memory, delete_memory, search_memories, get_recent_memories), but recall is a bare verb and semantic_search/hybrid_search are adjective_noun names. The mixed conventions are readable but not fully consistent.
With 8 tools, the server is well-scoped for a memory system. Each tool serves a meaningful purpose: storing, retrieving via multiple strategies, deleting, and evaluating whether content is worth remembering.
The core memory lifecycle is covered: store, retrieve, search, recall, and delete. One minor gap is the lack of an update/edit operation for existing memories, though this can be worked around by storing a new memory or deleting the old one.