# Jetblanc Private-Flight Brief Intake (remote · jetblanc.com)

Validate and submit authorised Asia private-flight briefs. Human-reviewed sourcing, not booking.

- Trust score: 39/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- remote · `jetblanc.com`: 39/100 (this document), [markdown](https://verifymcp.io/servers/com-jetblanc-charter-intake/api-mcp.md), [page](https://verifymcp.io/servers/com-jetblanc-charter-intake/api-mcp)

## Channel facts

- Endpoint: `https://jetblanc.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.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-10-02.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - 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**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Jetblanc Private-Flight Brief Intake MCP server?

Jetblanc Private-Flight Brief Intake is a hosted endpoint at https://jetblanc.com/api/mcp, 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.

### Claude

```bash
claude mcp add --transport http com-jetblanc-charter-intake 'https://jetblanc.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-jetblanc-charter-intake": {
      "url": "https://jetblanc.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-jetblanc-charter-intake": {
      "type": "http",
      "url": "https://jetblanc.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-jetblanc-charter-intake]
url = "https://jetblanc.com/api/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-jetblanc-charter-intake --url 'https://jetblanc.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-jetblanc-charter-intake:
    url: "https://jetblanc.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-jetblanc-charter-intake": {
      "Transport": "http",
      "Url": "https://jetblanc.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-jetblanc-charter-intake -t streamable-http -u 'https://jetblanc.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-jetblanc-charter-intake": {
      "type": "http",
      "url": "https://jetblanc.com/api/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-09-28 (score 39, 0)

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

### 2026-09-25 (score 39, 0)

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

### 2026-09-15 (score 39, −33)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Stability: 0.13 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security improvement] Authorization: partial → pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-14 (score 72, +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-09-12 (score 71, +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.

### 2026-09-11 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-10 (score 70)

First indexed and scored.

## MCP tools (4)

### `get_charter_intake_contract` (~28 tokens)

Public contract, self-service access and supported fields. Does not create a request.

### `validate_trip_brief` (~45 tokens)

Validate an explicitly approved brief without saving it or sending email.

Input parameters:

- `internalTest` (boolean)
- `request` (object, required)
- `userApproved` (boolean, required)

### `create_charter_request` (~72 tokens)

LIVE: save the authorised brief and email Jetblanc's desk. Not a flight booking. Keep one idempotencyKey for identical retries.

Input parameters:

- `idempotencyKey` (string, required)
- `internalTest` (boolean)
- `request` (object, required)
- `userApproved` (boolean, required)

### `get_request_status` (~35 tokens)

Only this key's minimal receipt; no contacts, quotes, supplier information or internal notes.

Input parameters:

- `requestId` (string, required)

## Diagnostics

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

## Score history

- 2026-10-02: 39
- 2026-10-01: 39
- 2026-09-30: 39
- 2026-09-29: 39
- 2026-09-28: 39
- 2026-09-27: 39
- 2026-09-26: 39
- 2026-09-25: 39
- 2026-09-24: 39
- 2026-09-23: 39
- 2026-09-22: 39
- 2026-09-21: 39
- 2026-09-20: 39
- 2026-09-19: 39
- 2026-09-18: 39
- 2026-09-17: 39
- 2026-09-16: 39
- 2026-09-15: 39
- 2026-09-14: 72
- 2026-09-13: 71
- 2026-09-12: 71
- 2026-09-11: 70
- 2026-09-10: 70

## Common questions

### What is the Jetblanc Private-Flight Brief Intake MCP server?

Jetblanc Private-Flight Brief Intake is an MCP server listed in the public MCP registry as com.jetblanc/charter-intake. Validate and submit authorised Asia private-flight briefs. Human-reviewed sourcing, not booking. This page covers its hosted endpoint (https://jetblanc.com/api/mcp).

### Is the Jetblanc Private-Flight Brief Intake MCP server safe to use?

Jetblanc Private-Flight Brief Intake scores 39 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 Jetblanc Private-Flight Brief Intake MCP server expose?

Jetblanc Private-Flight Brief Intake exposes 4 tools: get_charter_intake_contract, validate_trip_brief, create_charter_request, get_request_status. Their descriptions and schemas cost roughly 180 tokens of context every time the server is loaded.

### Does the Jetblanc Private-Flight Brief Intake MCP server require authentication?

Yes. Jetblanc Private-Flight Brief Intake asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Jetblanc Private-Flight Brief Intake MCP server still maintained?

Jetblanc Private-Flight Brief Intake is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://jetblanc.com/api/mcp
- Authorisation metadata: https://jetblanc.com/.well-known/oauth-protected-resource/api/mcp
- Website: https://jetblanc.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-jetblanc-charter-intake/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-jetblanc-charter-intake/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-jetblanc-charter-intake/api-mcp