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

direct-hotels

https://www.direct-hotels.com

Registry code: 5e9b8f8a9920af1c

api record

A free hotel directory: 425,000+ hotels in 230+ countries, each linked to its own website, which we fetched and saw name the hotel. No commission, no booking flow, no prices or availability. Typical order: search_hotels (or check_coverage) for a place, get_hotel for one hotel, then its booking_url. A result with covered: false means we list nothing there; the directory holds only the hotels in tool results. Each hotel carries provenance: its source and when we last checked its site. clientInfo.name on initialize, or `client` on calls, feeds the public count of assistants at…

endpoint
https://www.direct-hotels.com/api/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 direct-hotels live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is direct-hotels free to use?
Yes — the hub reached it with no key and no payment.
What tools does direct-hotels have?
6 tools: check_coverage, find_city, search_hotels, get_hotel, suggest_hotel, directory_info.
Is direct-hotels 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
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
16,715ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
1 open 5 never probed 1 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.

  • directory_info open 1h ago

    What Direct Hotels is: a free, non-commission directory linking 425,000+ hotels to their own websites; its size, where coverage is thin, and what it does not hold (prices, availability, bookings). Use when the user asks what Direct Hotels is, how it makes money, or whether it can book.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "client": {
          "type": "string",
          "maxLength": 80,
          "description": "Optional: your product or agent name, e.g. \"Claude\". Not used by the tool; recorded only for the public count of which assistants use the directory."
        }
      }
    }
    arguments 11 lines
  • check_coverage unknown 1h ago

    Whether the directory lists hotels in a place, and how many, without returning listings. Use when the user asks if a destination is covered, or before planning a trip around one. Deepest in the US and Western Europe, thin in China, the Gulf and much of Africa; an uncovered place comes back with covered places instead.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "place"
      ],
      "properties": {
        "place": {
          "type": "string",
          "maxLength": 120,
          "minLength": 2,
          "description": "City, region or country to check."
        },
        "client": {
          "type": "string",
          "maxLength": 80,
          "description": "Optional: your product or agent name, e.g. \"Claude\". Not used by the tool; recorded only for the public count of which assistants use the directory."
        },
        "country": {
          "type": "string",
          "description": "Country name or ISO code, if known."
        }
      }
    }
    arguments 24 lines
  • find_city unknown 1h ago

    Covered cities matching a few letters of a name, with hotel counts. Use when the user's place is partial, misspelled or ambiguous, before search_hotels.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "Partial city name, e.g. \"marra\", \"tok\"."
        },
        "client": {
          "type": "string",
          "maxLength": 80,
          "description": "Optional: your product or agent name, e.g. \"Claude\". Not used by the tool; recorded only for the public count of which assistants use the directory."
        }
      }
    }
    arguments 20 lines
  • search_hotels unknown never probed

    Hotels in a city or district, each with the link to book on the hotel's own website, its rating, stars and a short description. Use when the user asks where to stay somewhere, for hotels in a place, or for hotels with a pool, parking, pets allowed or a star rating. Districts, regions and spellings resolve to their city ("Shinjuku", "Badung Regency", "Marrakesh", "Roma"). City names repeat across countries, so `country` changes the answer ("Brisbane" alone is the one in California). Where the directory lists nothing, the result is covered: false with covered places instead. For one named hotel, use get_hotel.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "city"
      ],
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 120,
          "minLength": 2,
          "description": "City, neighbourhood or district name, e.g. \"Paris\", \"Shinjuku\"."
        },
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Default 5, max 20."
        },
        "stars": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Star class filter. Note: 84% of the directory has no published star class, so this hides most hotels — prefer sorting by rating."
        },
        "client": {
          "type": "string",
          "maxLength": 80,
          "description": "Optional: your product or agent name, e.g. \"Claude\". Not used by the tool; recorded only for the public count of which assistants use the directory."
        },
        "country": {
          "type": "string",
          "description": "Country name or ISO code, e.g. \"Australia\" or \"AU\". Disambiguates repeated city names."
        },
        "sort_by": {
          "enum": [
            "rating",
            "reviews"
          ],
          "type": "string",
          "description": "Default: rating."
        },
        "amenities": {
          "type": "array",
          "items": {
            "enum": [
              "pool",
              "pets",
              "parking",
              "breakfast",
              "spa",
              "gym",
              "beach",
              "accessible",
              "family",
              "air_conditioning",
              "ev_charging",
              "airport_shuttle"
            ],
            "type": "string"
          },
          "maxItems": 3,
          "description": "Only hotels whose own website mentions all of these. Read from hotel sites, which covers about a quarter of the directory, so an empty result means \"not mentioned\", not \"not available\"."
        }
      }
    }
    arguments 66 lines
  • get_hotel unknown never probed

    One hotel in full: address, rating, description, its booking link, and answers to what guests ask (pets, parking, breakfast, pool, check-in and check-out times), each with where and when it was read. Use when the user asks about a specific hotel by name, or follows up on one from search_hotels ("does it have a pool?"). Takes an id, slug or page URL from search_hotels, or a name, with `city` to narrow a common one; several matches come back as candidates. Holds no prices or availability.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "hotel"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "City, to narrow a name lookup."
        },
        "hotel": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Hotel id (\"27995\"), slug (\"27995-maison-proust\"), page URL, or name (\"Maison Proust\")."
        },
        "client": {
          "type": "string",
          "maxLength": 80,
          "description": "Optional: your product or agent name, e.g. \"Claude\". Not used by the tool; recorded only for the public count of which assistants use the directory."
        }
      }
    }
    arguments 24 lines
  • suggest_hotel unknown never probed

    Sends Direct Hotels a hotel it does not list, for review. Use when the user names a hotel that search_hotels and get_hotel did not find and wants it added. We check the hotel's own website before listing it (usually within minutes, otherwise after a manual review), so a suggestion is not yet a listing. The website, when known, is what we verify against. Stores the hotel's details only, nothing about the user.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "hotel_name",
        "city"
      ],
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 120,
          "minLength": 2,
          "description": "City or town, e.g. \"Rethymno\"."
        },
        "client": {
          "type": "string",
          "maxLength": 80,
          "description": "Optional: your product or agent name, e.g. \"Claude\". Not used by the tool; recorded only for the public count of which assistants use the directory."
        },
        "country": {
          "type": "string",
          "maxLength": 80,
          "description": "Country name or ISO code."
        },
        "website": {
          "type": "string",
          "maxLength": 500,
          "description": "The hotel's own website, not a booking platform."
        },
        "hotel_name": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "The hotel's name, e.g. \"Hotel Elida\"."
        }
      }
    }
    arguments 37 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 5e9b8f8a9920af1c.

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