Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Odile Gate Oversight

REMOTE · GATE.ODILELABS.COM

Watch Odile Gate: runs, held actions, audit log with signed export, metrics and refusal reasons.

+3 this week 69 Trust /100

Last scanned (19 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security66
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2921 tokens (~194/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 91% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1
    • Tool “gate_export_audit_proof” rewrote its description, which is the text the model reads security
    • Tool “gate_learn_suggestions” rewrote its description, which is the text the model reads security
    • Tool “gate_list_actions” rewrote its description, which is the text the model reads security
    • Tool “gate_export_audit_proof” is now declared destructive security
    • Tool “gate_learn_suggestions” is now declared destructive security
    • Tool “gate_list_actions” is now declared destructive security
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 66

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://gate.odilelabs.com/mcp/oversight

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=odilelabs.com CN=WE1,O=Google Trust Services,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA256 42dda9c0f3e7060113f43b02876534c1
SANs: odilelabs.com, gate.odilelabs.com, *.gate.odilelabs.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of gate.odilelabs.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
odilelabs.com. DS published 2371 13 Verified
gate.odilelabs.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gate.odilelabs.com/mcp/oversight Verified 200
http (plaintext) http://gate.odilelabs.com/mcp/oversight HTTPS enforced 301 https://gate.odilelabs.com/mcp/oversight
MCP tools · 15 exposed · ~2,732 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
gate_create_run ~350

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. Check gate_list_approvers for an active human approver before granting approval:true actions; create one on the setup endpoint, /mcp/setup if needed; without an active approver the grant is refused. Returns a run token (shown once) the agent sends as x-odile-run with its app key. Writes in a run need an Idempotency-Key. Give a write a check ("GET /bookings?idempotency_key={key}") and the agent can settle a lost answer with POST /g/<id>/_gate/recover.

NameTypeReqDescription
actionsarrayyesRules, or {rule, max, approval, check}
admin_keystringyesThe project admin key (ga_...). Read it from the .env; never print it.
appstringyesThe app id (app_...) this run is for
labelstring–Optional: what the run is for, e.g. "triage ticket 4411"
max_callsinteger–Optional: calls allowed in the whole run
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...
scopeobject–Values for the {placeholders}, e.g. {"customer":"A"}
ttl_secondsinteger–How long the run lasts (default 3600)

No output schema declared.

No examples provided.

gate_delegate_run ~162

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.

NameTypeReqDescription
actionsarrayyes–
appstringyesThe destination app id
app_keystringyesThe parent app key (gk_...)
labelstring–A short label for the delegated job
max_callsinteger––
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...
run_tokenstringyesThe parent run token (gr_...)
ttl_secondsinteger––

No output schema declared.

No examples provided.

gate_explain_refusal ~70

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

NameTypeReqDescription
reasonstringyesThe x-gate-refused value
recoverableboolean–Whether the write was granted with a recovery check

No output schema declared.

No examples provided.

gate_export_audit_proof ~249

Which signed audit records can I export for verification? Returns chained audit rows, decided-action feature snapshots and signed anchors; use it for a portable tamper-evident export instead of gate_read_audit's recent-call view, then check it with gate_verify_audit_proof. No sealed paths/bodies, notes, keys or IPs in the action labels. Legacy actions lack snapshots and are excluded. store_audit=false has no chain. Follow next_from for audit rows and next_actions_after as actions_after for labels (10,000 each). Use API/SDK to verify exports above the MCP request size limit. The signature is HMAC-SHA256. This also expires overdue held actions in the project and clears their stored request paths and bodies.

NameTypeReqDescription
actions_afterstring–Action cursor from next_actions_after
admin_keystringyesThe project admin key (ga_...). Read it from the .env; never print it.
frominteger––
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...
tointeger––

No output schema declared.

No examples provided.

gate_get_metrics ~279

What are the project call trends and current usage? Returns project-wide 24-hour call aggregates, anomaly scores, idle apps and current-month usage; use it for operational trends rather than individual calls in gate_read_audit or one run in gate_get_run_timeline. Includes 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, idle apps (active apps whose key made no allowed call in the project's idle_days, default 14; a flag only, never a revoke), and separate current-month gateway usage: plan, used, allowed, plus upgrade URL and checkout path on Free at 80% or above. Only POST the checkout path when the admin asks to upgrade; reading metrics never starts checkout. Requires the project owner key or an active member key. Audit may be partial: invalid-key sampling and audit-off periods are disclosed. No upstream requests, quota use or policy changes; not a health certificate or performance guarantee. For individual calls use gate_read_audit.

NameTypeReqDescription
admin_keystringyesThe project admin key (ga_...). Read it from the .env; never print it.
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...

No output schema declared.

No examples provided.

gate_get_run_timeline ~169

What happened during this run? Returns one run's call metadata, approvals and approver names, recovery outcomes and delegated children; use it to reconstruct that session instead of gate_read_audit's project-wide calls or gate_get_run_tree's permission state. No bodies or query values. One run only; the project-wide log is gate_read_audit.

NameTypeReqDescription
admin_keystringyesThe project admin key (ga_...). Read it from the .env; never print it.
beforeinteger–Older audit events (timeline pages have at most 500 events)
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...
run_idstringyesThe run id

No output schema declared.

No examples provided.

gate_get_run_tree ~130

Which permissions and delegated descendants does this run have? Returns one run and its delegated descendants without tokens; use it to inspect delegation and permission state instead of gate_get_run_timeline events. One run only; the project-wide log is gate_read_audit.

NameTypeReqDescription
admin_keystringyesThe project admin key (ga_...). Read it from the .env; never print it.
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...
run_idstringyesThe run id

No output schema declared.

No examples provided.

gate_learn_suggestions ~148

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 learning or applies rules. This also deletes learning sessions, route templates and minute counts past their retention deadline across the project.

NameTypeReqDescription
admin_keystringyesThe project admin key (ga_...). Read it from the .env; never print it.
appstringyesThe app id
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...

No output schema declared.

No examples provided.

gate_list_actions ~162

Which actions are waiting for a human decision? Read held actions (pending by default, or another requested state) and their exact calls; this tool cannot decide or resubmit them. This also expires overdue held actions in the project and clears their stored request paths and bodies. Approving or rejecting a held action is done by a person with an approver key in the dashboard, by design. No MCP tool can approve actions.

NameTypeReqDescription
admin_keystringyesThe project admin key (ga_...). Read it from the .env; never print it.
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...
statestring–Default: pending

No output schema declared.

No examples provided.

gate_list_approvers ~143

Approvers are people who decide held actions. List active and revoked dedicated approvers with ids, names and creation times; never returns keys or hashes. Team members with the approver role are a separate list. Requires the project owner key or an active member key. Create or revoke dedicated keys and inspect team roles on the setup endpoint, /mcp/setup.

NameTypeReqDescription
admin_keystringyesThe project owner key (ga_...) or an active member key (gm_...). Never print it.
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...

No output schema declared.

No examples provided.

gate_list_apps ~109

Read the project's apps, allowed calls, limits, state, idle flags and anomaly-guard settings. Use it to select an app id. Create or revoke apps on the setup endpoint, /mcp/setup.

NameTypeReqDescription
admin_keystringyesThe project admin key (ga_...). Read it from the .env; never print it.
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...

No output schema declared.

No examples provided.

gate_read_audit ~233

Which gateway calls happened recently? Returns recent gateway calls (time, app, matched route, status, reason, duration); use it to investigate individual calls across the project rather than gate_get_metrics aggregates or a single gate_get_run_timeline. Newest first, with totals by status and refusal reason for the returned calls. This view never returns bodies, query values or headers. For 24-hour totals and anomaly scores use gate_get_metrics; for a signed export an auditor can check, gate_export_audit_proof; for one run's history, gate_get_run_timeline.

NameTypeReqDescription
admin_keystringyesThe project admin key (ga_...). Read it from the .env; never print it.
appstring–Optional: only this app id (app_...)
limitinteger–How many calls (default 20)
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...
statusstring–Optional: only this HTTP status, e.g. "403"

No output schema declared.

No examples provided.

gate_revoke_run ~140

End one run granted with gate_create_run: its token stops working at once (403 run_revoked) while the app itself keeps working. Use it to stop an agent mid-job; grant a new run with gate_create_run if the work should continue.

NameTypeReqDescription
admin_keystringyesThe project admin key (ga_...). Read it from the .env; never print it.
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...
run_idstringyesThe run id: run.run_id in gate_create_run's result

No output schema declared.

No examples provided.

gate_update_app ~238

Apply stored learning suggestions to an existing app and return the applied routes, suggested per-minute limit and learning-session metadata. Review gate_learn_suggestions first, then explicitly confirm; requires the project owner key or an admin member key. mode="extend" adds learned routes (default); "replace" removes existing routes before applying them. Both modes set the learned rate limit and keep the app key. Only learned suggestions can be applied: arbitrary routes or rate limits are not accepted, and this tool never starts learning.

NameTypeReqDescription
admin_keystringyesThe project owner key (ga_...) or an accepted admin member key (gm_...). Read it from the .env; never print it.
appstringyesThe app id (app_...) with stored learning suggestions
confirmbooleanyesExplicit confirmation to apply the reviewed learning suggestions
modestring–Extend existing routes (default), or replace them with learned routes; both set the suggested rate limit
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...

No output schema declared.

No examples provided.

gate_verify_audit_proof ~150

Is this signed audit export intact? Returns intact or broken_at for a supplied signed export; use it to check a gate_export_audit_proof export rather than retrieve audit rows. Recomputes the chain and project signature; broken_at is a one-based row position. Does not approve actions or change permissions.

NameTypeReqDescription
admin_keystringyesThe project admin key (ga_...). Read it from the .env; never print it.
project_idstringyesThe project id from project creation on the setup endpoint (/mcp/setup), e.g. p1a2b3...
proofobjectyesThe full signed export from gate_export_audit_proof

No output schema declared.

No examples provided.

Install

How do I install the Odile Gate Oversight MCP server?

Odile Gate Oversight is a hosted endpoint at https://gate.odilelabs.com/mcp/oversight, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · gate.odilelabs.com

# add to Claude Code
claude mcp add --transport http com-odilelabs-gate-oversight 'https://gate.odilelabs.com/mcp/oversight'
Common questions

What is the Odile Gate Oversight MCP server?

Odile Gate Oversight is an MCP server listed in the public MCP registry as com.odilelabs/gate-oversight. Watch Odile Gate: runs, held actions, audit log with signed export, metrics and refusal reasons. This page covers its hosted endpoint (https://gate.odilelabs.com/mcp/oversight).

Is the Odile Gate Oversight MCP server safe to use?

Odile Gate Oversight scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Odile Gate Oversight MCP server expose?

Odile Gate Oversight exposes 15 tools: gate_list_apps, gate_list_approvers, gate_create_run, gate_delegate_run, gate_revoke_run, and 10 more. Their descriptions and schemas cost roughly 2,732 tokens of context every time the server is loaded.

Does the Odile Gate Oversight MCP server require authentication?

No. We connected to Odile Gate Oversight without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Odile Gate Oversight MCP server still maintained?

Odile Gate Oversight is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Odile Gate Oversight MCP server?

VerifyMCP ran 13 checks on Odile Gate Oversight, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.