# GetMovely (remote · getmovely.co.uk)

Search homes for sale and off-market, sold prices, EPC, stamp duty: 25m homes in England and Wales.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `getmovely.co.uk`: 78/100 (this document), [markdown](https://verifymcp.io/servers/uk-co-getmovely-getmovely/getmovely.md), [page](https://verifymcp.io/servers/uk-co-getmovely-getmovely/getmovely)

## Channel facts

- Endpoint: `https://getmovely.co.uk/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 7690 tokens (~284/item across 27 items; 24 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 87% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the GetMovely MCP server?

GetMovely is a hosted endpoint at https://getmovely.co.uk/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http uk-co-getmovely-getmovely 'https://getmovely.co.uk/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "uk-co-getmovely-getmovely": {
      "url": "https://getmovely.co.uk/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uk-co-getmovely-getmovely": {
      "type": "http",
      "url": "https://getmovely.co.uk/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.uk-co-getmovely-getmovely]
url = "https://getmovely.co.uk/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-co-getmovely-getmovely": {
      "type": "remote",
      "url": "https://getmovely.co.uk/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add uk-co-getmovely-getmovely --url 'https://getmovely.co.uk/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uk-co-getmovely-getmovely:
    url: "https://getmovely.co.uk/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "uk-co-getmovely-getmovely": {
      "Transport": "http",
      "Url": "https://getmovely.co.uk/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add uk-co-getmovely-getmovely -t streamable-http -u 'https://getmovely.co.uk/mcp'
```

### Other

```json
{
  "mcpServers": {
    "uk-co-getmovely-getmovely": {
      "type": "http",
      "url": "https://getmovely.co.uk/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 78, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.4.2 → 0.4.3

### 2026-11-20 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “energy_performance” rewrote its description, which is the text the model reads
- [security] Tool “get_address” rewrote its description, which is the text the model reads
- [security] Tool “house_age” rewrote its description, which is the text the model reads
- [security] Tool “price_check” rewrote its description, which is the text the model reads
- [security] Tool “price_trends” rewrote its description, which is the text the model reads
- [security] Tool “street_price_per_m2” rewrote its description, which is the text the model reads
- [security] Tool “whats_nearby” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 247 → 282
- [functional] Schema quality: good → excellent
- [functional] Server version: 0.4.1 → 0.4.2
- [cosmetic] “whats_nearby” added an optional parameter “akeys”
- [cosmetic] “whats_nearby” reworded the description of “akey”
- [cosmetic] “whats_nearby” reworded the description of “n”
- [cosmetic] “whats_nearby” made “akey” optional

### 2026-11-18 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.4.0 → 0.4.1
- [functional] New tool “negotiation_brief”

### 2026-11-13 (score 75, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “search_addresses” rewrote its description, which is the text the model reads
- [functional regression] Tool coverage: 91% → 85%
- [functional regression] Schema quality: 192 → 248
- [functional] Server version: 0.3.0 → 0.4.0
- [functional] New tool “draft_letter”
- [functional] New tool “find_homes_not_for_sale”
- [functional] New tool “recent_sales”
- [functional] New tool “search_homes_for_sale”
- [functional] New tool “stamp_duty”
- [cosmetic] “search_addresses” added an optional parameter “limit”
- [cosmetic] “search_addresses” reworded the description of “page”

### 2026-11-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (24)

### `search_addresses` (~493 tokens)

Search addresses

Find homes in England and Wales by street, postcode, town or address. Each row has
the home's last sale, freehold or leasehold, whether it is owner-occupied, whether it
is listed for sale, and its response likelihood (High = listed for sale and
owner-occupied, Medium = owner-occupied, Unknown = no record). Filter with
\`response_likelihood` to answer "which homes on this street are owner-occupied and for
sale", or sort by it. Returns 20 per page (`limit`, up to 60), newest sale first by default.
If the street name exists in several places the answer lists the places as `streets`
instead of rows; ask the person which one, then search again with the town or postcode.
When nothing matches exactly the answer says so (`exact_match` false) and gives at most
ten of the nearest names, which may be in other towns: Scotland and Northern Ireland are
not covered.

Input parameters:

- `limit` (integer): Addresses per page: 20 by default, up to 60. Ask for fewer when one home is wanted.
- `page` (integer): Page number; `limit` addresses per page.
- `query` (string, required): Street, postcode, outcode, town or full address, as a person would type it: 'Merton Road, SW19', 'BS7 8', 'Ash Street, Salford M6', '41 Denning Road NW3'.
- `response_likelihood`: Only homes with this response likelihood. 'High' = listed for sale and owner-occupied (the homes where a letter reaches an owner who is selling). 'Medium' = owner-occupied, not listed for sale. 'Unkn…
- `sale_pairs`: Filter to homes whose sale history contains these sales, each as 'price:year', e.g. ['450000:2019']. This is how to find the exact address behind a listing or an advert that shows past sales.
- `sort` (string): 'recent' newest sale first (default); 'likelihood' High first, then Medium, then the rest; 'price_desc' / 'price_asc' by last sale price; 'addr' by address.

### `get_address` (~223 tokens)

Address card

One home's card, the quick answer to "is this house for sale" and "does the owner
live there": full address, last sale, freehold or leasehold, whether it is
owner-occupied (from its Energy Performance Certificate), whether it is listed for sale
(with the portal, the agent and the link to the advert), its response likelihood (High
\= listed for sale and owner-occupied), and the link that opens a letter to its owner
on GetMovely.

Use it for those yes/no facts about a home you already have an `akey` for (from
search_addresses or any row another tool returned). For prices, energy, the street and
the area use address_report (everything) or the single-topic tools. Never guess an
\`akey`: an unknown one fails with "address not found". A field that is null means no
public record, not "no": `owner_occupied` null is not the same as false.

Input parameters:

- `akey` (string, required): Address key from search_addresses (hex string).

### `address_report` (~236 tokens)

Address report (nine tiles)

Everything GetMovely knows about one home in one call. `home` gives the facts in
brief: freehold or leasehold, whether it is owner-occupied (from its Energy
Performance Certificate), whether it is listed for sale, and its response likelihood
(High = listed for sale and owner-occupied). `tiles` is the nine-part report the
website shows: sold-price
history, building type and size, energy rating with costs and improvements, local
market (price per m2 nearby), area price trend, market history (asking price, time on
the market, the agent and the link to the advert when it is for sale), nearby
essentials, recorded crime and air quality. `contact_owner_url` opens a letter to its
owner. About 15 KB: use get_address, sale_history, energy_performance or price_check
when one part is enough. Limited to 60 reports per hour per caller, a limit
sale_history, energy_performance, price_check and compare_homes share.

Input parameters:

- `akey` (string, required): Address key from search_addresses (hex string).

### `street_price_per_m2` (~199 tokens)

Street price per square metre

Recent Land Registry sales near one home with their EPC floor area, as pounds per
square metre and per square foot by year. Scope is the home's own postcode when it has
enough sized sales, otherwise the whole street; `scope` says which. Market-value
(category A) sales only.

Use it for "what do homes on this street go for per square metre". To judge one
price or an asking price use price_check, which sets the street beside the district;
for a list of the sales themselves use recent_sales with the street as `area`; for a
whole district use area_overview. Takes an `akey` from search_addresses or any row
another tool returned. A street with no sale that has a floor area on record returns
an empty `years`; that means too little evidence, not a price of zero.

Input parameters:

- `akey` (string, required): Address key from search_addresses (hex string).

### `price_trends` (~264 tokens)

Price trends by factor

What freehold or leasehold, new build or resale, energy rating and floor area are
worth per square metre in one postcode district, for one property type (D detached,
S semi-detached, T terraced, F flat), by whole calendar year, against the national
picture. Property type is always held constant because it is the confounder that
makes the naive comparison lie. Every figure is a median of at least a minimum
number of sales; no per-address data. For a plain summary of a district across all
its property types use area_overview.

Use it for "is a leasehold flat cheaper here", "what is an A-rated house worth over a
D", "do bigger homes cost less per m2". For several districts use compare_areas; for
one home use price_check. When a district has too few sales of that type the tool
fails and names the property types it does have, so ask again with one of those.

Input parameters:

- `factor` (string)
- `outcode` (string, required): Postcode district (outcode) such as 'SW19', 'BS7', 'M6'. A full postcode is accepted; only the district is used.
- `property_type` (string)

### `whats_nearby` (~402 tokens)

What is nearby

Train, tram and ferry stops, bus stops, primary and secondary schools, cafes and
restaurants, pubs, takeaways, supermarkets, parks and play areas around a home, from
official open data, within 100 m to 2 km: for each kind the count, the nearest one and
its distance. Pass `closest` with a kind to get the nearest N of that kind instead,
however far (the way to ask "how far is the station" for a rural home). To compare
many homes, pass up to 50 keys in `akeys` and get one row per home in `homes`: never
call this once per home.

Use it for amenities and transport. Crime and air quality are in address_report;
compare_homes also names the nearest station, school, supermarket and park for two to
four homes. Keys come from search_addresses or any row another tool returned. A kind
with nothing inside the radius is left out of `kinds` (an empty `kinds` means nothing
within it at all): widen `radius_m` or use `closest`. Schools here are by distance only, not catchment
or Ofsted rating.

Input parameters:

- `akey`: Address key of one home, from search_addresses. Give this or `akeys`.
- `akeys`: Several homes in one call, up to 50 address keys: use this instead of calling once per home, for example for every home recent_sales or search_homes_for_sale returned.
- `closest`: Instead of counts within the radius, list the N closest places of this one kind (expanding rings up to 16 km).
- `n` (integer): How many closest places, with `closest`: 10 by default, up to 25 for one home; at most 3 per home with `akeys`.
- `radius_m` (integer): Radius in metres, 100 to 2000.

### `tenure_check` (~129 tokens)

Freehold or leasehold check

Whether homes matching an address are freehold or leasehold, from the tenure recorded
on the latest Land Registry sale of each exact address, with that sale's date. Up to 12
candidates; null tenure means no recorded sale with a tenure. Matching is by text: when
\`fuzzy` is true or the rows are not the address asked for, use search_addresses, whose
rows carry `tenure_at_last_sale` for the exact home.

Input parameters:

- `query` (string, required): Address or street with postcode, e.g. '12 Church Lane, BS7 8AB'.

### `house_age` (~197 tokens)

When was a house built

The construction age band of homes matching an address, from the Energy Performance
Certificate, with what that era means for the construction, plus the first recorded sale
year as corroboration and the property type. Up to 12 candidates.

Use it for "when was this house built" and "what is it built like" (solid walls, cavity
walls, asbestos era). It takes the address as text, so no `akey` is needed; for the
full energy picture of one home use energy_performance. Matching is by text: when
\`fuzzy` is true the rows are near matches, not the address asked for, so say so or
search_addresses for the exact home. `band` null means that home has no certificate
with an age band; `first_yr` is the first sale since 1995, not the build year.

Input parameters:

- `query` (string, required): Address or street with postcode.

### `sale_history` (~98 tokens)

Sale history of one home

Every recorded sale of one home since 1995, from HM Land Registry price paid
data: price, month and year, the price per square metre each sale works out at on
the home's current EPC floor area, and the change from the first sale to the last.
The short answer to "what did this house sell for"; address_report has the rest.

Input parameters:

- `akey` (string, required): Address key from search_addresses (hex string).

### `energy_performance` (~235 tokens)

Energy performance of one home

A home's Energy Performance Certificate in plain terms: rating and score now and
the rating it could reach, modelled running costs a year for heating, hot water and
lighting, carbon dioxide, which parts of the building are weak (walls, roof,
windows), and the assessor's own list of improvements with their indicative costs.
Costs are the assessor's model at the prices of the certificate's date, not bills.

Use it for "how efficient is this home", "what would it cost to heat" and "what
should I upgrade", when an `akey` is known (from search_addresses or any row another
tool returned). address_report carries the same certificate among its nine parts;
house_age gives only the build era. A home with no certificate returns
\`certificate: false` and a `reason` (one not sold or let since 2008 may never have
had one); that is missing evidence, not a bad rating. Check `certificate_year`:
an old certificate may predate later work on the home.

