memfix
Related Servers
Alternatives to memfix
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that lets coding agents record what they learn as provenance-carrying observations, retrieve and traverse that shared project memory, and keep contradictory claims side by side for human mediation. It enables opt-in peer sync of a workspace across machines, with every assertion keeping its source, basis, and computed trust tier.Apache 2.0
- AlicenseAqualityBmaintenanceAn MCP server that gives AI agents durable, temporal memory over local markdown vaults, with tools for searching, asserting facts, querying point-in-time state, and reinforcing useful knowledge.15167 npmMIT
- AlicenseAqualityBmaintenanceProvides a SQLite-backed MCP server that records agent memory as history, enabling explicit consolidation, source checks, revisions, narrative versions, and accountable forgetting.15MIT
- AlicenseAqualityBmaintenanceMCP server that gives coding agents persistent, verified memory of codebase decisions, conventions, and skills, with evidence-based claims that are re-checked via git hooks and human-gated review. Enables memory search, propose/approve, chat harvesting, and critique across MCP-compatible tools.21112 npm1MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for coding agents that stores facts in HydraDB, links them to entities, detects revisions, and propagates trust decay through provenance. It provides scoped recall with transparent scoring and abstains when evidence is missing.1MIT
- AlicenseAqualityAmaintenanceMCP server exposing memory search, index, and stats tools for agents, with honesty guards to prevent re-litigation of settled decisions.538 PyPI6AGPL 3.0
TDQS
Scored across 5 tools
Each tool targets a distinct action on memory facts: search reads, assert creates, retract tombstones, audit reports quality, correct applies natural-language fixes. The only mild overlap is between memory_correct and memory_retract, since a natural-language correction may imply a retraction, but the descriptions distinguish them (NL correction vs. explicit tombstone).
All five tools use a consistent memory_verb snake_case pattern with clear, distinct verbs. No mixing of conventions or verb styles.
Five tools is well-scoped for a memory/fact-management server, covering the essential lifecycle operations without redundancy or bloat. Each tool earns its place.
The surface covers create (assert), read (search), update/delete (correct, retract), and quality (audit), which is solid lifecycle coverage. A direct fetch-by-id or explicit fact update tool is missing, though assert returning an id partially mitigates this.