Odile Gate

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.odilelabs/gate and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 20 Oct 2026. Not supplied by the maker.

• gate_create_project

  Put Odile Gate in front of an existing HTTPS API. Returns project_id, admin_key (shown once) and the gateway base URL apps call instead of the API.

• gate_add_app

  Give one app its own key and the calls it may make. Routes are rules like "GET /orders/:id", "POST /orders", "GET /users/{user}/orders" (per-user), or example calls like "GET /orders/42", which become

• gate_list_apps

  The project's apps with their allowed calls, limits and state.

• gate_audit

  The most recent calls through the gateway (time, app, matched route, status, reason, duration), newest first, with totals by status and refusal reason. Gate never stores bodies, query values or header

• gate_create_run

  Gate Actions: give one agent session narrow, expiring permission. Actions are rules with {placeholders} bound by scope (e.g. "PATCH /customers/{customer}/tickets/:id" with scope {"customer":"A"}), eac

• gate_set_app_runs

  Make an app need a run: "writes" (every write needs x-odile-run), "all" (every call), or "off".

• gate_add_approver

  Create an approver key for the person who approves held actions (shown once). Give it to that person, never to an agent: once a project has an approver, the admin key can no longer approve.

• gate_list_actions

  Actions waiting for approval (or in another state), with the exact call. Approving is done by a person in the dashboard, not by a tool.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.