Input parameters:

- `akey` (string, required): Address key from search_addresses (hex string).

### `price_check` (~328 tokens)

Check a price against the district and the street

Is a price in line? Works out the price per square metre from the home's EPC
floor area and sets it against three things: what homes of the same type sold for
per square metre in the same postcode district in the latest whole year, with the
quartiles; recent sales on the home's own street or postcode; and the home's own
last sale moved by the district's change since. Also gives the price range the
district's quartiles imply for this floor area. Arithmetic on public medians, not a
valuation, and the answer carries the caveats to pass on. Shares the address
report's limit of 60 an hour per caller.

Use it for "is this price fair" or "what might this home be worth" on one home with
an `akey` (from search_addresses or any row another tool returned). For a home on
the market, negotiation_brief adds the asking-price cuts and time on the market.
When the home has no floor area on record, or its district too few sales of its
type, the answer has `comparable: false` and a `reason` naming the tool to use
instead; pass that on rather than inventing a figure.

Input parameters:

- `akey` (string, required): Address key from search_addresses (hex string).
- `price_gbp`: The price to check, in pounds: an asking price, an offer, a valuation. Leave out to get what the district's prices imply for a home this size (and, when the home is advertised for sale, to check its…

### `negotiation_brief` (~176 tokens)

Negotiation brief for a home for sale

