Jinko MCP
REMOTE · MCP.GOJINKO.COM · SCANNED SEP 28
Turn your ChatGPT to a super travel agent
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (trip). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability38
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- Instruction-quality not yet verified: the AI judgement didn't run.Unverified
- Context-footprint check failed: tool/resource definitions use about 17084 tokens (~1220/item across 14 items; 7 tools + 7 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety25
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "never tell the user", at byte 1035 of that field, plus 3 further marker(s) of the same kind. See how to fix → Fail
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- Manipulation not yet verified: only 6 of 9 captured unit(s) of tool text has been judged so far, so we will not certify text no model has read as clean.Unverified
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the Jinko MCP server?
Jinko MCP is a hosted endpoint at https://mcp.gojinko.com/, 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.
remote · mcp.gojinko.com
claude mcp add --transport http com-gojinko-mcp-jinko 'https://mcp.gojinko.com/'
{
"mcpServers": {
"com-gojinko-mcp-jinko": {
"url": "https://mcp.gojinko.com/"
}
}
} {
"servers": {
"com-gojinko-mcp-jinko": {
"type": "http",
"url": "https://mcp.gojinko.com/"
}
}
} [mcp_servers.com-gojinko-mcp-jinko] url = "https://mcp.gojinko.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-gojinko-mcp-jinko": {
"type": "remote",
"url": "https://mcp.gojinko.com/",
"enabled": true
}
}
} openclaw mcp add com-gojinko-mcp-jinko --url 'https://mcp.gojinko.com/' --transport streamable-http
mcp_servers:
com-gojinko-mcp-jinko:
url: "https://mcp.gojinko.com/" {
"McpServers": {
"com-gojinko-mcp-jinko": {
"Transport": "http",
"Url": "https://mcp.gojinko.com/"
}
}
} assistant mcp add com-gojinko-mcp-jinko -t streamable-http -u 'https://mcp.gojinko.com/'
{
"mcpServers": {
"com-gojinko-mcp-jinko": {
"type": "http",
"url": "https://mcp.gojinko.com/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Tool “hotel_search” rewrote its description, which is the text the model reads security
- Server version: 1.25.0 → 1.25.3 functional
- “hotel_details” reworded the description of “checkin” cosmetic
- “hotel_details” reworded the description of “checkout” cosmetic
- “hotel_search” reworded the description of “destination” cosmetic
- “hotel_search” reworded the description of “rooms” cosmetic
- “hotel_search” reworded the description of “trip_id” cosmetic
- “trip” reworded the description of “schedule_quote” cosmetic
- 26 Sept 26 0
- Server version: 1.24.1 → 1.25.0 functional
- 25 Sept 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Tool “flight_search” rewrote its description, which is the text the model reads security
- Server version: 1.23.1 → 1.24.0 functional
- “find_destination” reworded the description of “max_price” cosmetic
- “flight_calendar” reworded the description of “max_price” cosmetic
- 23 Sept 26 0
- Tool “flight_search” rewrote its description, which is the text the model reads security
- Tool “hotel_search” rewrote its description, which is the text the model reads security
- Server version: 1.22.1 → 1.23.1 functional
- “flight_search” reworded the description of “price_check” cosmetic
- 19 Sept 26 −3
- Injection markers: pass → fail ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “book” rewrote its description, which is the text the model reads security
- Tool “flight_search” rewrote its description, which is the text the model reads security
- Tool “hotel_search” rewrote its description, which is the text the model reads security
- Tool “trip” rewrote its description, which is the text the model reads security
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.22.1 functional
- 9 Sept 26 +1
No change was recorded against any check on this day. Schema Quality & AI Usability went from 67 to 69.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://mcp.gojinko.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.gojinko.com | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 909aa8bbbbf0dccf0ebfe20ee924f445 |
| SANs: mcp.gojinko.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.gojinko.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gojinko.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.gojinko.com | Verified | 200 | |
| sse | https://mcp.gojinko.com | Verified | 200 | |
| http (plaintext) | http://mcp.gojinko.com | HTTPS enforced | 301 | https://mcp.gojinko.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
book ~1,175
Unified tool for booking a trip. Actions are determined by which object you provide. SCHEMA: { create?: { // Initiate booking trip_id: string, // Required: ID of the trip to book buyer_contact?: { // Optional: buyer contact info email: string, phone?: string } }, status?: { // Check booking status booking_id: string // Required: ID of the booking to check }, idempotency_key?: string // Prevent duplicate processing } ACTIONS: 1. CREATE BOOKING (create object): Quotes the trip and returns a Stripe Checkout URL for payment authorization. { "create": { "trip_id": "trip_xxx" } } Returns: { "checkout_session": { "id": "cs_xxx", "url": "https://checkout.stripe.com/...", // Open this URL for payment "expires_at": "2026-01-08T15:30:00Z" // quote deadline — payment is refused past it, not re-priced. Not a price hold. Absent if the quote names none }, "pending_booking": { "id": "bkg_xxx", "status": "awaiting_payment", "trip_id": "trip_xxx" } } 2. CHECK STATUS (status object): Retrieves booking status. If payment is authorized but fulfillment hasn't started, automatically triggers fulfillment. { "status": { "booking_id": "bkg_xxx" } } Returns: Full booking object with status, items, passengers, totals, payment info. PREREQUISITES: • Trip must have at least one item (use trip tool with add_item) • Trip must have travelers assigned (use trip tool with upsert_travelers) • Trip must pass validation WORKFLOW (flights): 1. flight_calendar → offer_token 2. flight_search → trip_item_token 3. trip(add_item) → trip created 4. trip(upsert_travelers) → travelers set 5. book(create={trip_id}) → checkout URL WORKFLOW (hotels): 1. hotel_search → htl_* offer_id 2. trip(add_item, trip_item_token=htl_*) → trip created 3. trip(upsert_travelers) → travelers set 4. book(create={trip_id}) → checkout URL Flights and hot…
| Name | Type | Req | Description |
|---|---|---|---|
| create | object | – | Initiate booking for a trip. Quotes the trip and returns a Stripe Checkout URL for payment. Mutually exclusive with `status` — provide exactly one action per call. |
| idempotency_key | string | – | Idempotency key to prevent duplicate processing |
| status | object | – | Check the status of an existing booking. If payment is authorized, triggers fulfillment automatically. Mutually exclusive with `create` — provide exactly one action per call. |
| user_intent | string | – | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| booking | – | – | – |
| checkout_session | – | – | – |
| error_code | string | – | – |
| error_message | string | – | – |
| hint | string | – | – |
| pending_booking | – | – | – |
| quoted_offer | – | – | – |
| status | string | – | – |
| trip | – | – | – |
No examples provided.
find_destination ~2,347
Discover travel destinations when the user does NOT know where to go. This is a destination EXPLORATION tool. WHEN TO USE THIS TOOL (CRITICAL): - The user does NOT specify a destination: "Where should I go?", "Best deals from NYC" - The user wants inspiration based on criteria: "Beach destinations", "Somewhere warm", "Cheap flights from SF" - The user wants to compare multiple destination options from their origin - The user previously asked for destination recommendations and wants pricing for those options WHEN NOT TO USE THIS TOOL — USE flight_calendar INSTEAD: - The user specifies BOTH an origin AND a destination → use flight_calendar - Examples that should use flight_calendar, NOT this tool: • "Flights from Paris to Barcelona" → flight_calendar • "Find me a flight from JFK to CDG" → flight_calendar • "Cheapest flight from LA to Miami in June" → flight_calendar • "Paris to BCN for a weekend in April" → flight_calendar • "What are the cheapest dates to go to NYC from Paris?" → flight_calendar - If the user names a specific city/airport as destination, that means they KNOW where to go → flight_calendar IMPORTANT - DATES: All dates in query parameters (departure_dates, departure_date_ranges, return_dates, return_date_ranges) MUST be in the future. Never use past dates. Please fill as much as possible search parameters based on user intent to get best results. IMPORTANT - RE-CALL THIS TOOL when the user: - Asks for a different type of destination (beach, city trip, ski, etc.) - Asks for different dates while still exploring - The user is already in fullscreen mode in the widget CORE FUNCTIONALITY: - REQUIRED: User's origin location (LLM identifies ALL nearby airports) - OPTIONAL: Destination filtering by specific airports/cities OR omit for global discovery mode - Destination Discovery Mode: When destinations is omitted/empty, searches ALL destinations globally - Flexible dates and stay durations for exploring options - Filter by budget, direct f…
| Name | Type | Req | Description |
|---|---|---|---|
| cabin_class | string | – | Preferred cabin class. Options: "economy", "premium_economy", "business", or "first". Filters results accordingly. |
| currency | string | – | ISO 4217 currency code for displaying prices (e.g. "EUR", "USD", "GBP"). Infer from the user's country or locale. If the user mentions a specific currency, use that. |
| departure_date_ranges | array | – | List of departure date ranges for flexible travel discovery. Use when the user mentions periods like “next month” or “spring.” Supports multiple non-contiguous ranges (OR logic). Example: [{start: "2… |
| departure_dates | array | – | List of specific departure dates in ISO 8601 format (YYYY-MM-DD). Use for searching multiple specific dates with OR logic. Example: ["2025-12-15", "2025-12-16", "2025-12-17"] for flexible date search… |
| destinations | array | – | OPTIONAL. Array of destination IATA codes (3-letter uppercase), representing either airports or cities. When a city code is provided, the LLM MUST expand it to include all associated airports. Exampl… |
| direct_only | boolean | – | When true, only returns nonstop (direct) flights. Useful for avoiding layovers or minimizing total travel time. |
| locale | string | – | User's BCP 47 locale inferred from the conversation (e.g. "fr-FR", "en-US", "ja-JP"). Used for formatting dates, numbers, and selecting currency. Infer from the user's language and location context. |
| max_price | number | – | Maximum price PER PERSON: the cap applies to a one-adult fare, in the requested currency. For a whole-party budget, divide it by the number of ADULTS only and treat the result as a loose pre-filter:… |
| origins | array | yes | REQUIRED. Array of origin IATA codes (3-letter uppercase), representing either airports or cities where the trip starts. The LLM MUST detect and include all relevant nearby airports or city codes bas… |
| return_date_ranges | array | – | List of return date ranges for flexible round-trip searches. Supports multiple return windows. Example: [{start: "2025-12-22", end: "2025-12-25"}, {start: "2025-12-29", end: "2026-01-02"}]. |
| return_dates | array | – | List of specific return dates for round-trip searches (YYYY-MM-DD). Must be after the corresponding departure dates. Supports multiple options (OR logic). Example: ["2025-12-22", "2025-12-23", "2025-… |
| sort_by | string | – | Sorting preference for search results. Options: "lowest" (cheapest first, default) or "recommendation" (best overall balance of price, duration, and stops). |
| stay_days | integer | – | Exact number of days to stay at the destination. Used with a departure date to automatically compute the return date. Example: 7 = one-week trip; 3 = weekend getaway. |
| stay_days_range | object | – | Range of acceptable trip durations for flexible planning (e.g., “5 to 10 days”). Cannot be combined with stay_days or explicit return_date. Example: {min: 5, max: 10}. |
| trip_type | string | yes | REQUIRED. Type of trip: "oneway" for single-leg flights, or "roundtrip" for return flights. |
| user_intent | string | – | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… |
| Name | Type | Req | Description |
|---|---|---|---|
| availableAirlines | array | – | – |
| destinations | array | – | – |
| emissionsInfo | object | – | – |
| error_message | string | – | – |
| hasMore | boolean | – | – |
| origins | – | – | – |
| priceRange | object | – | – |
| searchQuery | object | – | – |
| status | string | – | – |
| totalDestinations | number | – | – |
| totalFlights | number | – | – |
No examples provided.
flight_calendar ~2,262
Search flights between a known origin and destination using cached pricing. Use this tool whenever the user specifies BOTH where they are flying FROM and where they are flying TO. WHEN TO USE THIS TOOL (CRITICAL): - The user provides both an origin AND a destination (city or airport) - Examples: "Paris to Barcelona", "JFK to CDG", "London to NYC for a weekend" - Supports loose / flexible dates: single dates, date arrays, date ranges, stay_days - ALSO the right tool for "cheapest flight", "best flight", "find me a flight", "cheapest date" phrasings — this tool returns the cheapest cached itineraries for the given route and window. WHEN TO USE find_destination INSTEAD: - The user does NOT specify a destination: "Where should I go from Paris?", "Best deals from NYC" - The user wants inspiration: "Beach destinations from London", "Cheap flights from SF" WHEN TO USE flight_search INSTEAD: - The user has committed to EXACT dates — both a single departure date AND a single return date for one specific route. - Example: "Paris → NYC, June 17 → June 26" - flight_search hits live pricing (each call has a cost) and is the step immediately before booking. Use it only once route + both dates are locked in. - **TRIP-CONTEXT DATES COUNT AS EXACT.** If a trip is already in context with a HOTEL, the hotel's check-in and check-out ARE the exact departure/return dates the user wants — even if they don't restate the dates in the message. In that case use flight_search (not flight_calendar) with the hotel's check-in as departure_date and check-out as return_date. Examples: cart has hotel May 8 → May 10 in Madrid; user says "add a flight from Paris" → flight_search with PAR→MAD, dep=2026-05-08, ret=2026-05-10. The trip cross-sell hint confirms this — when it points you at flight_search, follow it. IMPORTANT: All dates in query parameters (departure_dates, departure_date_ranges, return_dates, return_date_ranges) MUST be in the future. Never use past dates. Please fill as much as…
| Name | Type | Req | Description |
|---|---|---|---|
| arrival_time_range | object | – | Filter the OUTBOUND leg by local arrival time-of-day. Example: { "latest": "20:00" } to arrive by 8pm. Use when the user says "arrive before dinner", "land by noon", etc. |
| cabin_class | string | – | Cabin class preference. Options: "economy" (standard economy), "premium_economy" (enhanced economy with more space/amenities), "business" (business class), "first" (first class). When specified, only… |
| currency | string | – | ISO 4217 currency code for displaying prices (e.g. "EUR", "USD", "GBP"). Infer from the user's country or locale. If the user mentions a specific currency, use that. |
| departure_date_ranges | array | – | List of departure date ranges for flexible travel exploration. Use when user says "next month", "spring", or wants to discover deals across multiple date periods with OR logic. Example: [{start: "202… |
| departure_dates | array | – | List of specific departure dates in ISO 8601 format (YYYY-MM-DD). Use for searching multiple specific dates with OR logic. Example: ["2025-12-15", "2025-12-16", "2025-12-17"] for flexible date search… |
| departure_time_range | object | – | Filter the OUTBOUND leg by local departure time-of-day. Example: { "earliest": "08:00", "latest": "12:00" } for a late-morning departure. Use when the user says "morning flight", "leave after 6pm", e… |
| destination | string | yes | REQUIRED: Single origin airport IATA code or IATA City Code. Example for IATA airport code : "LGW" for Gatwick in London, "SFO" for San Francisco. Example for IATA city code : "LHR" for London, "BJS"… |
| direct_only | boolean | – | Only show direct/nonstop flights. When true, only flights with no stops are returned. Use for fastest travel or when layovers are not desired. |
| locale | string | – | User's BCP 47 locale inferred from the conversation (e.g. "fr-FR", "en-US", "ja-JP"). Used for formatting dates, numbers, and selecting currency. Infer from the user's language and location context. |
| max_price | number | – | Maximum price PER PERSON: the cap applies to a one-adult fare, in the requested currency. For a whole-party budget, divide it by the number of ADULTS only and treat the result as a loose pre-filter:… |
| origin | string | yes | REQUIRED: Single origin airport IATA code or IATA City Code. Example for IATA airport code : "JFK" for John F.Kennedy in New York, "LAX" for Los Angeles. Example for IATA city code : "NYC" for New Yo… |
| return_arrival_time_range | object | – | Round-trip only. Filter the RETURN leg by local arrival time-of-day. |
| return_date_ranges | array | – | List of return date ranges for flexible round-trip exploration. Use when user wants flexibility on return timing across multiple periods with OR logic. Example: [{start: "2025-12-22", end: "2025-12-2… |
| return_dates | array | – | List of specific return dates for round-trip flights (YYYY-MM-DD). Use for searching multiple return date options with OR logic. Must be after departure dates. Example: ["2025-12-22", "2025-12-23", "… |
| return_departure_time_range | object | – | Round-trip only. Filter the RETURN leg by local departure time-of-day. |
| sort_by | string | – | Sort results by this criteria. Default: lowest (best deals first). Options: lowest (cheapest flights), recommendation (best overall value considering price, duration, and stops). |
| stay_days | integer | – | Exact number of days to stay at destination. Used with departure_date to calculate return date automatically. Example: 7 for a week-long trip, 3 for a weekend getaway. |
| stay_days_range | object | – | Flexible stay duration range. Use when user wants flexibility in trip length (e.g., "5 to 10 days"). Cannot be combined with exact stay_days or return_date. Example: {min: 5, max: 10} |
| trip_type | string | yes | REQUIRED: Trip type: "oneway" for one-way flights or "roundtrip" for round-trip flights. |
| user_intent | string | – | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… |
| Name | Type | Req | Description |
|---|---|---|---|
| availableAirlines | array | – | – |
| destination | object | – | – |
| emissionsInfo | object | – | – |
| error_message | string | – | – |
| flights | array | – | – |
| hasMore | boolean | – | – |
| priceRange | object | – | – |
| searchQuery | object | – | – |
| status | string | – | – |
| totalFlights | number | – | – |
No examples provided.
flight_search ~3,643
Live flight tool with two modes. EACH CALL HITS LIVE PRICING — it prices ONE exact date pair, so any loose, open or flexible date query belongs to flight_calendar instead. MODE 1 — search: route + exact single dates + optional filters (most common first-call case) - Use when the user has committed to ONE specific route AND a specific departure date. For roundtrip, also provide a return_date; for one-way, OMIT return_date entirely (do NOT set it equal to departure_date — that books a same-day return). - Supports the full shop filter set on the same call: trip_type, max_stops, cabin_class, max_price (whole-trip budget for all passengers), limit, include_carriers / exclude_carriers, single_carrier_only, departure/arrival (and return_*) time ranges, connection_time_min/max_minutes, max_total_duration_minutes, refundable_only, changeable_only, checked_bag_included, via_airports / exclude_via_airports, aircraft_types, origin_alternate_airports / destination_alternate_airports, nearby_airports, same_connection/origin/turnaround_airport_only, origin_type, destination_type. - **Trip-context dates count as exact.** If the cart already has a HOTEL, the hotel's check-in/check-out ARE the precise departure/return dates — even if the user doesn't restate them in their message. Use those as departure_date and return_date and call this tool (not flight_calendar). Forward the trip_id on the call. - Examples: ✓ "Paris to NYC, June 1 to June 10" → { search: { origin: "PAR", destination: "NYC", departure_date: "2027-06-01", return_date: "2027-06-10" } } ✓ "Paris to Rome June 19 to 27, direct only, business class" → { search: { origin: "PAR", destination: "ROM", departure_date: "2026-06-19", return_date: "2026-06-27", max_stops: 0, cabin_class: "business" } } ✓ "JFK → CDG August 5 to 12, Air France only, under $800" → { search: { origin: "JFK", origin_type: "airport", destination: "CDG", destination_type: "airport", departure_date: "2026-08-05", return_date: "2026-08-12", includ…
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO 4217 currency code for displaying prices (e.g. "EUR", "USD", "GBP", "JPY"). ALWAYS set this — omitting it falls back to USD which is rarely what users actually want. Infer from the strongest sign… |
| locale | string | – | User's BCP 47 locale inferred from the conversation (e.g. "fr-FR", "en-US", "ja-JP"). Used for formatting dates, numbers, and selecting currency. |
| price_check | object | – | Get confirmed live fares for a specific flight offer. Returns fare brands with trip_item_token for booking. The BFF treats offer_token and the filter fields (direct_only, cabin_class, max_price, incl… |
| search | object | – | Live search for a committed itinerary with optional filters. Use it when the user has settled on a route and precise dates: origin + destination + departure_date (+ return_date for a round trip). No… |
| traveler_counts | object | – | Traveler counts. Defaults to 1 adult. |
| trip_id | string | – | Existing trip_id to associate this search with. Forward whenever the user is mid-trip-build (you have seen a trip_id in a recent trip(...) tool result and the user has NOT pivoted to a different trip… |
| user_intent | string | – | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… |
| Name | Type | Req | Description |
|---|---|---|---|
| applied_filters | array | – | – |
| details | array | – | – |
| error_code | string | – | – |
| error_message | string | – | – |
| filter_enforcement | array | – | – |
| flights | array | – | – |
| hasMore | boolean | – | – |
| hint | string | – | – |
| include_carriers_widened | boolean | – | – |
| priceRange | object | – | – |
| quoted_offer | – | – | – |
| searchQuery | object | – | – |
| status | string | – | – |
| totalFlights | number | – | – |
| unapplied_filters | array | – | – |
No examples provided.
hotel_details ~526
Rich metadata (gallery, facilities, policies, per-room details) for a single hotel — called by the hotel widget on fullscreen open. **Cost: 1 credit per call.**
| Name | Type | Req | Description |
|---|---|---|---|
| checkin | string | – | Check-in date (YYYY-MM-DD). Accepted for future cache-key alignment; currently unused by the platform. |
| checkout | string | – | Check-out date (YYYY-MM-DD). Accepted for future cache-key alignment; currently unused by the platform. |
| hotel_id | string | yes | Hotel ID (from a prior hotel_search offer). |
| user_intent | string | – | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| status | string | – | – |
No examples provided.
hotel_search ~3,784
Search live hotel inventory and rates worldwide. REQUIRED: - destination: object — two distinct modes. Mode A (rate lookup): { hotel_name (+ optional country_code, city_name) } or { hotel_ids }. Mode B (hotel search): { query }, { city_name + country_code }, { latitude + longitude (+ radius_km) }, or { place_id }. - checkin, checkout: YYYY-MM-DD - occupancy: either occupancies[] (one entry per room) OR shorthand { adults, children?, rooms? } TWO MODES — pick deliberately: MODE A (rate lookup — the user named a specific hotel): - { hotel_name }: free-text hotel name ("Hotel Calimala", "The St. Regis Rome", "Hôtel Costes"). Server fuzzy-matches against a 1.74M-hotel catalog. ALWAYS pair with country_code AND city_name when known — lookup precision drops sharply on common names without scope. Returns 422 HOTEL_NAME_LOW_CONFIDENCE if no candidate scores ≥ 0.7; see "ERROR HANDLING" below. - { hotel_ids }: re-shop a known set (from a prior search result). In Mode A: property filters and max_results are ignored (user named the property), but filters.max_budget_per_night still applies. The response includes nearby_alternatives — up to 40 hotels within ~3km of the matched property in the same response shape so the user can compare. MODE B (hotel search — the user is exploring a destination): - { query }: unambiguous cities or well-known POIs only ("Paris", "Times Square"). Provider AI search returns 0 for islands ("Menorca", "Santorini", "Mykonos"), regions ("Tuscany", "Provence", "Bavaria"), countries, archipelagos. Do NOT use { query } for those. - { city_name + country_code }: when the user named a city, even if ambiguous. Best when the destination has a primary city ("Mahón, ES" for Menorca; "Florence, IT" for Tuscany). Spell the city as an English-language booking site would — "Munich"/"Florence"/"Rome"/"Vienna", NOT "München"/"Firenze"/"Roma"/"Wien" — but keep the local form where that IS the international one ("Regensburg", "Nürnberg", "Lyon"), and never an archa…
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Shorthand: total adults across all rooms. Use ONLY when there is no ambiguity (1 or 2 adults = single room). For 3+ adults, or odd splits, ask the user how they want to split rooms and pass occupanci… |
| checkin | string | yes | Check-in date (YYYY-MM-DD). |
| checkout | string | yes | Check-out date (YYYY-MM-DD). |
| children | array | – | Shorthand: ages of all children across all rooms. If children are present, prefer occupancies[] so the caller controls which room each child goes in (ages affect pricing and some providers reject inv… |
| currency | string | – | ISO 4217 currency code (e.g. "EUR", "USD", "GBP", "JPY"). ALWAYS set this — omitting it falls back to USD which is rarely what users actually want. Infer from the strongest signal available: (1) the… |
| destination | object | yes | Destination — provide exactly one shape. Two distinct modes: MODE A (rate lookup — you know which hotel): • { hotel_ids } to re-shop a known set. • { hotel_name, country_code?, city_name? } when… |
| filters | object | – | Optional filter overrides applied on top of the tenant default filter set. |
| guest_nationality | string | – | Guest nationality (ISO 3166-1 alpha-2, uppercase, e.g. "FR"). Affects rate availability + tax handling at search time. Separate from traveler nationality used for booking documents. |
| occupancies | array | – | One entry per room (structured). PREFERRED whenever the party is larger than 2 adults or has children — it removes ambiguity about how guests are split across rooms. Example: [{ "adults": 2 }, { "adu… |
| rooms | integer | – | Shorthand: number of rooms (the platform auto-distributes adults + children). Use when the user named a room count but not the per-room split. |
| trip_id | string | – | Existing trip_id to associate this search with. Used only by the Jinko cart widget. The platform accepts the field for schema consistency but ignores it on surfaces without the widget. Forward whenev… |
| user_intent | string | – | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| error_message | string | – | – |
| hasMore | boolean | – | – |
| hint | string | – | – |
| hotels | array | – | – |
| searchQuery | – | – | – |
| status | string | – | – |
| totalHotels | number | – | Number of hotels in THIS response page (after max_results trimming, excluding nearby alternatives) — NOT the total number of matches. Upstream window info arrives in the BFF pagination block when pre… |
| trip_id | string | – | – |
No examples provided.
trip ~2,984
Unified tool for managing a trip (shopping cart). Supports flights and hotels in the same cart. Actions are determined by which objects you provide. SCHEMA: { trip_id?: string, // Existing trip ID (omit to create new) offer_id?: string, // (Legacy) Offer ID — now auto-encoded into trip_item_token by flight_search add_item?: { ... }, // Add a flight or hotel to the trip remove_item?: { ... }, // Remove an item from the trip upsert_travelers?: { ... }, // Set travelers (replaces all) idempotency_key?: string // Prevent duplicate processing } ACTIONS: 1. ADD ITEM (add_item object): - Flight: trip_item_token from flight_search (offer__* format, contains encoded offer_id) - Hotel: offer_id from hotel_search (htl_* format, use directly as trip_item_token) { "add_item": { "trip_item_token": "offer__1:0-2-0", // Flight token from flight_search // OR: "htl_abc123..." // Hotel token from hotel_search "traveler_ids": ["traveler_1", "traveler_2"] // Optional: associate travelers } } MULTI-ROOM HOTEL (rooms array — one booking, one reference): When the user wants MULTIPLE ROOMS for ONE hotel stay (same hotel, same check-in/check-out), make ONE add_item call with the rooms array — do NOT add the same hotel twice as separate items when the user wants one reservation. Each entry carries that room's htl_* rate token from hotel_search (e.g. one rate per requested occupancy). 2–8 rooms; for a single room use trip_item_token instead. rooms and trip_item_token are mutually exclusive. Hotel tokens only; currently supported for HotelBeds-inventory tenants only. { "add_item": { "rooms": [ { "trip_item_token": "htl_rate_room1", "traveler_ids": ["traveler_1", "traveler_2"] }, { "trip_item_token": "htl_rate_room2", "traveler_ids": ["traveler_3"] } ] } } 2. REMOVE ITEM (remove_item object): { "trip_id": "trip_xxx", "remove_item": { "item_id": "item_123" // From trip.tri…
| Name | Type | Req | Description |
|---|---|---|---|
| add_item | object | – | Add a flight or hotel to the trip. Use trip_item_token from flight_search (offer__* format) or offer_id from hotel_search (htl_* format). For MULTIPLE ROOMS of the same hotel stay, make ONE add_item… |
| idempotency_key | string | – | Idempotency key to prevent duplicate processing |
| offer_id | string | – | Deprecated: offer_id is now encoded into trip_item_token by flight_search. Only needed for legacy tokens without encoded offer_id. |
| payment_type | string | – | Payment flow type: "checkout" for Stripe Checkout (default), "intent" for Payment Intent. |
| remove_item | object | – | Remove an item from the trip by its ID. |
| schedule_quote | boolean | – | Schedule a fresh quote on the current cart state. Triggers async re-pricing on the BFF; poll trip(get) until trip.quote_status is "completed", "partial", or "failed". Only "completed" covers the whol… |
| select_ancillaries | object | – | Select ancillaries (bags, seats, meals) for a quoted trip item. Uses full-replacement semantics — send all desired selections. |
| trip_id | string | – | ID of an existing trip. If not provided, a new trip will be created. |
| upsert_travelers | object | – | Set travelers on the trip. Replaces all existing travelers (idempotent operation). |
| user_intent | string | – | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… |
| Name | Type | Req | Description |
|---|---|---|---|
| actions_performed | array | – | – |
| error_code | string | – | – |
| error_message | string | – | – |
| hint | string | – | – |
| recommended_products | array | – | – |
| saved_travelers | array | – | – |
| status | string | – | – |
| trip | – | – | – |
| trip_item_id | string | – | – |
No examples provided.
What is the Jinko MCP server?
Jinko MCP is listed in the public MCP registry as com.gojinko.mcp/jinko. Turn your ChatGPT to a super travel agent. This page covers its hosted endpoint (https://mcp.gojinko.com).
Is the Jinko MCP server safe to use?
Jinko MCP scores 70 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 Jinko MCP server expose?
Jinko MCP exposes 7 tools: flight_calendar, find_destination, flight_search, hotel_search, hotel_details, and 2 more. Their descriptions and schemas cost roughly 16,721 tokens of context every time the server is loaded.
Does the Jinko MCP server require authentication?
No. We connected to Jinko MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Jinko MCP server still maintained?
Jinko MCP is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.