Derbent runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 4 Oct 2026.
Gate for coding agents' MCP and built-in tool calls: rules, approvals and hash-chained receipts
What the code does
We read the source, 10 d ago · rules ccca72095570
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
e.Config, e.ConfigMissing, e.Project, e.ProjectFile = cfgPath, missing, key, filepath.Join(root, config.ProjectRulesFile)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Derbent
same job, measured the same waySigned receipts and Cedar policies for AI agent tool calls. Claude Code hooks, MCP gateway.
Governed MCP gateway: policy gate on every tool call, hash-chained DSSE receipt on every result.
Fail-closed deterministic checks and hash-chained receipts for AI agent outputs via MCP.
Governed MCP front door to FLOCORE; write calls need human approval and signed receipts.
Signed, hash-chained provenance receipts for AI agent actions.
Fail-closed quality gate and hash-chained receipt ledger for AI agent workflows.
Fail-closed Cedar policy gate + Ed25519 signed receipts for agent tool calls. Denies on any error.
A local receipt and approval gate for AI agent sessions. The agent can act, but it cannot sign.
Derbent — questions
Answers built from our own checks of this server.