The evidence a buyer brings to an offer on one home that is advertised for
sale: the asking price now, every change to it GetMovely has seen on the advert
(with dates and the total cut), how long it has been on the market, the asking
price per square metre against what the same type of home sold for in the postcode
district, against recent sales on the street, and against the home's own last sale
moved by the district's change since, then the points that follow, in plain
sentences. Evidence, not a valuation or advice on what to offer. For a home that
is not on the market use price_check. Shares the address report's limit of 60 an
hour per caller.

Input parameters:

- `akey` (string, required): Address key from search_addresses (hex string).

### `compare_homes` (~149 tokens)

Compare two to four homes

Two to four homes side by side, one row each: type and floor area, tenure, last
sale and its price per square metre, energy rating and modelled running cost, what
the street has sold for recently, the district trend, whether it is
owner-occupied, whether it is listed for sale and its response likelihood (High =
both), the nearest supermarket, primary school, station and park, recorded crime
and air quality. Each row links its own report and the page
that opens a letter to its owner. Counts as one address report per home against the
60 an hour limit.

Input parameters:

- `akeys` (array, required): Two to four address keys from search_addresses.

### `find_address_from_sale_history` (~249 tokens)

Find the address behind a listing from its sale history

Property portals often hide the house number but show the home's past sale
prices. HM Land Registry records every sale by exact address, so the sale history
identifies the home: give the area and the sales, get the address or addresses that
match. One match is the answer. Several means add another sale or a tighter area.
None means check the year (portals show the year the sale completed) or widen the
area. The returned `akey` works with every per-address tool.

