Jetblanc Private-Flight Brief Intake

com.jetblancPublished by jetblanc.comOfficial publisherv1.1.0Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP endpoint for validating and submitting authorised Asia private-flight briefs, with human-reviewed sourcing rather than booking.

What you can do
  • Validate private-flight briefs for Asia itineraries before submission.
  • Submit authorised briefs to Jetblanc for human-reviewed sourcing.
  • No tool list is published, so the exact operations are not documented; the server is described only as intake for briefs, not booking.
When to use it
When an assistant needs to prepare, check or hand off a private-flight request for Asia to a human sourcing team, and the user already holds Jetblanc developer access.
Requirements
A remote streamable HTTP endpoint at jetblanc.com; no local install. OAuth authentication is required, with a private bearer key supplied in the Authorization header, obtained from the provider's developer access page.
Before you install
A private bearer key is required and must be kept secret. Submitting a brief sends itinerary and traveller details to a third party, Jetblanc. The service handles sourcing requests only, not confirmed bookings, so nothing should be treated as a reservation.

Installation

In SourceWeft

  1. Open Jetblanc Private-Flight Brief Intake in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.jetblanc%2Fcharter-intake/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "jetblanc-private-flight-brief-intake": {
      "type": "http",
      "url": "https://jetblanc.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.