Servidor MCP de Odile Labs

• Nombre en el registrocom.odilelabs/gateverificado en el registro MCP

El nombre en el registro está bajo odilelabs.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-24
• Herramientas21
• El servidor se llamacom.odilelabs/gate
• Versión del servidor1.6.0
• Versión del protocolo2025-06-18

El 2026-10-24 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 75 ms.

• Sus herramientas no hacen ninguno de los casos de uso comprobados: answer calls and text owners each caller's name, number and need; forward missed calls to a receptionist after hours; reply to customers by text after calls come in.
• Comprobado 3 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 3 hasta ahora
• Qué puede hacer un agente con él0 de 3 casos de uso
• Respondiómidiendo3 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta128 ms
• Espacio en el contexto del agente≈ 4410 tokenslas definiciones de todas sus herramientas (21), que el agente lleva en cada turno
• Definiciones de herramientasA · 97 de 100
• Resultados tipados0 de 21 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 4 de 21

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• gate_openshell_setup

  Read-only local setup plan for native OpenShell + Gate: one command, exact installer hash, recipe schema, prerequisites, authority boundaries and cleanup. Default creates an isolated Free read-only demo with no model or payment. A trusted…

• gate_create_project

  Create a Free project in front of an existing HTTPS API. No signup or payment required. For a credential-free demo use https://sandbox.gate.odilelabs.com with GET /customers/:cid/tickets/:id. Returns project_id, admin_key (shown once) and…

• 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 rules allowing any id. Returns key…

• gate_list_apps

  The project's apps with their allowed calls, limits, state and anomaly-guard settings.

• gate_check_setup

  Read actual Gate protection settings before giving an integration production access. Reports observe-only mode, writes without mandatory runs, missing user-token configuration, wildcard grants and approval separation, with evidence, exact…

• gate_metrics

  Read last-24-hour stored call counts by HTTP status and reason, measured duration through response headers (including upstream wait), per-app anomaly scores and 24-hour anomaly counts, and separate current-month gateway usage: plan, used…

• 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 headers.

• 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"}), each with an optional max and approval…

• gate_set_app_runs

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

• gate_set_response

  Opt-in JSON response redaction: return only explicit JSON Pointer paths, e.g. /id and /items/*/name. * matches one segment; selecting a container allows its whole subtree. Applies to every upstream response for this app, including errors…

• 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. With an installed approval-risk model, pending actions sort by risk descending and include risk (0–1) and risk_features (top two advisory signals). No model means no…

• gate_explain_refusal

  What a Gate refusal means and how to fix it, from the x-gate-refused header value (e.g. route_not_allowed).

• gate_delegate_run

  Hand a narrower run to another active app in the same project. Uses the parent app key and run token, never the admin key. Scope, expiry, approvals and ancestor budgets stay enforced; maximum depth five.

• gate_learn_suggestions

  Read normalized routes and a suggested per-minute limit from an admin-enabled, time-boxed learning session. Records only method, normalized path templates and counts per minute; no query values, raw ids, headers or bodies. Never enables…

• gate_audit_proof

  Read chained audit rows, decided-action feature snapshots and anchors with an HMAC-SHA256 signature. No sealed paths/bodies, notes, keys or IPs in the action labels. Legacy actions lack snapshots and are excluded. store_audit=false has no…

• gate_audit_verify

  Recompute a pasted export chain and project signature; returns intact or broken_at (one-based row position). Does not approve actions or change permissions.

• gate_run_tree

  Read a run and its delegated descendants without tokens.

• gate_run_timeline

  Read call metadata, approvals and approver names, recovery outcomes and delegated children; no bodies or query values.

• gate_validate_config

  Parse and check a declarative Gate config (apps, routes, rate limits, run mode, plugins including anomaly-guard, alerts, approvers) without changing anything. anomaly-guard settings: mode off|alert|strict, z_threshold 2–10, min_minutes…

• gate_sync_declarative

  Make a Gate project match an odile.yaml: creates the project (if no project_id) and missing apps and approvers, applies run mode, loop, learning and anomaly-guard settings and alerts. Example plugin: {name: anomaly-guard, settings: {mode…

• com.odilelabs/odileresponde, 23 herramientasverificado en el registro MCP