Travel · Remote MCP server
Jetblanc Private-Flight Brief Intake
Validate and submit authorised Asia private-flight briefs. Human-reviewed sourcing, not booking.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.jetblanc/charter-intake- Version
- 1.1.0
- Status
- Active
- Category
- travel
- Transport
- Streamable HTTP
- Published
- 2026-09-10
- Updated
- 2026-09-10
- Publisher
- com.jetblanc
- Namespace
- Namespace verified by the MCP Registry via the domain jetblanc.com · how
- Listed under
- Flights MCP servers
- Website
- jetblanc.com/developers
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://jetblanc.com/api/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Jetblanc Private-Flight Brief Intake
Jetblanc Private-Flight Brief Intake is a remote MCP server: there is nothing to install. Its endpoint is https://jetblanc.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, jetblanc.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More travel servers
| Server | Runs |
|---|---|
| Japan RuleWatchJapan tourism entry and ecommerce evidence MCP for business agents; free tools and x402 pack. | Remote · HTTPLive check: ✓ handshake |
| Japan SeasonsLive Japan seasonal travel MCP: sakura, autumn leaves, flowers, festivals, fruit farms, weather. | Remote & Local · HTTP, stdio |
| Jenesis TravelBangkok boutique planner: live Thailand journeys, prices, FAQs, and enquiry handoff. | Remote · HTTPLive check: ✓ handshake |
| Jet TrackerBrazilian business aviation: registry, owner, flights, base, market, maintenance and sale signals. | Remote · HTTPLive check: sign-in required |
| JetopolisAirline strategy game 1950-2030: live worlds, leaders, historical airlines, aircraft prices. | Remote · HTTPLive check: ✓ handshake |
| Jinko MCPJinko is a travel MCP server that provides hotel search and booking capabilities. | Remote · HTTPLive check: ✗ no handshake |
| Journi TravelPersonal AI travel agent. Points optimization, live flight/hotel/award search, trip planning. | Remote · HTTPLive check: sign-in required |
| Jtr HolidaysSearch tours, attraction tickets, and holiday packages across 24 countries. | Remote · HTTPLive check: ✓ handshake |