vivac
Related Servers
Alternatives to vivac
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA 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.Apache 2.0

markovian-mcpofficial
AlicenseAqualityBmaintenanceBitcoin-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
- AlicenseCqualityAmaintenancePersistent 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.567 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables provenance capture and replay verification for scientific MCP tool calls, using a signed hash-chained ledger and data-source release resolution.MIT
TDQS
Scored across 17 tools
Several node-lifecycle tools have overlapping purposes: push vs add (both create nodes, but one moves focus), pop vs done (both close, but one focuses), and note vs decide vs add (recording facts vs decisions vs nodes). Descriptions attempt to differentiate, but the subtle boundaries leave room for misselection.
All 17 tools use the same `vivac_` prefix followed by a single lowercase word, consistently in snake_case. There is no mixing of camelCase or different verb styles, making the naming pattern highly predictable.
With 17 tools, this server sits at the upper bound of typical tool counts (3–15). While each tool has a distinct niche in a complex domain, the volume may feel heavy and could overwhelm an agent's selection process.
The surface covers node creation, closure, parking, notes, decisions, rules, artifacts, and agents, leaving few obvious gaps. Minor omissions like direct node updates or deletion are workaroundable and may be intentional.