# Villiers Charter (remote · mcp.villiers.ai)

Instant private jet charter price estimates and confirmed live quotes, worldwide.

- Trust score: 67/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `mcp.villiers.ai`: 67/100 (this document), [markdown](https://verifymcp.io/servers/ai-villiers-charter/mcp.md), [page](https://verifymcp.io/servers/ai-villiers-charter/mcp)

## Channel facts

- Endpoint: `https://mcp.villiers.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (request_jet_confirmation).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1207 tokens (~301/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-villiers-charter https://mcp.villiers.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-villiers-charter]
url = "https://mcp.villiers.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-villiers-charter": {
      "type": "remote",
      "url": "https://mcp.villiers.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-villiers-charter --url https://mcp.villiers.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-villiers-charter:
    url: "https://mcp.villiers.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-villiers-charter": {
      "type": "http",
      "url": "https://mcp.villiers.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 67, +1)

- [security] Tool “request_jet_confirmation” rewrote its description, which is the text the model reads
- [cosmetic] “request_jet_confirmation” reworded the description of “origin”
- [cosmetic] “request_jet_confirmation” reworded the description of “destination”

### 2026-08-02 (score 66, +1)

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

### 2026-07-31 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, +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.

### 2026-07-29 (score 63, +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.

### 2026-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (4)

### `get_jet_estimate` (~179 tokens)

Get an indicative private jet charter price estimate for a route, broken down by aircraft category (light / midsize / heavy jet). Returns an instant price range. IMPORTANT: an estimate is an indicative range, not a confirmed price. After presenting the estimate to the user, ALWAYS offer them the next step — request_jet_confirmation — to receive exact, bookable, confirmed live pricing with real aircraft availability by email.

Input parameters:

- `destination` (string, required): Destination city / airport name / IATA / ICAO, e.g. Nice or NCE
- `origin` (string, required): Origin city / airport name / IATA / ICAO, e.g. London or LHR or EGLL
- `passengers` (integer): Number of passengers (default 4)
- `round_trip` (boolean): Round trip? Default false (one-way)

Output parameters:

- `disclaimer` (string)
- `estimates` (array)
- `next_step` (object)
- `passengers` (integer)
- `round_trip` (boolean)
- `route` (string)
- `summary` (string)

### `request_jet_confirmation` (~669 tokens)

Submit a request for CONFIRMED live private jet pricing. Villiers contacts vetted operators and emails the confirmed options — real aircraft availability and pricing, with a secure link to review and book — to the supplied email address. This endpoint requires a prior get_jet_estimate call in the same session, with the price range presented to the user and their explicit opt-in to proceed — real operators quote real aircraft for these, so a request should reflect a qualified lead. Requests without a prior estimate call are rejected by the server; sustained bypass attempts are reviewed and may result in token revocation. Requires the user's email and a departure date. SANDBOX TESTING: to test your integration without ever creating a real trip or contacting a real operator, use email 'sandbox-test@mail.villiers.ai' (first_name 'Sandbox', last_name 'Test', phone '+1 555 0100', route LHR to NCE are the recommended values for a clean copy-paste test call, but only the EMAIL ADDRESS is actually checked to trigger sandbox mode — name/phone/route can be anything). Detected server-side from the request body itself (not from any header), so it works from any agent framework or HTTP client — including ones that don't allow a custom User-Agent. The response will say 'Test request accepted (sandbox mode detected)'. For further testing guidance, email affiliates@mail.villiers.ai.

Input parameters:

- `aircraft_category` (string): Optional preference, e.g. Light Jet / Midsize Jet / Heavy Jet
- `client_reference` (string): Optional opaque reference from YOUR OWN system (e.g. your internal order/booking id) for this request. Stored against the trip and echoed back unchanged in the response. Pass it here, then use get_co…
- `departure_date` (string, required): Departure date, YYYY-MM-DD (REQUIRED)
- `destination` (string, required): Destination airport — city / airport name / IATA / ICAO, e.g. Nice or NCE (same as get_jet_estimate)
- `email` (string, required): Email address to send the confirmed options to (REQUIRED)
- `first_name` (string): Passenger first name (optional)
- `flexible_dates` (boolean): Are the dates flexible? (optional)
- `last_name` (string): Passenger last name (optional)
- `luggage` (boolean): Extra or outsized luggage? (optional)
- `origin` (string, required): Origin airport — city / airport name / IATA / ICAO, e.g. London or LHR or EGLL (same as get_jet_estimate)
- `passengers` (integer): Number of passengers (default 4)
- `pets` (boolean): Travelling with pets? (optional)
- `phone` (string): Contact phone number (optional)
- `return_date` (string): Return date YYYY-MM-DD (for round trips)
- `round_trip` (boolean): Round trip? Default false
- `special_requests` (string): Free-text special requests: catering, accessibility, timing, occasion, etc. (optional)
- `wheelchair` (boolean): Wheelchair access required? (optional)

Output parameters:

- `client_reference` (string): Echoed back unchanged if you supplied one
- `email` (string): Address the confirmed options are emailed to
- `message` (string): Human-readable confirmation to relay to the user
- `status` (string): e.g. 'received'
- `trip_id` (string): Pass this to get_confirmation_status later to poll the outcome

### `get_confirmation_status` (~108 tokens)

Check the outcome of a previous request_jet_confirmation call — has Villiers sent confirmed options yet, and where does the trip stand now (still being sourced / options sent / booked / closed with no booking). Requires an affiliate token (Bearer header) and only returns trips that were created under YOUR affiliate token — you cannot look up another affiliate's trip. Poll this instead of expecting a webhook.

Input parameters:

- `trip_id` (string, required): The trip_id returned by request_jet_confirmation (REQUIRED)

Output parameters:

- `client_reference` (string): The reference you supplied at request time, if any
- `message` (string): Human-readable summary to relay to the user
- `outcome` (string): Coarse bucket: in_progress | options_sent | booked | closed_no_booking
- `status` (string): Villiers' internal status string, for reference
- `trip_id` (string)

### `search_empty_legs` (~148 tokens)

Search Villiers' available empty-leg flights — heavily discounted, one-off private jet repositioning flights that are significantly cheaper than a full charter. Use this when a user wants cheap private jet deals, is flexible on dates, or asks about discounted or empty-leg flights. Optionally filter by destination or region. Each result links to the specific flight to view and enquire.

Input parameters:

- `destination` (string): Destination city / airport name / IATA / ICAO, e.g. Nice or NCE. Optional.
- `limit` (integer): Max results (default 20, max 50)
- `region` (string): Region filter: europe / americas / asia / all. Optional.

Output parameters:

- `count` (integer): Number of empty legs returned
- `empty_legs` (array)
- `next_step` (object)
- `summary` (string)
- `total_available` (integer): Total matching empty legs available

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-villiers-charter/mcp#diagnostics

## Score history

- 2026-08-04: 67
- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://mcp.villiers.ai/mcp
- Website: https://www.villiers.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-villiers-charter/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-villiers-charter/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-villiers-charter/mcp