Bilinc
Related Servers
Alternatives to Bilinc
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceExposes repo-native, self-verifying memory to coding agents over stdio MCP, letting them recall ranked past decisions, record new claims with verifiable receipts, and check the health and stats of stored memory. Keeps agent context honest by surfacing memories whose evidence no longer holds.7 npmMIT
- FlicenseNot gradedqualityCmaintenanceServes local-first project memory over stdio, exposing tools to inspect project state, search and retrieve context, report memory, and create Git-aware checkpoints for coding agents.1-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to commit and read shared memory facts that must cite a registered artifact SHA-256 receipt, with confidence that decays over time and a cascade rollback that quarantines a poisoned fact plus every downstream decision derived from it. Exposes provenance tracing (blame), evidence registration, and commit/revert tools over stdio so multi-agent teams can detect and unwind cascading memory poisoning.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to persist project memory across sessions by compiling decisions, progress, and pitfalls into git-linked, evidence-backed entries. It lets clients add, query, inject, scan for stale, check assertions on, and compute ROI of those memories over stdio.367 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides a local stdio MCP server that gives AI coding agents a typed, temporal, evidence-backed memory on embedded SQLite, letting them record decisions and constraints, ask why something happened, navigate memory by time, trace proof paths between refs, and export or supersede stored state without rewriting it. It also exposes read-only ChronoLoom view tools so a person and their agent can steer the same multidimensional memory view by semantic intent rather than raw coordinates.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables development agents to keep persistent memory: proposing and reviewing workspace-scoped content, running hybrid search over accepted sources, and resuming projects with auditable history and provenance. It exposes 32 MCP tools over stdio and authenticated Streamable HTTP, with optional embeddings and rerank.Apache 2.0
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes: recall vs list_memories, diff vs history, and snapshot vs rollback are unambiguous. The main overlap is commit_mem vs revise, both updating existing keys, though the descriptions explicitly guide when to use revise instead of commit_mem.
Names mix single verbs (diff, confirm, forget), nouns (history, snapshot, status), and two snake_case verb_noun forms (list_memories, commit_mem). The set remains readable, but there is no consistent naming convention.
11 tools is well-scoped for a memory and checkpoint service. Each tool earns its place, with no obvious bloat or missing essential operation.
The surface covers the full memory lifecycle (create, read, update, confirm, forget), version history, checkpointing (snapshot, diff, rollback), and workspace discovery (status). No critical gaps are apparent.