Input parameters:

- `area` (string, required): Where the listing says the home is: a street with its district ('Merton Road, SW19'), a postcode or its first half ('SW19 1'), or a town.
- `match` (string): 'any' (default): the home has these sales, possibly among others. 'last': the newest sale given is the home's most recent sale. 'only': the home has exactly these sales and no others.
- `sales` (array, required): Past sales shown on the listing, each as 'price:year' in pounds, for example ['450000:2019', '310000:2012']. More sales narrow it faster.

### `area_overview` (~148 tokens)

Overview of one postcode district

What homes sell for in one postcode district, for every property type sold
there (detached, semi-detached, terraced, flats): the latest whole year's median
price per square metre with its quartiles and number of sales, the change since
the series began in 2015, and the year in progress against the same months a year
earlier. Use compare_areas to set districts against each other and price_trends
for what tenure, energy rating or size are worth within one.

Input parameters:

- `outcode` (string, required): Postcode district such as 'SW19', 'BS7', 'M6'. A full postcode is accepted; only the district is used.

### `compare_areas` (~185 tokens)

Compare postcode districts

Two to six postcode districts side by side for one property type: latest whole
year's median price per square metre with quartiles and sales, change since 2015,
the year in progress against the same months a year earlier and, when a floor area
is given, what that many square metres cost at each district's median. Property
type is held constant because comparing a district of flats with a district of
houses compares the mix, not the place.

