vivac
Related Servers
Alternatives to vivac
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA tree whose vocabulary, rules and solvers are data, edited at runtime through generic tree_* tools. Rules go red on the node that breaks them, so it works as a design-dexision ledger on any checked knowledge base.14Apache 2.0

markovian-mcpofficial
AlicenseAqualityCmaintenanceBitcoin-anchored provenance for AI outputs; enables stamping, verifying, and tracing outputs with offline-verifiable canonical roots.3Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables tracking and querying the provenance of AI-generated code, showing which sources influenced each line of code.MIT
- AlicenseCqualityBmaintenancePersistent multi-agent work graph and document-state machine for contracts, specs, slices, evidence, verification, handoffs, and cost-aware AI execution.7Apache 2.0
- AlicenseBqualityDmaintenanceVerifiable agent-to-agent task handoff with signed provenance chain.557 PyPIMIT
- 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
TDQS
Scored across 17 tools
Most tools map to distinct phases, but several clusters overlap: brief/open/why all expose context and lineage, while add/push/decide/note/park/save all record state, and done/pop both close work. Descriptions give explicit routing rules, so an agent can usually disambiguate, but the tool set still requires careful reading to avoid misselection.
All names share the vivac_ prefix and a lowercase single-word suffix, making the family recognizable. However, suffixes mix nouns (artifacts, agents, rules, brief, why) with verbs (open, push, pop, done, add, decide, note, park, save, arm), and names like why/open/pop are not self-explanatory without descriptions.
17 tools is slightly heavy but defensible for a server spanning project-tree lifecycle, governance, artifacts, and agents. The project-state operations are fine-grained while artifacts and agents are broad multi-operation tools, so the count is reasonable but near the edge.
Core lifecycle coverage is strong: orientation/search, node creation, focus push/pop, closure, notes/decisions/parking/saves, and governance with verification commands are all represented. Gaps include no general update/edit/rename or explicit reopen/unpark operation for existing nodes, but these appear partly intentional in the append-only/closure model and are workable.