Home / MCP registry index / com.odilelabs/gate
Odile Gate
com.odilelabs/gate in the official MCP registry.
Endpoint https://gate.odilelabs.com/mcp.
The registry describes it as: Free, no signup: your agent puts each app on its own key, allowed calls, approvals and an audit log.
We read its 21 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
gate_openshell_setup gate_create_project gate_add_app gate_list_apps gate_check_setup gate_metrics gate_audit gate_create_run gate_set_app_runs gate_set_response gate_add_approver gate_list_actions gate_explain_refusal gate_delegate_run gate_learn_suggestions gate_audit_proof gate_audit_verify gate_run_tree gate_run_timeline gate_validate_config gate_sync_declarative
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-odilelabs-gate)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.