Input parameters:

- `floor_area_m2`: Optional floor area to price at each district's median, for example 100.
- `outcodes` (array, required): Two to six postcode districts, for example ['SW19', 'BS7', 'M20'].
- `property_type` (string): One type, held constant across the districts: D detached, S semi-detached, T terraced, F flat.

### `district_statistics` (~189 tokens)

Research figures for a local authority district

GetMovely's published research for one local authority district, with England
and Wales alongside: the share of homes that are leasehold (houses and flats
separately), how many years pass between sales of the same home and the share not
sold for 20 years or more, the share of purchases resold within two years, and how
big homes are (median floor area, by property type and built form). Districts are
named as HM Land Registry and the EPC register name them; an unclear name returns
the candidates. For prices use area_overview, which works by postcode district.

Input parameters:

- `district` (string, required): A local authority district in England or Wales by name: 'Bristol', 'Camden', 'Merton', 'Leeds', 'Cardiff'. 'London' gives Greater London as a whole and 'England and Wales' the national figures.

### `search_homes_for_sale` (~487 tokens)

Search homes for sale

Homes currently advertised for sale in an area of England or Wales, by criteria:
"find me a 3-bed under £400k in BS7", "flats over 60 m2 in Wimbledon". Filter by
asking price, bedrooms, property type and floor area; and, for adverts GetMovely has
matched to an exact address, by freehold or leasehold, energy rating and whether the
owner lives there. Each row has the asking price, bedrooms, type, floor area, price
per square metre, when it was listed and days on the market, the portal, agent and
link to the advert, and for a matched home its address key, response likelihood and
the link that opens a letter to its owner. 20 a page; `total` is every advert that
fits. Adverts are re-read regularly, so a brand-new listing can be missing.

Input parameters:

- `area` (string, required): Where to look: a postcode district ('BS7'), a full postcode ('SW19 1AB'), a town ('Wimbledon'), or a street with its district or town ('Elm Road, BS7').
- `epc_ratings`: Energy ratings to keep, for example ['A','B','C']. Only adverts matched to an exact address.
- `max_bedrooms`
- `max_price_gbp`: Highest asking price in pounds.
- `min_bedrooms`
- `min_floor_area_m2`: Smallest floor area in square metres. Adverts with no floor area on record are left out.
- `min_price_gbp`: Lowest asking price in pounds.
- `owner_occupied`: True: only homes whose Energy Performance Certificate records them as owner-occupied (response likelihood High). Only adverts matched to an exact address.
- `page` (integer): Page number, 20 homes a page.
- `property_type`: From the advert's own words. 'house' is any house including bungalows; 'flat' includes apartments and maisonettes; 'terraced' includes end of terrace.
- `sort` (string): 'newest' advert first (default), by asking price, by asking price per square metre (lowest first), or largest first.
- `tenure`: As recorded at the home's last sale. Only adverts matched to an exact address can be filtered this way.

### `find_homes_not_for_sale` (~542 tokens)

Find homes that are not for sale

