Derbent
Related Servers
Alternatives to Derbent
- AlicenseAqualityCmaintenanceHuman-in-the-loop approval gateway for agent tool calls: agents request, policies decide, humans approve via Slack/Discord/web — with an OWASP-LLM-Top-10-tagged audit trail. Self-hostable.1018 npm33MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to call backend tools under per-agent policy, deciding which tools each agent can see, what arguments it may pass, how often it may call, and which writes wait for human approval. It also redacts secrets and PII from tool results, fences untrusted output against injection, and records every call in a hash-chained audit log.25 npmMIT
- AlicenseBqualityAmaintenanceThe safety gate between AI agents and your servers: 25 typed, policy-checked tools for services, logs, Docker, disk, ports and nginx, with human approval for changes and a hash-chained audit log.251MIT
- AlicenseAqualityBmaintenanceLocal zero-trust permission gateway for AI agents. Enforces policy-based tool authorization, human approvals, scoped permissions, and cryptographically verifiable audit logs.4101 PyPI5Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA local proxy in front of any MCP server for developers on Claude Code or Cursor: see every tool call your agent makes, hold the risky ones for your approval, and keep a secret-redacted journal that is tamper-evident with an external anchor.115 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceSafe, reversible tool execution for AI agents. It sits between an agent and its tool servers, adding contracts, dry-run planning, policy, approvals, saga execution, and rewind.MIT
- AlicenseAqualityAmaintenanceUniversal session & handoff layer for AI coding agents: shared task, decision, blocker and test state, checkpoints, and deterministic handoff between Claude Code, Codex, OpenCode, Cursor, Cline, pi and omp. Local SQLite, git-aware, 25 tools + 7 resources over stdio or streamable-http.26MIT
TDQS
Scored across 7 tools
The seven tools split cleanly into two non-overlapping domains (handoffs and memory notes), and within each domain the operations target distinct lifecycle stages. handoff_create/take/list/done are unambiguous, and memory_read (by id) versus memory_search (by query) are clearly differentiated.
All names use a predictable snake_case namespace_verb pattern (handoff_*, memory_*), which is easy to scan. The only minor wrinkle is handoff_done, which is a state adjective rather than a verb like the others, but consistency overall is strong.
Seven tools is a well-scoped set for a coordination server: four handoff operations and three memory operations, each earning its place. Nothing is redundant or missing at the count level.
Coverage is solid: handoffs support create/list/take/done, and memory supports write/read/search plus supersedes for replacement. Minor gaps remain (e.g., no delete or list-all for memory notes, no cancel/release for a taken handoff), but agents can work around these.