rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Gate for coding agents' MCP and built-in tool calls: rules, approvals and hash-chained receipts
Skills que enseñan a la IA este tipo de trabajo; funcionan junto a este
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Las listas se ordenan por una puntuación de uso (sobre 100) con estas partes
| Popularidad | 6/80 | Estrellas de GitHub o descargas semanales: la mayor cuenta 60, la menor 20 |
|---|---|---|
| Actualidad | 7/12 | Puntuación completa con una versión o cambio de código en 30 días |
| Sigue respondiendo | 0/8 | El endpoint en la nube respondió en la última revisión |
| Puntuación de uso | 13/100 |
Calidad: Pasó 3/3 revisiones básicas (se muestra, no ordena) · Impulso: Sin datos aún (Solo se usa en la pestaña En auge)
Elige la app de IA que usas y copia la configuración.
Pasó 3/3 revisiones · Funciona en tu computadora
Primero: ¿qué IA usas?
Elige tu app y los pasos aparecen abajo.
Claude todavía no puede conectar Derbent
El autor aún no ha puesto cómo instalarlo en el registro MCP
ChatGPT todavía no puede conectar Derbent
El autor aún no ha puesto cómo instalarlo en el registro MCP
B · Otros en Herramientas para desarrolladores que funcionan con ChatGPT
Elegidos entre los más usados de la misma categoría, solo los que se conectan con una dirección y sin clave
Claude Code todavía no puede conectar Derbent
El autor aún no ha puesto cómo instalarlo en el registro MCP
Cursor todavía no puede conectar Derbent
El autor aún no ha puesto cómo instalarlo en el registro MCP
VS Code todavía no puede conectar Derbent
El autor aún no ha puesto cómo instalarlo en el registro MCP
Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps
Ver todas las apps que usan MCP →
La configuración JSON está en “Para desarrolladores”, abajo
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 19 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub tunahanaliozturk, dueña del repo
Último cambio de código: el mes pasado
Usa Apache-2.0
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/servers/tunahanaliozturk-derbent)Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Aún no hay reseñas
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez el mes pasado, y la última versión (1.0.0) llegó al registro hace 2 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code.
En la misma categoría: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Misma categoría, otros creadores, comandos ya revisados. Primero los oficiales, luego por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| Este Derbent | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Dónde se ejecuta | Se instala en tu equipo | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | En la nube o instalado en tu equipo |
| Necesita clave | No | No | No | No | No | No |
| Se añade con + en Claude | No | No | No | Sí | No | No |
| Revisiones básicas | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| Licencia | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Precio | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro |
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
One guarded pass for all your coding agents.
Every tool call that reaches Derbent, MCP or a CLI's built-in tools, is decided by one policy and written to a tamper-evident log, and the calls you care about wait for you.
Derbent guards against mistakes and prompt injection, and keeps an audit trail. It is not a sandbox: an agent that can already run shell commands as you can get around it (see Limits).
In Turkish history, a derbent was a guarded post on a mountain pass: its keepers decided who went through and kept a record of everyone who did. Derbent does the same for your coding agents' tool calls.
Claude Code, Codex, GitHub Copilot CLI and Antigravity CLI connect to Derbent as one MCP server, and your other MCP servers sit behind it. Each CLI's pre-tool hook sends its built-in tools, such as the shell and file edits, through the same gate. Every call is decided by your rules and written down.
Support for Codex and Antigravity CLI is experimental (configured from their docs, not yet checked in a real session).
It is one binary for Windows, macOS and Linux. There is no daemon and no network listener: a SQLite file is the only shared state (ADR 0001).
a in the terminal UI, or is denied after 50 seconds by default.derbent verify names the first receipt where the chain breaks after one was edited, moved, inserted or removed. Keep the head hash it prints to catch the newest ones being deleted too.Also:
Download the binary for your system and SHA256SUMS from the latest release, check the hash, and put it on your PATH as derbent (derbent.exe on Windows):
# Linux on amd64; the other files differ only in the end of the name
curl -LO https://github.com/tunahanaliozturk/derbent/releases/download/v1.0.0/derbent-v1.0.0-linux-amd64 curl -LO https://github.com/tunahanaliozturk/derbent/releases/download/v1.0.0/SHA256SUMS sha256sum --ignore-missing -c SHA256SUMS install -m 755 derbent-v1.0.0-linux-amd64 ~/.local/bin/derbent
Or build it with Go 1.27 or later:
go install github.com/tunahanaliozturk/derbent/cmd/derbent@latest
Homebrew (brew install tunahanaliozturk/tap/derbent) and Scoop install it too; see Install and set up.
Every release can be rebuilt byte for byte from its tag. Install and set up has the other systems, how to check a release, and each CLI's entries by hand.
derbent init --preset balanced # add Derbent to each CLI it finds, and write a first config
derbent doctor # check what init wrote derbent # open the terminal UI in a terminal of its own
derbent init shows every change and asks once before it makes any. It copies each file it changes first and never replaces an entry you already have. With --dry-run it only shows the changes. Two of them, from a real run with the paths shortened:
claude: ~/.claude.json
copied first to ~/.claude.json.derbent-backup-20260930T205424Z runs: claude mcp add --scope user derbent -- ~/bin/derbent mcp --agent claude derbent: ~/.config/derbent/config.toml a new file adds the balanced preset (derbent init --preset balanced --print shows it)
It also adds the derbent gate hook to each CLI's settings; Install and set up shows every entry. Start your agents as usual. Their calls now appear in the UI, and calls the rules ask about wait there for you. Built-in tools says what each CLI's hook covers.
To put your other MCP servers behind the gate, so each agent needs only the one derbent entry, see Downstream servers.
Rules live in config.toml in your user config directory (%AppData%\derbent\ on Windows, ~/.config/derbent/ on Linux, ~/Library/Application Support/derbent/ on macOS). A downstream MCP server's tools are named __ , and a CLI's built-in tools native__ :
[[rule]]
tool = "github__issue_read" action = "allow"
[[rule]] tool = "github__*" # every other GitHub tool waits for you action = "ask"
[[rule]] agent = "claude" tool = "native__Bash" # Claude Code's shell, through the hook args = { command = "git push*" } action = "ask"
[[rule]] action = "allow" # the last rule has no condition
To see how a call would be decided before it happens:
derbent explain --agent claude --tool native__Bash --args '{"command":"git push origin main"}'
It prints each rule and why it matches or not, down to the first match, then the project's rules, budgets, pin and grant, and ends with verdict: ask (rule:3) for this call under the rules above. Rules covers globs, the three presets (watch, balanced, strict), project rules, budgets and rule suggestions.
derbent verify # count, head hash, and whether the chain is intact
derbent receipts --agent codex --since 1h # also --tool, --project, --limit, --json
A receipt keeps the arguments after masking secrets, and only the size and hash of what a tool returned (ADR 0004). Someone who can write the database could still rewrite the whole chain or delete the newest receipts, so keep the head hash somewhere else if you want to be able to tell later. Receipts and verify covers exports that can be checked without the database.
| Command | What it does | More |
|---|---|---|
derbent | Terminal UI: waiting calls, agents, live receipts, memory, grants | Approvals |
derbent init, derbent doctor | Add Derbent to each CLI, then check the setup | Install |
derbent mcp --agent | The MCP server each CLI starts | Install |
derbent gate --agent | The pre-tool hook for built-in tools | Built-in tools |
derbent pending, approve, deny | Answer waiting calls from any shell | Approvals |
derbent grants, revoke | List and take back session grants | Approvals |
derbent explain | Show how a call would be decided | Rules |
derbent suggest | Print the rules your answers point to | Rules |
derbent config check | Validate the config and list each server's tools | Servers |
derbent pins | See and accept changed downstream tools | Servers |
derbent receipts, verify | Read, export and verify receipts | Receipts |
derbent handoffs | List the tasks agents left for each other | Memory and handoffs |
derbent version | Print the release |
Measured on GitHub's hosted runners on 2026-10-01 (Linux on an Intel Xeon Platinum 8370C, Windows on an AMD EPYC 9V74, 4 vCPUs each), median of ten runs at p50, from docs/benchmark-results:
| Linux | Windows | |
|---|---|---|
| MCP tool call, direct to the server | 256.5 µs | 293.0 µs |
| MCP tool call, through the gate | 756.0 µs | 909.0 µs |
| Starting the binary and exiting | 4.292 ms | 40.40 ms |
Hook call, derbent gate, allowed | 6.421 ms | 64.51 ms |
The gate adds 499.5 µs to an MCP call on Linux and 616.0 µs on Windows, for the extra stdio hop, the rule decision, the project rules check and the receipt written to SQLite. A hook call costs about 2.1 ms more than starting the binary on Linux and 24 ms more on Windows, where most of its cost is the process start. The numbers come from one run on shared runners, and runs differ by more than one run's intervals: the day before, the same code on the same Windows CPU model put the gate 459.5 µs over a direct MCP call, against 616.0 µs here. The results page has p99, calls per second and the caveats.
The whole list, with the reasons, is under Known limits and risks. The ones to know first:
git push* does not match cd repo && git push.derbent approve itself.allow for a command prefix lets any options through.handoff_take can claim every open handoff addressed to *.ask means denied after the timeout.