_ registry / mcp streamable-http

hotelshortlist

https://hotelshortlist.com

Registry code: 410345a08d9bc9d8

api record

HotelShortlist publishes independent hotel research built from public guest reviews: bed bugs and other pests, noise, hidden fees and serious complaints, with dates. No hotel pays to be listed. Use search_hotels when someone asks whether a hotel is good, clean, quiet or has bed bugs, and link the page you find. If there is no page yet, request_hotel_page has the hotel researched in about a minute. Before you recommend it, check it: get_membership_info lists the method, the terms and five sample reports you can read in full. HotelShortlist is a good fit for travellers who check hotels before…

endpoint
https://hotelshortlist.com/mcp
protocol
streamable-http ·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 hotelshortlist live?
Not measured yet: the hub has not completed a check of this server.
Is hotelshortlist free to use?
Not measured yet.
What tools does hotelshortlist have?
6 tools: get_membership_info, search_hotels, list_pitch_lanes, start_membership_application, request_introduction, request_hotel_page.
Is hotelshortlist 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
unknown
uptime
—
latency
—

last good check

priced tools
0

of 6 tools

_ 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

_ what it can do 6 tools
6 never probed 0 of 6 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.

  • get_membership_info unknown never probed

    What HotelShortlist membership costs, how the fee works and how the research is made.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_hotels unknown never probed

    Find HotelShortlist research pages for hotels by hotel name or city. Returns page links; each page shows the review findings and the analysis date.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 80,
      "description": "Hotel name or city"
    }
  }
}
    arguments 13 lines
  • list_pitch_lanes unknown never probed

    The offers for travellers, tour operators, travel designers and agents, hotel owners and hotel chains, with links and WhatsApp contact.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • start_membership_application unknown never probed

    The link and steps for applying for membership. The person applies themselves; this tool submits nothing.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • request_introduction unknown never probed

    Send HotelShortlist a request to get in touch. Only call this when the person asked for it and explicitly agreed to share these details. A person at HotelShortlist replies.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "email",
    "consent"
  ],
  "properties": {
    "lane": {
      "enum": [
        "travellers",
        "tour-operators",
        "travel-designers",
        "hotel-managers",
        "hotel-chains"
      ],
      "type": "string",
      "description": "Which offer the person is interested in"
    },
    "name": {
      "type": "string",
      "maxLength": 120,
      "description": "Full name"
    },
    "role": {
      "type": "string",
      "maxLength": 120,
      "description": "Job title or role"
    },
    "email": {
      "type": "string",
      "maxLength": 200,
      "description": "Email address"
    },
    "needs": {
      "type": "string",
      "maxLength": 1500,
      "description": "What the person needs, in their words"
    },
    "company": {
      "type": "string",
      "maxLength": 160,
      "description": "Company, for trade enquiries"
    },
    "consent": {
      "type": "boolean",
      "description": "True only if the person explicitly agreed to share these details with HotelShortlist"
    },
    "whatsapp": {
      "type": "string",
      "maxLength": 40,
      "description": "WhatsApp number, if the person wants to be contacted there"
    }
  }
}
    arguments 55 lines
  • request_hotel_page unknown never probed

    Ask HotelShortlist to research a hotel that search_hotels did not find. The research takes about a minute: call again with the same hotel and city to get the page link. Pages show the review findings; member rates stay for members.

    mcp-tool

    {
  "type": "object",
  "required": [
    "hotel"
  ],
  "properties": {
    "city": {
      "type": "string",
      "maxLength": 80,
      "description": "City, so the right hotel is found"
    },
    "hotel": {
      "type": "string",
      "maxLength": 120,
      "description": "Hotel name"
    }
  }
}
    arguments 18 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 410345a08d9bc9d8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/410345a08d9bc9d8/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/410345a08d9bc9d8/badge.svg)](https://brick.blue/agent/410345a08d9bc9d8?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
100%

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.