What it does
The server exposes tools such as verifyActionGate and get_architectural_blast_radius, which coding agents can call through the Model Context Protocol. It traverses dependency paths of up to eight hops across decisions, facts and source documents, and it approves or blocks an action based on the current graph state. When an action is blocked, the result includes violation paths and line-level ADR citations. The graph also records superseded decisions, so an older decision is not treated as current.
Teams using coding agents such as Cursor, Claude Code, Cline, Windsurf or GitHub Actions CI can reach for it when they want file changes checked against a shared, versioned set of architectural decisions. Each repository and branch gets its own isolated graph, and the agent runtimes read the same graph state.
The publisher's web console includes a graph visualisation with a live Cypher query inspector, a pre-flight action playground, and a tamper-evident audit ledger that records each tool execution, verdict, target file path and grounding decision ID. Plan quotas, subscription tiers and MCP API keys are managed from a profile page.
Limitations and requirements
Access depends on subscription tier and plan quotas, and MCP API keys must be provisioned from the profile page. Agents cannot execute file writes without graph clearance, so actions depend on the graph's decision records being kept up to date.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CAVDAX/cavdax
CAVDAX MCP Server backed by FalkorDB GraphBLAS for causal invalidation gating and ADR provenance.
v1.3.3As shown on registry.modelcontextprotocol.io when we last read it