Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Cubi Estate is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read-only European property search by location, price, size and features. No sign-in required.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http cubi-estate-mcp https://mcp.cubi.estate/mcp
# 2 — ask your agent for something these tools do
# search_properties, get_listing, get_contact_options and 5 more
Cubi Estate costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http cubi-estate-mcp https://mcp.cubi.estate/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search Cubi Estate's live property listings across 20 European countries. Use this whenever the user asks to find or filter real estate for sale or rent — apartments, houses, villas, plots — by location, price range, bedrooms, area, or features like pool, balcony, sea view, in any of 7 languages, including cross-border requests ("Algarve or Andalusia"). Every returned listing
No parameter schema on file.
Fetch one Cubi Estate listing's full details. Use after a search when the user wants the long description, every feature/amenity, or the full image list for a specific result. Args: listing_id: Either the listing URL exactly as shown in a search result (e.g. https://www.example.com/property/123 — the simplest option, since every result card prints its
No parameter schema on file.
How a buyer can reach the agent for one Cubi Estate listing. Read-only: lists the available contact methods (send the agent questions via Cubi, message Cubi on WhatsApp/Telegram, send a request by email), suggested questions the listing does not already answer, and the links that start each one. Nothing is sent to anyone, and the agent's phone number or email is never returned
No parameter schema on file.
Structured property filter — bypasses natural-language extraction. Use this when filters are already known (from prior turns or external state) and you want to skip the OpenAI NLU step. For free-text user queries like "cheap apartments near the beach", use search_properties instead. Prefer this tool whenever the user has named specific towns or cities plus a budget: it runs
No parameter schema on file.
Compare one listing's asking price with comparable homes on Cubi. Returns the range of ASKING prices of comparable active listings in the same city (25th-75th percentile, with the number of comparables) and where this listing's own asking price sits against it: below, within or above. This is a comparison of asking prices, not a valuation and not a prediction of the sale price
No parameter schema on file.
Day-by-day Cubi corpus activity — aggregate counts only, no listings. Use this for dashboards or "how is the corpus moving" questions: active listing totals, per-country breakdown, and per-day series of newly ingested listings, deactivated listings, and detected price drops. Args: days: Trailing window length in days (1-90, default 30). country: Optional full coun
No parameter schema on file.
Live coverage of Cubi's per-listing enrichment data layers. Use for a data-pipeline dashboard: how many active listings carry each environmental / accessibility layer, the flood-risk band split, and the per-country share of listings in a modelled High (1-in-20-year) river floodplain. Returns: JSON string. Warm cache (exact, ~6h fresh): {active_listings, cached:
No parameter schema on file.
How many NEW listings Cubi added per day, by country and by source, split into sale and rent — aggregate counts only, no listings. Use it to answer "how much new inventory is arriving" questions: today, yesterday and the last 7 completed days, per country, plus the 15 sources contributing the most new listings over those 7 days. Complements corpus_stats (which has no transact
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Cubi Estate or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Cubi Estate can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.