Property Price Search MCP Server

What is Property Price Search MCP Server?

A Model Context Protocol (MCP) server that allows users to search for property prices by postcode using the HM Land Registry’s SPARQL endpoint. Designed for IDE and MCP-client integration, it returns real UK property transaction data directly within development tools.

How to use Property Price Search MCP Server?

Install globally (npm install -g property-prices-mcp) or locally. Configure your MCP client (e.g., Claude Desktop) with the command property-prices-mcp via stdio transport. Use the search-property-prices tool with parameters like postcode, minPrice, propertyType, or lookup-postcodes (requires separate download of Ordnance Survey Code-Point Open data). Run npm run setup:postcodes to build the local postcode database.

Key features of Property Price Search MCP Server

• Search by UK postcode or street/city combination
• Filter results by price, property type, and date range
• Connects to HM Land Registry’s public SPARQL endpoint
• Implements MCP stdio transport for IDE integration
• TypeScript with full type safety and comprehensive tests
• Local postcode lookup & nearest‑neighbour tool (OS Code‑Point Open)

Use cases of Property Price Search MCP Server

• Quickly retrieve recent property sales for a given postcode
• Filter sales by price range and property type for market analysis
• Combine with an IDE or AI assistant for data‑driven development tasks
• Validate property price trends across different UK cities and streets

FAQ from Property Price Search MCP Server

What are the runtime requirements?

Node.js >= 20 and npm >= 7. The server runs via stdio transport and requires no additional services.

How does the server handle case sensitivity in queries?

The UK Land Registry data is case‑sensitive, but the server automatically converts street and city parameters to uppercase before querying, so users can input any case.

Where does the property price data come from?

All price data is sourced from the HM Land Registry’s public SPARQL endpoint. The optional postcode lookup uses Ordnance Survey Code‑Point Open data (downloaded separately) for resolving and finding nearby postcodes.

What should I do if I get “No Results Found”?

Broader search criteria (wider date range, remove price filters) or verify that the postcode exists. The SPARQL endpoint may also be temporarily unavailable or rate‑limited.

Is authentication required or is there any data transmission concern?

The server connects to a public, read‑only SPARQL endpoint and requires no authentication. All data resides at HM Land Registry and Ordnance Survey; no user data is stored locally except the optional Code‑Point Open database built by the user.