io.github.DIDA-AI/hotelbooking
NPM · @DIDAAI/HOTELBOOKING · SCANNED AUG 3
Hotel Booking MCP Server
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (107 of 108), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (107 of 108), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 730 tokens (~243/item across 3 items; 3 tools + 0 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @didaai/hotelbooking
claude mcp add dida-ai-hotelbooking -- npx -y @didaai/hotelbooking
codex mcp add dida-ai-hotelbooking -- npx -y @didaai/hotelbooking
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dida-ai-hotelbooking": {
"type": "local",
"command": [
"npx",
"-y",
"@didaai/hotelbooking"
],
"enabled": true
}
}
} openclaw mcp add dida-ai-hotelbooking --command npx --arg -y --arg @didaai/hotelbooking
mcp_servers:
dida-ai-hotelbooking:
command: "npx"
args: ["-y", "@didaai/hotelbooking"] {
"mcpServers": {
"dida-ai-hotelbooking": {
"command": "npx",
"args": [
"-y",
"@didaai/hotelbooking"
]
}
}
} 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.
- 2 Aug 26 +29
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- License: unverified → fail ▼ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- 1 Aug 26 +28
- Malware scan: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −38
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 43
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@didaai/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 107 packages
107 packages in the resolved dependency tree · 107 deprecated · 32 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
getHotelDetail ~290
查询单个酒店的实时房型和价格（包括房型、价格和税费、可用性、取消政策等）。在用户选择特定酒店后，用于二次比价和确认详情。
| Name | Type | Req | Description |
|---|---|---|---|
| dateParam | object | — | 入住/退房日期对象。字段：checkInDate (字符串，YYYY-MM-DD，请尽可能传递有效的未来日期)；checkOutDate (字符串，YYYY-MM-DD，必须晚于 checkInDate)。 |
| hotelId | number | — | 酒店唯一 ID。使用此字段或 `name`；如果同时提供，则优先使用 `hotelId`（从 searchHotels 工具获取）。 |
| localeParam | object | — | 地区/货币偏好。字段：countryCode (ISO 3166-1 alpha-2，默认为 CN)；currency (ISO 4217，默认为 CNY)。 |
| name | string | — | 酒店名称（模糊匹配）。仅在未提供 `hotelId` 时使用。 |
| occupancyParam | object | — | 入住人员详情。字段：adultCount (整数，>=1，默认 2)；childCount (整数，>=0，默认 0)；childAgeDetails (儿童年龄数组，例如 [3,5])；roomCount (整数，>=1，默认 1)。 |
No output schema declared.
No examples provided.
getHotelSearchTags ~58
检索酒店搜索标签元数据（AI 缓存），包括可用标签的列表。适用于在本地缓存标签后，通过解析用户意图，将结构化标签传递给 `searchHotels.hotelTags`。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
searchHotels ~382
根据位置搜索酒店。支持城市、机场、景点、火车站、地铁站、酒店名称、区县或详细地址。返回包含基本信息和价格的匹配酒店列表。
| Name | Type | Req | Description |
|---|---|---|---|
| checkInParam | object | — | 入住参数。字段：adultCount (整数，>=1，默认 2)；checkInDate (字符串 YYYY-MM-DD，未来的日期)；stayNights (整数，1~28，默认 1)。 |
| countryCode | string | — | ISO 3166-1 alpha-2 国家/地区代码，用于货币/地区偏好。默认值为 CN（中国）。 |
| filterOptions | object | — | 酒店筛选选项，例如酒店星级、每间房成人数、距离等 |
| hotelTags | object | — | 酒店筛选标签参数（可选）。当传入此参数时，将直接使用这些标签进行筛选和排序，无需服务端额外解析。包含字段：requiredTags（必须标签）、preferredBrands（偏好品牌）、maxPricePerNight（每晚最高预算） |
| originQuery | string | yes | 综合多轮对话，归纳用户的完整住宿/预订意图。 |
| place | string | yes | 搜索目标名称。填写用户指定的城市、机场、景点、火车站、地铁站、酒店、区/县或详细地址；如果用户输入的是具体酒店名称，直接填写酒店名称 |
| placeType | string | yes | place 的类型，必须与 place 的实际内容一致。可选值：城市、机场、景点、火车站、地铁站、酒店、区/县、详细地址。 |
| size | number | — | 返回酒店结果数量，默认5个酒店，最大不超过20个 |
No output schema declared.
No examples provided.