Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Praesago UK property data 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
UK property area data for England and Wales: prices, rents, crime, flood risk, live listings.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http praesago-uk-property-data-mcp https://praesago.com/api/mcp
# 2 — ask your agent for something these tools do
# get_area_overview, get_area_context, get_area_profile and 6 more
Praesago UK property data 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 praesago-uk-property-data-mcp https://praesago.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take X-API-Key header (Optional Praesago API key for the full area profile. Setup: https://praesago.com/docs/mcp) if you want to set it.
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.
9 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.
Headline facts for a UK area: median sold price and its 12-month change, household income, population, private-renter share, deprivation, flood risk, broadband, council tax, the live listings pulse, live rents (active rent listings and median asking rent a month), the asking rental yield and average private rent, recorded crime per 1,000 residents (withheld where the police data has gaps), and peo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| area | string | yes | A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney") |
| response_format | string | no | 'concise' (about 150 words: price, income, deprivation, live market and rents) or 'detailed' (default: every headline fact) |
The deeper profile for a UK area. With a free Praesago API key: about 30 sections (demographics, income, ethnicity, tenure, dwelling types, deprivation domains, health, schools, broadband, flood, noise, green space, council tax, politics, homelessness, local economy), each with its source year. Without a key you get the same headline facts as get_area_overview plus a note on what the key adds. Tak
| Parameter | Type | Required | Notes |
|---|---|---|---|
| area | string | yes | A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney") |
Figures for a whole local authority (a council area such as Leeds, Manchester or Hackney), added up over the postcode districts that sit mostly inside it: median sold price over all their sales and its 12-month change, population, household income, deprivation, and live sale and rent listings. The result says how many districts it covers. Takes a local authority name. For one postcode district, po
| Parameter | Type | Required | Notes |
|---|---|---|---|
| authority | string | yes | A local authority (council area) name, e.g. "Leeds", "Manchester", "Hackney" |
Screen England & Wales postcode districts. Filters (all optional): median sold price range over 12 months, live asking rent range a month, minimum active sale listings, price-cut share range (from the week of 2026-11-02), and region (including "Wales"). Sort by price, rent, listings or price_cut. Returns the matching districts with their figures and links. Use for questions like "districts in the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| min_median_price_gbp | number | no | Minimum 12m median sold price in GBP (optional) |
| max_median_price_gbp | number | no | Maximum 12m median sold price in GBP (optional) |
| min_asking_rent_pcm | number | no | Minimum median asking rent a month in GBP (optional) |
| max_asking_rent_pcm | number | no | Maximum median asking rent a month in GBP (optional) |
| min_sale_listings | number | no | Minimum active sale listings (optional) |
| min_price_cut_pct | number | no | Minimum share of sale listings that were price-reduced, in percent (optional) |
| max_price_cut_pct | number | no | Maximum share of sale listings that were price-reduced, in percent (optional) |
| region | string | no | One region name: North East, North West, Yorkshire and The Humber, East Midlands, West Midlands, East of England, London, South East, South West, Wales (optional) |
| sort_by | string | no | price (default), rent, listings or price_cut |
| order | string | no | asc or desc (default: asc for price and rent, desc for listings and price_cut) |
| limit | number | no | Max results, up to 25 (default 10) |
Screen England & Wales postcode districts by region and median property price. Returns matching districts with medians and links, cheapest first. Use for questions like "areas in the North West under £250k". The region must be one of: North East, North West, Yorkshire and The Humber, East Midlands, West Midlands, East of England, London, South East, South West, Wales. Counties and cities are not r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_median_price_gbp | number | no | Maximum 12m median sold price in GBP, as a plain number such as 250000 (optional) |
| region | string | no | One region name from the list in the tool description, e.g. "North West", "London", "South East" (optional) |
| limit | number | no | Max results, up to 25 (default 10) |
Compare two UK areas side by side on median sold price and its change, income, population, private renters, deprivation, flood risk, broadband, council tax and (when both are current) the live listings pulse and live asking rents. Each line says which area is higher and by how much. Each input can be a postcode, a postcode district or a place name. Two local authority names (for example Leeds and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| area_a | string | yes | First area. A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney") |
| area_b | string | yes | Second area. A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney") |
Live asking-market state for a UK area, collected weekly from property portals: active listing count, new listings, how many have been price-reduced, median asking price, and median time on market, plus active rent listings and median asking rent a month. Answers "is this area moving or stuck?" and "are sellers cutting prices here?" — the negotiation-side data that completed-sales records (which l
| Parameter | Type | Required | Notes |
|---|---|---|---|
| area | string | yes | A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney") |
Search Praesago UK property area intelligence by place name, borough, region or postcode district. Use it when you only have a place name (for example Hackney or Sheffield) and want the matching districts. Returns matching areas with ids and links; an empty list means no match.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Place name, borough, region or postcode district |
Fetch the Praesago area profile for a postcode district returned by search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Postcode district id from search results |
- 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 Praesago UK property data 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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_area_overview | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_area_context | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_area_profile | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| screen_areas | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_areas | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| compare_areas | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_market_pulse | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| fetch | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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.1.
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 Praesago UK property data 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.