_ registry / mcp http-sse · checked 7h ago

hotel-mcp-server

https://hotel.gqmg.com

Registry code: 89df75a9946eb009

api record

Searches hotels by city and price, lists available rooms, recommends hotel routes across trip cities and records booking requests (Chinese-language).

endpoint
https://hotel.gqmg.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is hotel-mcp-server live?
Partly — its last checks failed now and then (checked 7h ago). It answered 97% of checks over the last 30 days.
Is hotel-mcp-server free to use?
Yes — the hub reached it with no key and no payment.
What tools does hotel-mcp-server have?
5 tools: update-hotel-quality, create_booking_request, recommend-hotel-route, find_hotels, search_hotel_rooms.
Is hotel-mcp-server safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
degraded
uptime, 30 days
97.4%

90 days 98.3%· all time 98.3%

latency
971ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 360 checks · signed record
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → down· HTTP 502
  • live → degraded· HTTP 502
  • degraded → live
_ what it is for
used for
  • search hotels by city and price
  • list available hotel rooms and prices
  • recommend hotel routes for a trip
  • submit a hotel booking request
takes → gives
text, data → data
tools
3 reads2 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • update-hotel-quality changes data unknown never probed

    为现有计划中某一天的酒店,更换为更高品质或更低价格的

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "toJSON": {
          "type": "boolean",
          "default": false,
          "description": "是否直接返回JSON数据,如果为false则调用generate-travel-article生成旅游计划书"
        },
        "dayIndex": {
          "type": "number",
          "default": 0,
          "description": "要更新的日期索引,从0开始"
        },
        "planType": {
          "enum": [
            "性价比优先路线",
            "舒适优质路线"
          ],
          "type": "string",
          "default": "性价比优先路线",
          "description": "要更新的路线类型"
        },
        "routeData": {
          "type": "string",
          "description": "之前生成的路线数据,JSON格式"
        },
        "preferHigherQuality": {
          "type": "boolean",
          "default": true,
          "description": "是否优先选择更高品质的酒店,false表示优先选择更低价格的酒店"
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • create_booking_request changes data unknown never probed

    当用户最终确认预订某个具体房型后,将所有预订信息记录到后台系统。

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "price": {
          "type": "number",
          "default": -1,
          "description": "确认的价格"
        },
        "hotel_name": {
          "type": "string",
          "default": "三亚海韵度假酒店",
          "description": "酒店名称"
        },
        "contact_name": {
          "type": "string",
          "default": "",
          "description": "联系人姓名"
        },
        "check_in_date": {
          "type": "string",
          "default": "2026-08-05",
          "description": "入住日期"
        },
        "contact_email": {
          "type": "string",
          "default": "",
          "description": "联系人邮箱"
        },
        "contact_phone": {
          "type": "string",
          "default": "",
          "description": "联系人电话"
        },
        "check_out_date": {
          "type": "string",
          "default": "2026-08-07",
          "description": "离店日期"
        },
        "selected_room_name": {
          "type": "string",
          "default": "行政套房",
          "description": "用户选择的具体房型名称"
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
  • recommend-hotel-route reads unknown never probed

    根据用户输入的行程途径城市,推荐两条酒店优惠路线

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "cities": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "default": [
            "广州",
            "深圳",
            "珠海"
          ],
          "description": "途径的城市列表"
        },
        "toJSON": {
          "type": "boolean",
          "default": false,
          "description": "是否直接返回JSON数据,如果为false则调用generate-travel-article生成旅游计划书"
        },
        "endDate": {
          "type": "string",
          "default": "2025-10-05",
          "description": "旅行结束日期,格式为YYYY-MM-DD"
        },
        "startDate": {
          "type": "string",
          "default": "2025-10-01",
          "description": "旅行开始日期,格式为YYYY-MM-DD"
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • find_hotels reads unknown 2d ago

    根据城市、价格区间和关键词搜索匹配的酒店列表,供用户选择。

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "所在城市名称,例如 \"北京\",如果提供,将优先从该城市中筛选"
        },
        "query": {
          "type": "string",
          "description": "用户输入的酒店名称关键词, 例如 \"香格里拉\",支持空格分隔的多关键词"
        },
        "maxPrice": {
          "type": "number",
          "description": "最高价格,单位为元"
        },
        "minPrice": {
          "type": "number",
          "description": "最低价格,单位为元"
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • search_hotel_rooms reads unknown 2d ago

    当获取到具体的酒店全名和日期后,查询该酒店的可用房型和价格。

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "hotel_name",
        "check_in_date",
        "check_out_date"
      ],
      "properties": {
        "hotel_name": {
          "type": "string",
          "description": "酒店的准确全名"
        },
        "check_in_date": {
          "type": "string",
          "description": "入住日期,格式为'YYYY-MM-DD'"
        },
        "check_out_date": {
          "type": "string",
          "description": "离店日期,格式为'YYYY-MM-DD'"
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 89df75a9946eb009.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/89df75a9946eb009/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/89df75a9946eb009/badge.svg)](https://brick.blue/agent/89df75a9946eb009?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.