# Landregistry Uk [Health: Active]

**Category:** 🏠 Real Estate  
**Repository:** https://github.com/pipeworx-io/mcp-landregistry-uk  
**GitHub Stars:** 0  
**npm Downloads (last month):** 441  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/landregistry-uk

## Description
HM Land Registry Price Paid Data (UK) MCP.

## Tools
Capabilities this server exposes over MCP:

- **search_transactions** — Search HM Land Registry Price Paid records — individual residential property sales in England & Wales since 1995. Filter by postcode, town, district, county, price range and sale-date range; sort and page through results. Each record returns price paid (£GBP), sale date, full address, property type…
- **lookup_postcode** — Convenience: list the most recent HM Land Registry property sales for a single UK postcode (England & Wales). Returns sale price (£GBP), date, address, property type, tenure and new-build flag, newest sale first. Postcode must be UPPERCASE with a space, e.g. "SW1A 1AA".

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "landregistry-uk": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-landregistry-uk"]
  }
}
```

## Documentation

## What the Landregistry Uk MCP server does

The Landregistry Uk MCP server exposes HM Land Registry Price Paid Data through the Model Context Protocol. The underlying records cover individual residential property sales in England and Wales from 1995 onward. Results can include the sale price in pounds sterling, transaction date, full address, property type, tenure, and whether the property was a new build.

This is a property transaction lookup service rather than a general real-estate database. Its data scope is limited to the Price Paid records described above, so it is suited to examining recorded sales rather than listings, valuations, ownership details, or properties outside England and Wales.

## How it works

An MCP-compatible client sends tool calls to either the Pipeworx hosted endpoint or a local process. The hosted pack endpoint is available at `https://gateway.pipeworx.io/landregistry-uk/mcp`. It lists this pack's tools along with shared Pipeworx gateway tools. The full gateway endpoint is also available if an agent needs direct access to other Pipeworx data packs.

The Landregistry Uk MCP server can alternatively run as a local stdio process. In that mode, it responds to MCP `initialize`, `tools/list`, and `tools/call` requests and exposes only the two pack-specific tools. The same tools can also be called through Pipeworx's HTTP API without using an MCP client.

## Setup and configuration

For a hosted connection, add the gateway URL to the MCP client's server configuration. The README gives configurations for Claude Desktop, Cursor, and Windsurf. For local use, run `npx -y @pipeworx/mcp-landregistry-uk` and configure the client with `command: "npx"` and the package as its argument.

The hosted HTTP examples indicate that no account is needed for the first calls. No environment variables are documented as required. Direct HTTP callers can post JSON to endpoints such as `https://gateway.pipeworx.io/v1/tools/search_transactions`.

## Tools and capabilities

- `search_transactions` searches sales records using postcode, town, district, county, minimum and maximum price, and sale-date ranges.
- Results from `search_transactions` can be sorted and paginated, which supports bounded queries over larger result sets.
- `lookup_postcode` returns the most recent recorded sales for one postcode, with newest transactions first.
- Both tools return transaction details including price, date, address, property type, tenure, and new-build status.
- Postcodes must use uppercase letters and include a space, such as `SW1A 1AA`.

## Limitations and notes

The records cover England and Wales only, despite the product's UK name. A postcode lookup is limited to a single UK postcode and requires the specified formatting. The hosted pack endpoint includes shared Pipeworx meta-tools in addition to the listed property tools, while the standalone process does not. `ask_pipeworx` can route natural-language questions through the gateway, but it is not part of the local pack-only process.

Treat those as outside the documented scope.

_Full upstream README: https://allmcps.com/mcp/landregistry-uk/readme_