Jinko Mcp

so.jinkoPublished by jinko.soOfficial publisherv0.0.27Updated Oct 24, 2026

Jinko is a travel MCP server that provides hotel search and booking capabilities.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Jinko is a travel MCP server that lets an assistant search for hotels and handle bookings.

What you can do
Jinko is a travel-focused MCP server that provides hotel search and booking capabilities. It is offered as a remote endpoint, so an assistant connects to it over the network rather than running it locally. The registry description does not list individual tools, so the exact search and booking operations are not documented here.
When to use it
Worth considering when an assistant needs to look up hotel options or complete a hotel booking as part of a travel-planning workflow. It is less relevant if you only need general travel information without booking.
Requirements
A remote MCP endpoint at reached over streamable HTTP. No packages, environment variables, or headers are declared, and no authentication is declared in the manifest.
Before you install
Booking capability implies the assistant may make reservations or commit to purchases, which can involve payment or cancellation terms; confirm costs and policies before letting it act. The manifest declares no authentication, so check how the endpoint handles accounts and personal or payment data before use.

Installation

In SourceWeft

  1. Open Jinko Mcp in the dashboard and add it to a workspace.
  2. 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/so.jinko%2Fjinko-mcp/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.

{
  "mcpServers": {
    "jinko": {
      "type": "http",
      "url": "https://mcp-remote.jinko.so/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.0.27LatestSep 16, 2026

Score

25% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.