Odile Gate
REMOTE · GATE.ODILELABS.COM
Create a free Gate project. Give each app its own API key and choose which calls it can make.
Available components
Last scanned (21 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (gate_manage_app_key). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2723 tokens (~194/item across 14 items; 14 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 15 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
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 →
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_list_actions” rewrote its description, which is the text the model reads security
- Tool “gate_list_actions” is now declared destructive security
- 19 Nov 26 +1
- “gate_create_app” added an optional parameter “runs” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 66
First indexed and scored.
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/setup
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/setup | Verified | 200 | |
| http (plaintext) | http://gate.odilelabs.com/mcp/setup | HTTPS enforced | 301 | https://gate.odilelabs.com/mcp/setup |
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 →
gate_check_setup Check an agent integration setup ~121
Read actual project protection settings and configuration gaps without changing them. Configuration analysis only: no upstream requests, runtime enforcement test or security certificate. Config-file validation and application are separate capabilities when enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | yes | The project admin key (ga_...). Read it from the .env; never print it. |
| app | string | – | Optional: check one active app id (app_...) instead of all active apps |
| project_id | string | yes | The project id from gate_create_project, e.g. p1a2b3... |
No output schema declared.
No examples provided.
gate_configure_app Configure one app setting ~270
Set models, mandatory runs, response fields, or add one confirmed literal route to an existing app. Choose exactly one operation; models:null removes the model limit, response allow:null disables filtering, and runs:off removes the run requirement. Use gate_check_setup to inspect settings; apply learned routes and rate limits on the oversight endpoint, /mcp/oversight.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | – | The project admin key (ga_...). Read it from the .env; never print it. |
| allow | – | – | Allowed JSON Pointer paths (1–32), or null to disable response filtering. |
| app | string | – | The active app id from gate_list_apps. |
| confirm | boolean | – | Explicit owner-authorized confirmation to add this exact route. |
| mode | string | – | Run requirement: off, writes, or all. |
| models | array|null | – | Exact names or prefixes ending in *; null for no limit |
| operation | string | yes | Perform exactly one operation: models, runs, response, add_route. |
| project_id | string | – | The project id from gate_create_project, e.g. p1a2b3... |
| rule | string | – | One exact rule, e.g. GET /health; no *, :param, {user} or query. |
No output schema declared.
No examples provided.
gate_create_app Register an app ~435
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 (shown once), app.id and normalized rules. Send key as Authorization: Bearer <key> to the project gateway; never send the admin key to the workload.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | yes | The project admin key (ga_...). Read it from the .env; never print it. |
| expires_at | string | – | Pro: optional future ISO time with timezone, at most 30 days from creation. Rotation preserves this expiry. |
| max_calls | integer | – | Pro: optional lifetime call allowance for this app. Rotation preserves its count. |
| models | array | – | For a model API: the only models this app may ask for, exact names or a prefix ending in * (e.g. ["gpt-4.1-mini", "claude-haiku-*"]). Omit for no model limit. |
| name | string | yes | The app name, e.g. "storefront" or "nightly sync" |
| per_minute | integer | – | Calls per minute for this app (default 60) |
| project_id | string | yes | The project id from gate_create_project, e.g. p1a2b3... |
| routes | array | – | Only the calls this app makes, one "METHOD /path" per item |
| runs | string | – | Whether calls need a Gate Actions run (x-odile-run). Default writes: the app's writes need a run. Use off for a model or MCP gateway, where every call is a POST, or for direct writes; template apps d… |
| template | string | – | Ready-made API policy: reads allowed, risky writes held, destructive calls refused. Explicit routes replace the entire template policy. Free and Pro; configure the project upstream first. See /templa… |
No output schema declared.
No examples provided.
gate_create_approver Create an approver key ~132
Approvers are people who decide held actions. Create a dedicated approver key (shown once) before granting approval actions; give it to that person, never to an agent. Only an active approver key can approve, reject or reopen actions in the dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | yes | The project admin key (ga_...). Read it from the .env; never print it. |
| name | string | yes | Who approves, e.g. "Dana (support lead)" |
| project_id | string | yes | The project id from gate_create_project, e.g. p1a2b3... |
No output schema declared.
No examples provided.
gate_create_project Create a Gate project ~199
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 (customer A holds tickets 1-3, B holds 4-5: try GET /customers/A/tickets/1). Returns project_id, admin_key (shown once) and the gateway base URL apps call instead of the API. A real API and its credentials need owner authorization.
| Name | Type | Req | Description |
|---|---|---|---|
| header_name | string | – | Optional: the secret header your API expects, e.g. Authorization or apikey |
| header_value | string | – | Optional: its value. Stored encrypted; apps never see it. |
| name | string | yes | A name for the project, e.g. "Shop API" |
| upstream | string | yes | The API base URL, https only, e.g. https://api.example.com/v1 |
No output schema declared.
No examples provided.
gate_list_actions List held actions ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | yes | The project admin key (ga_...). Read it from the .env; never print it. |
| project_id | string | yes | The project id from gate_create_project, e.g. p1a2b3... |
| state | string | – | Default: pending |
No output schema declared.
No examples provided.
gate_list_approvers List approver keys ~147
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. Use gate_create_approver to issue a key, gate_revoke_approver to revoke one, or gate_manage_members to inspect team roles.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | yes | The project owner key (ga_...) or an active member key (gm_...). Never print it. |
| project_id | string | yes | The project id from gate_create_project, e.g. p1a2b3... |
No output schema declared.
No examples provided.
gate_list_apps List apps ~103
Read the project's apps, allowed calls, limits, state, idle flags and anomaly-guard settings. Use it to select an app id. Use gate_manage_app_key to rotate its key or revoke a retired app.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | yes | The project admin key (ga_...). Read it from the .env; never print it. |
| project_id | string | yes | The project id from gate_create_project, e.g. p1a2b3... |
No output schema declared.
No examples provided.
gate_manage_app_key Rotate or revoke an app key ~154
Rotate one app key (new key shown once, old key stops immediately) or revoke the app permanently. Both operations keep other apps unchanged; revoke requires gate_create_app to restore access. Use gate_list_apps to find the app; use gate_configure_app to change its settings without replacing its key.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | – | The project admin key (ga_...). Read it from the .env; never print it. |
| app | string | – | The app id (app_...) from gate_list_apps |
| operation | string | yes | Perform exactly one operation: rotate, revoke. |
| project_id | string | – | The project id from gate_create_project, e.g. p1a2b3... |
No output schema declared.
No examples provided.
gate_manage_members Invite, list or revoke team members ~230
Members are people with project administration access according to their role. Use the project owner key to invite, list or revoke them; viewer and approver roles have narrower access than admins. Invites expire after 72 hours and their links and accepted keys are shown once; listing returns no secrets. Revocation invalidates a key or pending invite and is safe to repeat. Gate sends no email. For dedicated approval keys use gate_create_approver, gate_list_approvers and gate_revoke_approver.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | – | The project admin key (ga_...). Read it from the .env; never print it. |
| member | string | – | The member id (mem_...) from gate_manage_members with operation="list" |
| name | string | – | The person's name |
| operation | string | yes | Perform exactly one operation: invite, list, revoke. |
| project_id | string | – | The project id from gate_create_project, e.g. p1a2b3... |
| role | string | – | Invited member role: viewer, approver, or admin. |
No output schema declared.
No examples provided.
gate_revoke_approver Revoke an approver key ~156
Invalidate one dedicated approver key immediately; use gate_list_approvers to find its id. Requires the project owner key or an admin member key. A missing or already revoked id returns an error. To restore access issue a new key with gate_create_approver; to revoke a team member use gate_manage_members.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | yes | The project owner key (ga_...) or an admin member key (gm_...). Never print it. |
| approver | string | yes | The dedicated approver id from gate_list_approvers; not a member id or key. |
| project_id | string | yes | The project id from gate_create_project, e.g. p1a2b3... |
No output schema declared.
No examples provided.
gate_sync_declarative Apply an odile.yaml ~153
Apply an odile.yaml or JSON config to create missing resources and reconcile supported settings. dry_run previews steps; new keys are shown once. Never revokes or deletes; existing route or rate differences are drift, not applied. Use gate_validate_config to check a file or gate_check_setup to inspect project protection.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | – | Its admin key (ga_...), required with project_id. Read it from the .env; never print it. |
| config | string | yes | The whole odile.yaml (or the same as JSON) as text |
| dry_run | boolean | – | List the steps without changing anything |
| project_id | string | – | Optional: an existing project to sync |
No output schema declared.
No examples provided.
gate_update_project Update project alert settings ~181
Update the project rejection-alert threshold or idle-app window using its existing settings API. Omitted settings and the webhook destination stay unchanged. threshold counts rejections per app in ten minutes (5–1000); idle_days flags apps after 1–90 idle days, never revokes them. Requires the owner key or an admin member key. Returns current alert settings; does not rename or delete the project.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_key | string | yes | The project owner key (ga_...) or an admin member key (gm_...). Never print it. |
| idle_days | integer | – | Idle days before flagging an app; never revokes it. |
| project_id | string | yes | The project id from gate_create_project, e.g. p1a2b3... |
| threshold | integer | – | Rejections per app within ten minutes that trigger an alert. |
No output schema declared.
No examples provided.
gate_validate_config Check an odile.yaml ~76
Validate and normalize an odile.yaml or JSON config without reading or changing a project. Returns errors, warnings and normalized config. Use gate_check_setup for actual project settings; use gate_sync_declarative to apply the validated file.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | The whole odile.yaml (or the same as JSON) as text |
No output schema declared.
No examples provided.
How do I install the Odile Gate MCP server?
Odile Gate is a hosted endpoint at https://gate.odilelabs.com/mcp/setup, 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
claude mcp add --transport http com-odilelabs-gate 'https://gate.odilelabs.com/mcp/setup'
What is the Odile Gate MCP server?
Odile Gate is an MCP server listed in the public MCP registry as com.odilelabs/gate. Create a free Gate project. Give each app its own API key and choose which calls it can make. This page covers its hosted endpoint (https://gate.odilelabs.com/mcp/setup).
Is the Odile Gate MCP server safe to use?
Odile Gate scores 70 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 MCP server expose?
Odile Gate exposes 14 tools: gate_create_project, gate_update_project, gate_create_app, gate_list_apps, gate_manage_app_key, and 9 more. Their descriptions and schemas cost roughly 2,512 tokens of context every time the server is loaded.
Does the Odile Gate MCP server require authentication?
No. We connected to Odile Gate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Odile Gate MCP server still maintained?
Odile Gate 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 MCP server?
VerifyMCP ran 13 checks on Odile Gate, 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.