# Praesago: England and Wales property data (remote · praesago.com)

Data for every postcode district in England and Wales: prices, rents, crime, flood risk, listings.

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `praesago.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-praesago-praesago/api-mcp.md), [page](https://verifymcp.io/servers/com-praesago-praesago/api-mcp)

## Channel facts

- Endpoint: `https://praesago.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## 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-22.

- **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**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2018 tokens (~201/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (50% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 Praesago: England and Wales property data MCP server?

Praesago: England and Wales property data is a hosted endpoint at https://praesago.com/api/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 com-praesago-praesago 'https://praesago.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-praesago-praesago": {
      "url": "https://praesago.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-praesago-praesago": {
      "type": "http",
      "url": "https://praesago.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-praesago-praesago]
url = "https://praesago.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-praesago-praesago": {
      "type": "remote",
      "url": "https://praesago.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-praesago-praesago --url 'https://praesago.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-praesago-praesago:
    url: "https://praesago.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-praesago-praesago": {
      "Transport": "http",
      "Url": "https://praesago.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-praesago-praesago -t streamable-http -u 'https://praesago.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-praesago-praesago": {
      "type": "http",
      "url": "https://praesago.com/api/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-22 (score 81, +1)

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

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

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

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

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

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

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

### 2026-11-14 (score 77, +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-13 (score 76, +2)

- [security improvement] HSTS header: fail → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “compare_areas” rewrote its description, which is the text the model reads
- [security] Tool “get_area_context” rewrote its description, which is the text the model reads
- [security] Tool “get_area_overview” rewrote its description, which is the text the model reads
- [security] Tool “get_market_pulse” rewrote its description, which is the text the model reads
- [security] Tool “search” rewrote its description, which is the text the model reads

### 2026-11-12 (score 74, +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-11 (score 73, 0)

- [security] Tool “screen_areas” rewrote its description, which is the text the model reads
- [cosmetic] “screen_areas” added an optional parameter “max_yield_pct”
- [cosmetic] “screen_areas” added an optional parameter “min_yield_pct”
- [cosmetic] “screen_areas” reworded the description of “sort_by”

## MCP tools (10)

### `get_area_overview` (~317 tokens)

Area overview

Headline facts for an area in England or Wales: 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 people killed or seriously injured on the roads over three years. Takes a postcode, a postcode district or a place name (a borough name returns its best-matching district and lists the others). Optional response_format: "concise" (about 150 words) or "detailed" (default). The result also carries the figures as structured data. England & Wales only (Scotland and Northern Ireland are not covered). Each figure carries its year or date. It describes the area as it is and does not forecast prices. Give a full postcode or a postcode sector (for example "E17 7") to also get the sold price of that sector (median only with 10 or more sales in 12 months).

Input parameters:

- `area` (string, required): A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney")
- `response_format` (string): 'concise' (about 150 words: price, income, deprivation, live market and rents) or 'detailed' (default: every headline fact)

Output parameters:

- `area_name` (string|null)
- `council_tax_band_d_gbp` (number|null)
- `deprivation_median_decile` (number|null)
- `district` (string)
- `household_income_gbp` (number|null)
- `live_rents` (object|null)
- `live_sale_market` (object|null)
- `median_sold_price_gbp` (number|null)
- `population` (number|null)
- `price_change_pct` (number|null)
- `private_renters_pct` (number|null)
- `properties_at_high_or_medium_flood_risk` (number|null)
- `region` (string|null)
- `sales_12m` (number|null)
- `sector` (object)
- `ultrafast_broadband_pct` (number|null)
- `url` (string)

### `get_area_context` (~206 tokens)

Full area profile

The deeper profile for an area in England or Wales. 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. Takes a postcode, a postcode district or a place name. England & Wales only. It describes the area as it is and does not forecast prices. Give a full postcode or a postcode sector (for example "E17 7") to also get the sold price of that sector (median only with 10 or more sales in 12 months).

Input parameters:

- `area` (string, required): A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney")

### `get_area_profile` (~146 tokens)

Local authority profile

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, postcode or town use get_area_overview. England & Wales only. It describes the authority as it is and does not forecast prices.

Input parameters:

- `authority` (string, required): A local authority (council area) name, e.g. "Leeds", "Manchester", "Hackney"

Output parameters:

- `authority` (string)
- `authority_code` (string)
- `deprivation_average_decile` (number|null)
- `district_count` (number)
- `districts` (array)
- `household_income_gbp` (number|null)
- `median_sold_price_gbp` (number|null)
- `population` (number|null)
- `price_change_pct` (number|null)
- `rent_listings` (object|null)
- `sale_listings` (object|null)
- `sales_12m` (number|null)

### `screen_areas` (~466 tokens)

Screen districts by price, rent, listings and region

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), asking yield range in percent, and region (including "Wales"). Sort by price, rent, listings, price_cut or yield (a yield ranking). Returns the matching districts with their figures and links. Use for questions like "districts in the North West with a median under £200k and asking rent over £900". Districts with fewer than 30 sales have no median; fewer than 20 rent listings no asking rent. Asking rents and prices are not agreed or sold prices.

Input parameters:

- `limit` (number): Max results, up to 25 (default 10)
- `max_asking_rent_pcm` (number): Maximum median asking rent a month in GBP (optional)
- `max_median_price_gbp` (number): Maximum 12m median sold price in GBP (optional)
- `max_price_cut_pct` (number): Maximum share of sale listings that were price-reduced, in percent (optional)
- `max_yield_pct` (number): Maximum gross asking yield in percent (optional)
- `min_asking_rent_pcm` (number): Minimum median asking rent a month in GBP (optional)
- `min_median_price_gbp` (number): Minimum 12m median sold price in GBP (optional)
- `min_price_cut_pct` (number): Minimum share of sale listings that were price-reduced, in percent (optional)
- `min_sale_listings` (number): Minimum active sale listings (optional)
- `min_yield_pct` (number): Minimum gross asking yield in percent, this week, 2-bed homes where available (optional)
- `order` (string): asc or desc (default: asc for price and rent, desc for listings and price_cut)
- `region` (string): 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): price (default), rent, listings, price_cut or yield

Output parameters:

- `districts` (array)
- `order` (string)
- `rent_week` (string|null)
- `sale_week` (string|null)
- `sorted_by` (string)
- `total_matches` (number)
- `yield_week` (string|null)

### `search_areas` (~219 tokens)

Screen districts by price and region

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 regions (Kent and Surrey are in South East); for a town or borough use `search`. Districts with fewer than 30 sales in the last 12 months are left out. Scotland is not covered.

Input parameters:

- `limit` (number): Max results, up to 25 (default 10)
- `max_median_price_gbp` (number): Maximum 12m median sold price in GBP, as a plain number such as 250000 (optional)
- `region` (string): One region name from the list in the tool description, e.g. "North West", "London", "South East" (optional)

### `compare_areas` (~202 tokens)

Compare two areas

Compare two areas in England or Wales 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 Manchester) are compared as authorities, each as the postcode districts that sit mostly inside it, and the result says so. England & Wales only.

Input parameters:

- `area_a` (string, required): First area. A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney")
- `area_b` (string, required): Second area. A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney")

### `get_market_pulse` (~186 tokens)

Live asking-market pulse

Live asking-market state for an area in England or Wales, 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 lag by months) cannot show. The result states the week it covers and warns if that week is not current. Takes a postcode, a postcode district or a place name. England & Wales, sale listings and rent listings. It reports the market as it is now and does not forecast prices.

Input parameters:

- `area` (string, required): A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney")

Output parameters:

- `active_listings` (number)
- `active_listings_at_least` (boolean)
- `age_days` (number)
- `district` (string)
- `left_market` (number|null)
- `median_asking_gbp` (number|null)
- `median_days_on_market` (number|null)
- `new_listings` (number|null)
- `price_reduced` (number|null)
- `price_reduced_pct` (number|null)
- `rents` (object|null)
- `week` (string)

### `search` (~83 tokens)

Find areas by name

Search Praesago property area data for England and Wales 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.

Input parameters:

- `query` (string, required): Place name, borough, region or postcode district

### `get_usage` (~54 tokens)

Your credits and usage

Shows the credits left on your API key (free this month and purchased) and what you spent today and this month. It costs nothing. Needs an API key. Example: call it before a long batch to stay within budget.

Output parameters:

- `buy_url` (string)
- `calls_this_month` (number)
- `calls_today` (number)
- `credits_enforced` (boolean)
- `credits_left` (number)
- `credits_spent_this_month` (number)
- `credits_spent_today` (number)
- `free_credits_left` (number)
- `purchased_credits` (number)

### `fetch` (~36 tokens)

Fetch an area profile

Fetch the Praesago area profile for a postcode district returned by search.

Input parameters:

- `id` (string, required): Postcode district id from search results

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-praesago-praesago/api-mcp#diagnostics

## Score history

- 2026-11-22: 81
- 2026-11-21: 80
- 2026-11-20: 80
- 2026-11-19: 79
- 2026-11-18: 79
- 2026-11-17: 78
- 2026-11-16: 78
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 76
- 2026-11-12: 74
- 2026-11-11: 73
- 2026-11-10: 73
- 2026-11-09: 72
- 2026-11-08: 71
- 2026-11-07: 71
- 2026-11-06: 71
- 2026-11-05: 70
- 2026-11-04: 70

## Common questions

### What is the Praesago: England and Wales property data MCP server?

Praesago: England and Wales property data is an MCP server listed in the public MCP registry as com.praesago/praesago. Data for every postcode district in England and Wales: prices, rents, crime, flood risk, listings. This page covers its hosted endpoint (https://praesago.com/api/mcp).

### Is the Praesago: England and Wales property data MCP server safe to use?

Praesago: England and Wales property data scores 81 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 Praesago: England and Wales property data MCP server expose?

Praesago: England and Wales property data exposes 10 tools: get_area_overview, get_area_context, get_area_profile, screen_areas, search_areas, and 5 more. Their descriptions and schemas cost roughly 1,915 tokens of context every time the server is loaded.

### Does the Praesago: England and Wales property data MCP server require authentication?

No. We connected to Praesago: England and Wales property data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Praesago: England and Wales property data MCP server still maintained?

Praesago: England and Wales property data is still listed as active in the MCP registry. We last reached this channel on 22 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 Praesago: England and Wales property data MCP server?

VerifyMCP ran 13 checks on Praesago: England and Wales property data, 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://praesago.com/api/mcp
- Website: https://praesago.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-praesago-praesago/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-praesago-praesago/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-praesago-praesago/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-praesago-praesago/api-mcp
