rollinggo-hotelbooking

MCPcommunity
v1.0.0io.github.RollingGo-AIUnknownUpdated 27d agonpmGitHub

RollingGo Hotel Booking MCP Server (国内中文版)

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
25GitHub stars
27d agoLast update
Needs 1 credential before it runs
  • ROLLINGGO_API_KEYAPI keyrequired

    RollingGo Hotel API Key

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.RollingGo-AI
LicenseUnknown
Version1.0.0
Sourcenpm+mcp-registry
npmrollinggo-hotelbooking
GitHubRollingGo-AI/RollingGo-hotel-MCP-CN
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface3 tools · none privileged
Security scan✓ Cleanv1.0.0 · 26d agoHow well does this scan work?
EvalsNone
IndexedSep 16, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · none privileged
Statically extracted from the published packagev1.0.0 · 26d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

getHotelDetail查询单个酒店的实时房型和价格（包括房型、价格和税费、可用性、取消政策等）。在用户选择特定酒店后，用于二次比价和确认详情。

查询单个酒店的实时房型和价格（包括房型、价格和税费、可用性、取消政策等）。在用户选择特定酒店后，用于二次比价和确认详情。

No input schema was published for this tool.

searchHotels根据位置搜索酒店。支持城市、机场、景点、火车站、地铁站、酒店名称、区县或详细地址。返回包含基本信息和价格的匹配酒店列表。

根据位置搜索酒店。支持城市、机场、景点、火车站、地铁站、酒店名称、区县或详细地址。返回包含基本信息和价格的匹配酒店列表。

No input schema was published for this tool.

getHotelSearchTags检索酒店搜索标签元数据（AI 缓存），包括可用标签的列表。适用于在本地缓存标签后，通过解析用户意图，将结构化标签传递给 `searchHotels.hotelTags`。

检索酒店搜索标签元数据（AI 缓存），包括可用标签的列表。适用于在本地缓存标签后，通过解析用户意图，将结构化标签传递给 `searchHotels.hotelTags`。

No input schema was published for this tool.

3 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

RollingGo Hotel Booking MCP Server (国内中文版)

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

3 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-16 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

73 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+61 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.