Connect Jetblanc Private-Flight Brief Intake and your agent gets 4 tools, among them create_charter_request, get_charter_intake_contract, get_request_status. It answers at https://jetblanc.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Validate and submit authorised Asia private-flight briefs. Human-reviewed sourcing, not booking.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
create_charter_request | LIVE: save the authorised brief and email Jetblanc's desk. Not a flight booking. Keep one idempotencyKey for identical retries. Inputs: request, userApproved, internalTest, idempotencyKey |
get_charter_intake_contract | Public contract, self-service access and supported fields. Does not create a request. |
get_request_status | Only this key's minimal receipt; no contacts, quotes, supplier information or internal notes. Inputs: requestId |
validate_trip_brief | Validate an explicitly approved brief without saving it or sending email. Inputs: request, userApproved, internalTest |
Every block below points at https://jetblanc.com/api/mcp. Pick your client and copy.
claude mcp add --transport http jetblanc-private-flight-brief-in https://jetblanc.com/api/mcp
{
"mcpServers": {
"jetblanc-private-flight-brief-in": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://jetblanc.com/api/mcp"]
}
}
}{
"mcpServers": {
"jetblanc-private-flight-brief-in": {
"url": "https://jetblanc.com/api/mcp"
}
}
}{
"servers": {
"jetblanc-private-flight-brief-in": {
"type": "http",
"url": "https://jetblanc.com/api/mcp"
}
}
}{
"context_servers": {
"jetblanc-private-flight-brief-in": {
"url": "https://jetblanc.com/api/mcp"
}
}
}{
"mcpServers": {
"jetblanc-private-flight-brief-in": {
"serverUrl": "https://jetblanc.com/api/mcp"
}
}
}{
"mcpServers": {
"jetblanc-private-flight-brief-in": {
"url": "https://jetblanc.com/api/mcp"
}
}
}name: Jetblanc Private-Flight Brief Intake
version: 0.0.1
schema: v1
mcpServers:
- name: Jetblanc Private-Flight Brief Intake
type: streamable-http
url: https://jetblanc.com/api/mcp{
"mcpServers": {
"jetblanc-private-flight-brief-in": {
"httpUrl": "https://jetblanc.com/api/mcp"
}
}
}{
"mcpServers": {
"jetblanc-private-flight-brief-in": {
"type": "http",
"url": "https://jetblanc.com/api/mcp"
}
}
}{
"mcpServers": {
"jetblanc-private-flight-brief-in": {
"url": "https://jetblanc.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fjetblanc.com%2Fapi%2Fmcp&type=streamable_http&id=jetblanc-private-flight-brief-in&name=Jetblanc%20Private-Flight%20Brief%20Intake
It answered our last check on 19 October 2026 in 319 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by jetblanc.com and served from jetblanc.com, the vendor's own domain: https://jetblanc.com/api/mcp.
4, as returned by the server's own tools/list on 10 September 2026: create_charter_request, get_charter_intake_contract, get_request_status, validate_trip_brief.
It answered our last check on 19 October 2026 in 319 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://jetblanc.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.jetblanc. Endpoint host: jetblanc.com. ARD identifier: urn:air:com.jetblanc:mcp:charter-intake.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.