← Registry

General Tools

hellolanding.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint12 known toolsFirst detected August 2, 2026Last detected August 2, 2026

ENDPOINT 1

https://www.hellolanding.com/mcp/public

No auth detected

MCP server metadata

Name
landing_furnished_apartments
Version
1.0.0
Capabilities
tools.listChangedprompts.listChangedresources.listChangedlogging
Server instructions

Landing Furnished Apartments — help anyone find and book a furnished apartment on hellolanding.com. ## Getting started / transports This is an MCP server: JSON-RPC over HTTP POST to https://www.hellolanding.com/mcp/public. No authentication is required for any tool. **Can't use MCP?** If your environment can't POST/JSON-RPC or has no MCP client (e.g. a GET-only fetch tool), the read-only DATA tools are available as plain HTTP GET at https://www.hellolanding.com/api/public. The three MCP-only tools have no REST mirror: `search_apartments_on_map` and `compare_apartments` exist to drive in-chat widgets, and `availability_overview` is kept off the GET API because of its fan-out — GET consumers use the data tools and build their own presentation. Docs: https://www.hellolanding.com/api/public (quick reference) and https://www.hellolanding.com/api/public/openapi.json (OpenAPI 3.1). Example: `GET https://www.hellolanding.com/api/public/search?market=birmingham&check_in=2026-09-01&check_out=2026-12-01`. **Agent guide (llms.txt):** https://www.hellolanding.com/llms.txt — a plain-text walkthrough of both transports (this MCP server + the GET REST API), the tool set, and typical search→quote flows. **Tool catalog:** https://www.hellolanding.com/api/public/tools.json — this server's `tools/list` as a plain GET (full descriptions, schemas, example calls); markdown at https://www.hellolanding.com/api/public/tools. Share these URLs with agents that can't hold an MCP session. ## Recommended flow 1. **list_markets** — see which markets Landing operates in AND the display cities within each. A market is a broad metro; a display city is a specific place inside it (e.g. the "Washington DC" market contains "Alexandria, VA" / "alexandria-va"). The site is display-city-centric, so PREFER a city slug when the guest names a specific place; use a market slug for a whole region. Both search tools' `market` argument accepts either. 2. **get_market_filters** — optional but recommended before searching: returns all available filter options for a market (bedroom counts, amenities, price range, neighborhoods, sort orders). 3. **search_apartments** — find available homes in a market. Use `get_market_filters` first to see all available filter options for the market (bedroom counts, amenities, price range, neighborhoods, sort orders). Key filters: `start_date`/`end_date`, `end_date: "indefinite"` + `committed_nights` (Landing Flex), `min_bedrooms`/`max_bedrooms`, `min_bathrooms`, `min_price`/`max_price`, amenity booleans (`pets`, `cats`, `dogs`, `parking`, `pool`, `gym`, `in_unit_laundry`, `air_conditioned`, `balcony`, `elevator`, `first_floor_unit`, `self_check_in`), `deals_only` (find special offers/discounts), `guest_rating` (EXCELLENT/VERY_GOOD/GOOD), `sort_by`, proximity (`near_latitude`/`near_longitude`/`near_radius_miles`/`near_label`), and `page`/`per_page` (default 25, max 100). Response includes `total_count`, `total_pages`, and per-home `latitude`/`longitude`/`home_url`. **Resolving a location: match a display city/market FIRST.** For a named place ("in Birmingham", "Alexandria", "downtown Austin"), pass the display-city/market slug from list_markets as `market` — that is the normal path. Use `near_latitude`/`near_longitude` ONLY as a last resort, when the guest anchors to a precise spot that is NOT a listable city/market (a specific building, employer, hospital, campus, or address, e.g. "near UAB hospital"); even then also set `market` to the city it's in, and **prefer `search_apartments_on_map`** so the point and the surrounding apartments render on a map. 4. **get_apartment** — full details on one home: amenities, photos, the full availability calendar (`bookable_windows`, `ranges`, `earliest_available_date` — clipped to your dates), base pricing, aggregate guest rating (`member_rating`: average + count; individual reviews are only on hellolanding.com), walk/transit/bike scores, and a `home_url` to share. Use `bookable_windows` to find open date ranges without a separate availability call. 4b. **availability_overview** — a date-agnostic OVERVIEW of when apartments are available across a WHOLE display city or market: every matching home with its `bookable_windows` and minimum-stay rules, no dates required. Reach for this only when you need availability in a BROAD sense — open-ended, date-flexible asks like "find me a place for 3 nights, I don't care when" — then scan the returned windows for a gap that fits. **If you already know the dates, prefer `search_apartments` (or `search_apartments_on_map`) instead** — it filters to that window directly. Takes the same filters as search minus dates. 5. **get_flex_options** — if the guest wants Landing Flex (a 6+ month stay at Landing's lowest rates), call this to see exactly which commitment lengths the home accepts. Not all homes support all lengths. 6. **get_quote** — real pricing for specific dates: monthly rent, first-month charge, and the all-in total (`total_cost_estimate`). Verifies bookability too (returns an unavailable reason when the window isn't bookable). Returns `home_url` and `checkout_url`, both pre-filled and ready to share. 7. **booking_intent** — save the guest's interest and get a direct `checkout_url` to send them to payment. The guest creates a Landing account and pays there. ## Beyond search - **compare_apartments** — side-by-side comparison of 2-4 homes (price, size, amenities, ratings, availability). Use this instead of calling get_apartment repeatedly when the guest is deciding between specific homes. - **Deals** — to find discounted homes, call `search_apartments` with `deals_only: true` (composable with every other filter). - **get_market_info** — average rent by bedroom count, inventory, and popular neighborhoods for a market (great for cross-market comparisons); pass a `home_slug` too to also get that home's neighborhood description and walk/transit/bike score. - **get_policies_faq** — grounded answers on deposits, pets, parking, cancellation, qualification, and Landing Flex mechanics. Use this instead of guessing at policy specifics. ## Sharing links Tools return `home_url` (home detail page with dates pre-filled) and/or `checkout_url` (goes straight to payment). Always share the most direct link available: - After get_quote or booking_intent → use `checkout_url`. - After get_apartment → use `home_url`. - You can build links manually: `https://www.hellolanding.com/homes/{slug}?startDate=YYYY-MM-DD&endDate=YYYY-MM-DD&searchedCity={market-slug}` — replace `/homes/` with `/checkout/` for direct checkout. ## Landing Flex — best rates, total flexibility Landing Flex lets members book once, stay as long as they need, and take their discount to any home across 250+ markets. It's Landing's lowest rate option. If a guest mentions wanting flexibility, a longer stay, or a better price — bring up Landing Flex. Use get_flex_options to see which tiers a home supports, then get_quote with end_date="indefinite" and committed_nights to show the flex price. ## Notes - No authentication required for any tool. - Prices are public/anonymous rates. Promo codes, membership pricing, and credits apply after the guest signs in on hellolanding.com. - Reservations are completed on hellolanding.com — this server handles discovery and interest, not payment. - Rate-limited per IP — space out bulk requests.

