Hivelore
Related Servers
Alternatives to Hivelore
- FlicenseAqualityAmaintenanceA basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats.9138,656 npm91,381-
Related Servers

corbatofficial
AlicenseAqualityDmaintenancePolicy and quality engine for AI coding agents that enforces team coding standards and provides validation gates for agent-assisted software delivery.733 npm5MIT- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to evaluate actions against team-defined policies, record decisions, and obtain human approvals for potentially risky operations.57 npm1-
- FlicenseAqualityDmaintenanceProvides real-time policy enforcement for AI coding agents by intercepting and validating their actions against organizational standards like naming conventions, security policies, and compliance rules before execution. Prevents violations through immediate feedback and auto-correction suggestions.5-

Tently MCPofficial
AlicenseNot gradedqualityAmaintenanceEnables coding agents such as Claude Code and Cursor to check a team's learned decisions from pull requests, reviews, and docs before writing code, showing whether breaking them is blocking or advisory. It also provides locally computed symbol impact/blast-radius analysis so source code never leaves the machine.356 npm1MIT- AlicenseBqualityDmaintenanceGives AI coding assistants persistent memory, safety controls, and project awareness by tracking coding sessions, protecting critical files from modifications, and managing approval workflows with automatic changelog generation.1916 npmMIT
- AlicenseAqualityDmaintenanceActs as a production-grade safety layer for AI-assisted coding, monitoring Git hygiene, scanning for security issues (PII, secrets, injection), and enabling semantic history search.9MIT
TDQS
Scored across 16 tools
The core retrieval tools (get_briefing, mem_relevant_to, mem_search, mem_get) overlap in purpose, but the descriptions explicitly stage them via progressive disclosure and state when to prefer each. mem_save vs mem_tried, code_map vs code_search, and propose_sensor vs scaffold_test are clearly differentiated. Only minor residual ambiguity remains in the memory-retrieval cluster.
A clear mem_* family (mem_save, mem_get, mem_update, mem_verify, mem_search, etc.) and a code_* family (code_map, code_search) give strong internal consistency, with verb_noun style elsewhere. A few standalone names (get_briefing, pre_commit_check, report_friction) break the prefix grouping, but everything stays readable.
16 tools is at the upper edge of a comfortable set, spanning memory CRUD, code intelligence, validation, sensors, and feedback. Most tools earn their place, though report_friction and the sensor pair lean toward feature sprawl for a memory server. Slightly heavy but defensible.
Strong lifecycle coverage: create (mem_save/mem_tried), read (mem_get/mem_search/get_briefing), update (mem_update), verify (mem_verify), feedback, session recap, sensors, and pre-commit gating. The notable gap is the absence of any explicit delete/archive/forget operation, and no list-all primitive, but these are minor.