Homes that are NOT advertised for sale, by criteria: the homes a buyer could write
to. "Which houses on this street could I write to", "owner-occupied houses over
120 m2 in BS7 that last sold before 2005". Filter by property type, floor area,
freehold or leasehold, energy rating, when and for how much the home last sold, and
whether the owner lives there. Each row has the address, type, floor area, energy
rating, last sale and its price per square metre, whether it is owner-occupied, its
response likelihood, and `contact_owner_url`, the link that opens a letter to that
home's owner on GetMovely. Most property servers list only what is on the market;
this one searches the homes that are not. 20 a page.

Input parameters:

- `area` (string, required): Where to look: a postcode district ('BS7'), a full postcode ('SW19 1AB'), a town ('Wimbledon'), or a street with its district or town ('Elm Road, BS7'). A town of more than four postcode districts mu…
- `epc_ratings`: Energy ratings to keep, for example ['E','F','G'] for homes that need work.
- `last_sold_after_year`: Last sold in or after this year.
- `last_sold_before_year`: Last sold before this year: long-held homes. Homes with no recorded sale since 1995 are included too unless no_recorded_sale says otherwise.
- `max_floor_area_m2`
- `max_last_sale_price_gbp`
- `min_floor_area_m2`
- `min_last_sale_price_gbp`
- `no_recorded_sale`: Homes with no sale on record since 1995 (held longest of all): 'only' those, or 'exclude' them.
- `owner_occupied`: True: only homes whose Energy Performance Certificate records them as owner-occupied (response likelihood Medium), where a letter reaches the owner.
- `page` (integer): Page number, 20 homes a page.
- `property_type`: From the home's Energy Performance Certificate, which does not say detached, semi-detached or terraced.
- `sort` (string): 'owner_occupied_first' (default, the website's order), 'longest_held' oldest last sale first, 'recent' newest sale first, by last sale price, or largest floor area first.
- `tenure`: As recorded at the home's last sale, so homes with no recorded sale are left out.

### `recent_sales` (~397 tokens)

Recent sold prices in an area

What sold in an area, newest first: "what sold near here this year", "flats sold in
SW19 since January for under £500k". HM Land Registry price paid data for a postcode
district, postcode, street or small town, filtered by property type, date range,
price range, floor area, tenure and new build. Each sale has the address, price,
date, type, freehold or leasehold, and the price per square metre where the home has
a floor area on its Energy Performance Certificate. Market-value sales only. Sales
reach the register two weeks to two months after completion, so the last few weeks
are always incomplete. For one home's own history use sale_history.

Input parameters:

- `area` (string, required): Where to look: a postcode district ('BS7'), a full postcode ('SW19 1AB'), a town ('Wimbledon'), or a street with its district or town ('Elm Road, BS7'). A town of more than six postcode districts mus…
- `max_price_gbp`
- `min_floor_area_m2`: Only sales of homes at least this big. Needs a floor area on an Energy Performance Certificate; with this filter the total is not counted.
- `min_price_gbp`
- `new_build`: New-build sales only, or leave them out.
- `page` (integer): Page number, 20 sales a page.
- `property_type`: D detached, S semi-detached, T terraced, F flat (the Land Registry's own classes).
- `sold_from`: Earliest sale date, 'YYYY-MM-DD', or a year ('2026' means from 1 January 2026).
- `sold_to`: Latest sale date, 'YYYY-MM-DD', or a year ('2025' means to 31 December 2025).
- `tenure`: As recorded on the sale.

### `stamp_duty` (~256 tokens)

Stamp duty calculator (SDLT in England, LTT in Wales)

How much stamp duty: Stamp Duty Land Tax for a home in England, Land Transaction Tax
for one in Wales, for a home mover, a first-time buyer or an additional property,
with the tax in each band and the other two buyer cases beside it. Uses the
residential rates published on GOV.UK and gov.wales, quoted in `sources` with the
date they were read. An estimate for a standard purchase of one freehold or
existing leasehold home by individuals: shared ownership, new leases with rent,
companies, mixed-use property and linked purchases follow other rules, and the
official calculator is linked in the answer.

Input parameters:

- `buyer` (string): 'home_mover': replacing a main home, the standard rates. 'first_time': every buyer is a first-time buyer. 'additional': the buyer will own more than one home after the purchase (second home, buy to l…
- `country` (string): Where the home is. England uses Stamp Duty Land Tax; Wales uses Land Transaction Tax.
- `non_uk_resident` (boolean): Buyer is not a UK resident (adds 2% in England).
- `price_gbp` (integer, required): Purchase price in pounds.

### `draft_letter` (~224 tokens)

Open a drafted letter to a home's owner on GetMovely

Hand a letter the person has agreed with you to GetMovely. Returns `letter_url`: a
link that opens the letter composer for that home on getmovely.co.uk with the text
already filled in, where the person reads it, can edit it, and sends it themselves
(free; sending needs a free account, and GetMovely prints and posts it). Nothing is
sent and nothing is stored by this call: the text travels inside the link. Checks
the website's letter rules first (200 words, 1,400 characters) and says what to fix
if the text breaks them. Draft with the person first; the guide
'letter-to-homeowner-asking-to-buy-house' says what a good letter contains.

Input parameters:

- `akey` (string, required): Address key from search_addresses (hex string).
- `letter_text` (string, required): The message the person has agreed, as plain text: what goes in the body of the letter. No address block, date or sign-off name is needed; GetMovely lays the letter out.

### `search_guides` (~157 tokens)

Search the guides

GetMovely's plain-English guides to buying and selling homes in England and
Wales: contacting an owner directly and the law on it, buying or selling without an
estate agent, finding who owns a property or the address behind a listing, how
often sales fall through, speeding a sale up, best and final offers, stopping
unwanted letters. Returns the closest guides with a one-paragraph summary and the
questions each answers; read_guide gives the full text with its sources.

Input parameters:

- `query`: What the person wants to know, in plain words: 'is it legal to write to a homeowner', 'who owns the freehold', 'how many house sales fall through'. Leave out to list every guide.

### `read_guide` (~109 tokens)

Read a guide

The full text of one GetMovely guide as Markdown, with the questions it
answers, the primary sources it cites (GOV.UK, HM Land Registry, the ICO, The
Property Ombudsman and others) and the date it was last updated. General
information, not legal advice. Cite the guide's `url` when you use it.

Input parameters:

- `slug` (string, required): Guide slug from search_guides, for example 'is-it-legal-to-write-to-a-homeowner'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/uk-co-getmovely-getmovely/getmovely#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 75
- 2026-11-11: 74
- 2026-11-10: 74

## Common questions

### What is the GetMovely MCP server?

GetMovely is an MCP server listed in the public MCP registry as uk.co.getmovely/getmovely. Search homes for sale and off-market, sold prices, EPC, stamp duty: 25m homes in England and Wales. This page covers its hosted endpoint (https://getmovely.co.uk/mcp).

### Is the GetMovely MCP server safe to use?

GetMovely scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the GetMovely MCP server expose?

GetMovely exposes 24 tools: search_addresses, get_address, address_report, street_price_per_m2, price_trends, and 19 more. Their descriptions and schemas cost roughly 6,072 tokens of context every time the server is loaded.

### Does the GetMovely MCP server require authentication?

No. We connected to GetMovely without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GetMovely MCP server still maintained?

GetMovely is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the GetMovely MCP server?

VerifyMCP ran 13 checks on GetMovely, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://getmovely.co.uk/mcp
- Website: https://getmovely.co.uk/mcp
- Changelog RSS feed: https://verifymcp.io/servers/uk-co-getmovely-getmovely/getmovely.xml
- Changelog JSON feed: https://verifymcp.io/servers/uk-co-getmovely-getmovely/getmovely/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/uk-co-getmovely-getmovely/getmovely.json
- HTML version of this page: https://verifymcp.io/servers/uk-co-getmovely-getmovely/getmovely