Known tools 12

list_markets_tool

List every Landing market currently accepting bookings, and — nested under each — its **display cities** (the specific, neighborhood-level places the website is organized around).

Inferred read-only
get_market_filters_tool

Returns all available filter options for a given market — its display cities, bedroom counts, amenities, price range, bathroom options, neighborhoods, and sort orders.

Inferred read-only
search_apartments_tool

Search Landing's published furnished apartments by location.

Inferred read-only
search_apartments_on_map

Search Landing's published furnished apartments in a given market and render the results as an interactive map (pins), not a card grid.

Inferred read-only
get_apartment_tool

Fetch a single Landing home by its slug — property details, amenities, photos, **flex pricing**, **the full availability calendar**, and a pre-filled `reservation_link` so the agent doesn't have to probe dates or assemble booking URLs by hand (get_apartment already returns the full calendar).

Inferred read-only
availability_overview_tool

Full, date-agnostic availability OVERVIEW of a whole display city or market: every matching apartment together with its booking ranges (the SAME availability ranges the website's property page uses) and minimum-stay rules.

Inferred read-only
get_flex_options_tool

Return the flex (open-ended) commitment tiers a given home accepts, so the agent doesn't suggest a `committed_nights` value the home will reject.

Inferred read-only
get_quote_tool

Real, date-specific anonymous quote for a home.

Inferred read-only
booking_intent_tool

Save the guest's interest in a home so Landing can follow up, then return a direct checkout link for them to complete the booking.

Inferred read-only
compare_apartments_tool

Side-by-side comparison of 2-4 Landing homes — price, size, amenities, ratings, and availability in one call, instead of stitching together multiple get_apartment calls yourself.

Inferred read-only
get_market_info

Market context for a Landing market: average monthly rent by bedroom count, total published inventory, and the neighborhoods with the most availability — useful for cross-market comparisons ("is Austin or Dallas cheaper for a 1BR?") without paging through search_apartments.

Inferred read-only
get_policies_faq_tool

Grounded, conservative answers to the most common Landing policy questions (deposits, pets, parking, cancellation, qualification, Landing Flex, utilities, move-in).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.landing_furnished_apartments]
url = "https://www.hellolanding.com/mcp/public"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "landing_furnished_apartments": {
      "type": "http",
      "url": "https://www.hellolanding.com/mcp/public"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: landing_furnished_apartments
Remote MCP URL: https://www.hellolanding.com/mcp/public

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "landing_furnished_apartments": {
      "url": "https://www.hellolanding.com/mcp/public"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "landing_furnished_apartments": {
      "type": "http",
      "url": "https://www.hellolanding.com/mcp/public"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "landing_furnished_apartments",
  "transport": "streamable-http",
  "url": "https://www.hellolanding.com/mcp/public"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for hellolanding.com was fetched 2026-08-08T19:43:26.595Z and is being refreshed.

Trust status Trusted

hellolanding.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.