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

Airbnb

https://mcp.wondel.ai

Registry code: 4deb8d0241c60c80

api record

YouTube search: find videos, fetch details and comments, pull full transcripts.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.wondel.ai/airbnb/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 Airbnb live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Airbnb free to use?
Yes — the hub reached it with no key and no payment.
What tools does Airbnb have?
2 tools: airbnb_listing, airbnb_search.
Is Airbnb 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
399ms

last good check

priced tools
0

of 2 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

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 2 tools
2 never probed 0 of 2 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.

  • airbnb_listing unknown never probed

    Full details of one Airbnb listing: name, type, capacity, bedrooms/beds/baths, sleeping arrangements, amenities (and notable ones missing), description (trimmed), house rules with check-in/check-out times, the host (name, Superhost, company or individual, years hosting, response rate — no contact details), the rating with its categories, approximate location, highlights and photos. With checkin/checkout it also returns the price for that stay and guests — the TOTAL incl. all fees (`price`), `price_per_night`, `price_before_discount`, `price_breakdown` — and `available`: false when the listing cannot be booked for those dates or that many guests (the note says why). Without dates there is no price (Airbnb prices only dated stays). Scraped live from airbnb.pl (typically ~1 s via direct fetch; ~10 s when it falls back to an unblocker). Two requests with dates (the page, then a dated search around it for the price). Result: { source, fetchedAt, query, page_url, listing: { id, url, name, kind, room_type, property_type, summary, overview, capacity, bedrooms, beds, baths, location: { name, lat, lng, approximate }, rating, review_count, rating_categories, guest_favorite, is_new, host: { name, superhost, verified, business, years_hosting, rating, review_count, response_rate, response_time, about }, description, checkin_from, checkin_until, checkout_by, house_rules, additional_rules, sleeping: [{ room, beds }], amenities, amenities_not_included, highlights, photos, stay, guests, available, free_cancellation, price_basis, price, price_per_night, price_per_month, price_before_discount, nights, currency, price_text, price_breakdown }, note? }. Text fields are Airbnb's Polish wording.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "listing"
      ],
      "properties": {
        "pets": {
          "type": "integer",
          "maximum": 5,
          "minimum": 0,
          "description": "Pets (limits results to pet-friendly stays). Default 0."
        },
        "adults": {
          "type": "integer",
          "maximum": 16,
          "minimum": 1,
          "description": "Adults (13+). Default 2."
        },
        "checkin": {
          "type": "string",
          "description": "Arrival date, YYYY-MM-DD (from today to about two years ahead). Pass together with checkout; omit both for Airbnb's own suggested dates."
        },
        "infants": {
          "type": "integer",
          "maximum": 5,
          "minimum": 0,
          "description": "Infants under 2 (not counted as guests). Default 0."
        },
        "listing": {
          "type": "string",
          "minLength": 1,
          "description": "The listing: its `id` from airbnb_search (e.g. '49891381') or its link from any Airbnb domain (https://www.airbnb.pl/rooms/49891381, https://www.airbnb.com/rooms/49891381)."
        },
        "checkout": {
          "type": "string",
          "description": "Departure date, YYYY-MM-DD, after checkin (at most 365 nights; 28+ nights are quoted per month)."
        },
        "children": {
          "type": "integer",
          "maximum": 15,
          "minimum": 0,
          "description": "Children aged 2–12. adults + children ≤ 16. Default 0."
        },
        "currency": {
          "type": "string",
          "description": "3-letter ISO currency for prices, e.g. 'PLN' (default), 'EUR', 'USD', 'GBP'."
        },
        "no_cache": {
          "type": "boolean",
          "description": "Force a fresh fetch and bypass this server's result cache (5 min). Default false."
        }
      }
    }
    arguments 54 lines
  • airbnb_search unknown 1h ago

    Search places to stay on Airbnb — apartments, houses, rooms, cabins, villas and hotels — in any city, region or country, for given dates and guests: price for the stay, rating and review count, Guest favourite / Superhost badges, beds and baths, coordinates, photos and a link that opens the same stay. Filter by room type, minimum bedrooms and total price. One page is up to 18 stays; `page` 2–15 for more (Airbnb caps a search at 270). Pass a listing's `id` to airbnb_listing for amenities, house rules and the host. Scraped live from airbnb.pl (typically ~1 s via direct fetch; ~10 s when it falls back to an unblocker). WITH checkin + checkout, `price` is the TOTAL for the whole stay for the given guests, all fees and taxes included (Airbnb's EU total-price display), in `currency`; `price_per_night` = price ÷ nights; `price_before_discount` is the struck-through total when discounted; `price_breakdown` lists Airbnb's own lines (e.g. '2 noce x 245,00 zł' → 490, 'Podatki' → 8). Stays of 28+ nights are quoted per month: `price` null, `price_per_month` set. WITHOUT dates, Airbnb prices each listing for its own suggested stay (its `stay`, usually ~5 nights soon), so prices are not comparable and not a quote — a `note` says so; pass dates to quote a trip. Only stays bookable for the given dates are listed. Result shape: { source, fetchedAt, query, search_url, place: { query, place_id, resolved, city, region, country }, stay: { checkin, checkout, nights } | null, guests: { adults, children, infants, pets }, currency, total_count, page, total_pages, count, listings: [...], note? } — the list key is `listings`; `total_count` is Airbnb's count of matches (more than it lets you page through). Each listing: { id, url, name, kind, city, details, bedrooms, beds, baths, host_type, rating, review_count, is_new, guest_favorite, superhost, badges, free_cancellation, stay, price_basis, price, price_per_night, price_per_month, price_before_discount, nights, currency, price_text, price_breakdown, lat, lng, photos }. `rating` is 0–5; `kind`/`city`/`details`/`price_text` are Airbnb's Polish wording (e.g. kind 'Mieszkanie' = apartment, 'Pokój' = room, 'Dom' = house); `host_type` is business | private; coordinates are approximate (Airbnb blurs them). An empty match answers count: 0 with a `note` saying why and what to change — that is a successful result, not an error.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "place"
      ],
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 15,
          "minimum": 1,
          "description": "Results page, 1-based (18 stays per page, at most 15 pages). Default 1."
        },
        "pets": {
          "type": "integer",
          "maximum": 5,
          "minimum": 0,
          "description": "Pets (limits results to pet-friendly stays). Default 0."
        },
        "place": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Where to stay — a city, region, area or country, as you would type it into Airbnb: 'Zakopane', 'Kraków', 'Mazury', 'Lisbon, Portugal', 'Tuscany'. Add the country to disambiguate. Latin script (diacritics are fine)."
        },
        "adults": {
          "type": "integer",
          "maximum": 16,
          "minimum": 1,
          "description": "Adults (13+). Default 2."
        },
        "checkin": {
          "type": "string",
          "description": "Arrival date, YYYY-MM-DD (from today to about two years ahead). Pass together with checkout; omit both for Airbnb's own suggested dates."
        },
        "infants": {
          "type": "integer",
          "maximum": 5,
          "minimum": 0,
          "description": "Infants under 2 (not counted as guests). Default 0."
        },
        "checkout": {
          "type": "string",
          "description": "Departure date, YYYY-MM-DD, after checkin (at most 365 nights; 28+ nights are quoted per month)."
        },
        "children": {
          "type": "integer",
          "maximum": 15,
          "minimum": 0,
          "description": "Children aged 2–12. adults + children ≤ 16. Default 0."
        },
        "currency": {
          "type": "string",
          "description": "3-letter ISO currency for prices, e.g. 'PLN' (default), 'EUR', 'USD', 'GBP'."
        },
        "no_cache": {
          "type": "boolean",
          "description": "Force a fresh fetch and bypass this server's result cache (5 min). Default false."
        },
        "price_max": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Maximum total price for the whole stay incl. fees, whole units of `currency` (needs dates)."
        },
        "price_min": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Minimum total price for the whole stay incl. fees, whole units of `currency` (needs dates)."
        },
        "room_type": {
          "enum": [
            "entire_home",
            "private_room"
          ],
          "type": "string",
          "description": "Only 'entire_home' (the whole place to yourself) or only 'private_room'. Default: any."
        },
        "min_bedrooms": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "At least this many bedrooms."
        }
      }
    }
    arguments 87 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 4deb8d0241c60c80.

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

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.

_ also on wondel.ai 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.