Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Praesago: England and Wales property data

REMOTE · PRAESAGO.COM

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

Available components

+4 this week 81 Trust /100

Last scanned (28 minutes ago)

Scores higher than 79% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Nov 26 +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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 13 Nov 26 +2
    • 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 security
  • 12 Nov 26 +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.

  • 11 Nov 26 0
    • Tool “screen_areas” rewrote its description, which is the text the model reads security
    • “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” cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Nov 2026 · Probed https://praesago.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=praesago.com CN=YE1,O=Let's Encrypt,C=US 15 Nov 2026 13 Feb 2027 ECDSA 256 ECDSA-SHA384 525ddfe9817e03f27269bbbe0cc8f128419
SANs: *.praesago.com, praesago.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of praesago.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
praesago.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy frame-ancestors 'self'; base-uri 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://praesago.com/api/mcp Verified 200
http (plaintext) http://praesago.com/api/mcp HTTPS enforced 301 https://praesago.com/api/mcp
MCP tools · 10 exposed · ~1,915 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_areas ~202

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.

NameTypeReqDescription
area_astringyesFirst area. A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney")
area_bstringyesSecond area. A postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney")

No output schema declared.

No examples provided.

fetch ~36

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

NameTypeReqDescription
idstringyesPostcode district id from search results

No output schema declared.

No examples provided.

get_area_context ~206

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).

NameTypeReqDescription
areastringyesA postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney")

No output schema declared.

No examples provided.

get_area_overview ~317

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).

NameTypeReqDescription
areastringyesA postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney")
response_formatstring–'concise' (about 150 words: price, income, deprivation, live market and rents) or 'detailed' (default: every headline fact)
NameTypeReqDescription
area_namestring|null––
council_tax_band_d_gbpnumber|null––
deprivation_median_decilenumber|null––
districtstringyes–
household_income_gbpnumber|null––
live_rentsobject|null––
live_sale_marketobject|null––
median_sold_price_gbpnumber|null––
populationnumber|null––
price_change_pctnumber|null––
private_renters_pctnumber|null––
properties_at_high_or_medium_flood_risknumber|null––
regionstring|null––
sales_12mnumber|null––
sectorobject––
ultrafast_broadband_pctnumber|null––
urlstringyes–

No examples provided.

get_area_profile ~146

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.

NameTypeReqDescription
authoritystringyesA local authority (council area) name, e.g. "Leeds", "Manchester", "Hackney"
NameTypeReqDescription
authoritystringyes–
authority_codestring––
deprivation_average_decilenumber|null––
district_countnumberyes–
districtsarray––
household_income_gbpnumber|null––
median_sold_price_gbpnumber|null––
populationnumber|null––
price_change_pctnumber|null––
rent_listingsobject|null––
sale_listingsobject|null––
sales_12mnumber|null––

No examples provided.

get_market_pulse ~186

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.

NameTypeReqDescription
areastringyesA postcode ("E17 7AB"), postcode district ("E17") or place name ("Walthamstow", "Hackney")
NameTypeReqDescription
active_listingsnumberyes–
active_listings_at_leastboolean––
age_daysnumber––
districtstringyes–
left_marketnumber|null––
median_asking_gbpnumber|null––
median_days_on_marketnumber|null––
new_listingsnumber|null––
price_reducednumber|null––
price_reduced_pctnumber|null––
rentsobject|null––
weekstringyes–

No examples provided.

get_usage ~54

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
buy_urlstring––
calls_this_monthnumber––
calls_todaynumber––
credits_enforcedbooleanyes–
credits_leftnumberyes–
credits_spent_this_monthnumber––
credits_spent_todaynumber––
free_credits_leftnumberyes–
purchased_creditsnumberyes–

No examples provided.

screen_areas ~466

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.

NameTypeReqDescription
limitnumber–Max results, up to 25 (default 10)
max_asking_rent_pcmnumber–Maximum median asking rent a month in GBP (optional)
max_median_price_gbpnumber–Maximum 12m median sold price in GBP (optional)
max_price_cut_pctnumber–Maximum share of sale listings that were price-reduced, in percent (optional)
max_yield_pctnumber–Maximum gross asking yield in percent (optional)
min_asking_rent_pcmnumber–Minimum median asking rent a month in GBP (optional)
min_median_price_gbpnumber–Minimum 12m median sold price in GBP (optional)
min_price_cut_pctnumber–Minimum share of sale listings that were price-reduced, in percent (optional)
min_sale_listingsnumber–Minimum active sale listings (optional)
min_yield_pctnumber–Minimum gross asking yield in percent, this week, 2-bed homes where available (optional)
orderstring–asc or desc (default: asc for price and rent, desc for listings and price_cut)
regionstring–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_bystring–price (default), rent, listings, price_cut or yield
NameTypeReqDescription
districtsarrayyes–
orderstring––
rent_weekstring|null––
sale_weekstring|null––
sorted_bystring––
total_matchesnumberyes–
yield_weekstring|null––

No examples provided.

search ~83

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.

NameTypeReqDescription
querystringyesPlace name, borough, region or postcode district

No output schema declared.

No examples provided.

search_areas ~219

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.

NameTypeReqDescription
limitnumber–Max results, up to 25 (default 10)
max_median_price_gbpnumber–Maximum 12m median sold price in GBP, as a plain number such as 250000 (optional)
regionstring–One region name from the list in the tool description, e.g. "North West", "London", "South East" (optional)

No output schema declared.

No examples provided.

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.

remote · praesago.com

# add to Claude Code
claude mcp add --transport http com-praesago-praesago 'https://praesago.com/api/mcp'
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.