Realestate logo

Realestate

Queries Japan’s reported real-estate transactions and resolves municipality codes through MLIT data.

Install Realestate

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "realestate": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-realestate"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Realestate MCP server queries reported Japanese residential and commercial transaction data from MLIT’s 不動産情報ライブラリ. It can filter transactions by prefecture, municipality, station, year, and quarter, then return fields such as price, area, building year, structure, and use. A separate tool lists cities and wards with five-digit municipality codes for building precise queries. Use it for Japan housing-market research, especially when comparing sales in a prefecture, city, or ward.

Use cases

  • Compare reported home prices across Japanese prefectures
  • Find sales in a Tokyo ward for a selected quarter
  • Resolve municipality codes before querying transactions
  • Inspect commercial property prices by area and period

Key features

  • Reported Japanese residential and commercial transactions
  • Prefecture, municipality, station, year, and quarter filters
  • Municipality and ward code lookup
  • Transaction price, area, structure, and use fields
  • Remote gateway and local stdio access

Tools2

What Realestate lets your agent do. Expand a tool for its parameters.

Self-reported~155 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 47d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @pipeworx/mcp-realestate (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads473Package downloads in the last 30 days.
Last commit27d agoMost recent push to the default branch.
Tools exposed2Callable tools this server registers over MCP.

How Realestate works

What Realestate MCP server does

The Realestate MCP server exposes two tools for researching reported property transactions in Japan. Its data comes from the Ministry of Land, Infrastructure, Transport and Tourism’s 不動産情報ライブラリ. The transaction tool covers residential and commercial deals, including agreed or contract prices available from 2021 onward.

Results can include transaction type, district, total trade price, property area, price per unit, building construction year, structure, and intended use. The available transaction history begins in the third quarter of 2005. Agreed-price coverage begins in the first quarter of 2021.

How it works

realestate_transactions accepts geographic and time filters. You can provide a Japanese prefecture by name or code, narrow the request with a municipality or station code, and select a year and quarter. This makes the tool suitable for questions about sale prices in places such as Tokyo, Osaka, or a particular Japanese ward.

realestate_municipalities returns the cities or wards in a selected prefecture together with their five-digit municipality codes. Use it before a transaction query when you know a place name but need the code required for a more specific search. The prefecture can be supplied by name or by its two-digit code from 01 through 47.

Setup and configuration

The Realestate MCP server is available through the Pipeworx gateway or as a local package. For a remote MCP connection, configure an MCP client with:

config.json
{
  "mcpServers": {
    "realestate": {
      "url": "https://gateway.pipeworx.io/realestate/mcp"
    }
  }
}

The scoped gateway endpoint lists the two Realestate tools along with shared Pipeworx meta-tools. The gateway’s ask_pipeworx tool can route plain-language questions to tools across the catalog. Alternatively, connect to https://gateway.pipeworx.io/mcp for the full gateway.

For a local stdio connection, run the package with npx -y @pipeworx/mcp-realestate and configure the client with that command and package argument. The local mode serves only this pack’s tools and does not add the gateway meta-tools. The HTTP tools can also be called directly through the gateway’s /v1/tools/realestate_transactions endpoint.

Tools and capabilities

  • realestate_transactions: Retrieves reported Japanese property transactions, with filters for prefecture, municipality, station, year, and quarter.
  • realestate_municipalities: Resolves the cities and wards within a prefecture and provides their five-digit municipality codes.
  • Transaction records may expose property type, district, price, area, unit price, building age information, structure, and use.

Limitations and notes

The Realestate MCP server focuses on Japanese transaction data from the named MLIT source. Its transaction coverage starts at 2005-Q3, while agreed or contract prices are available from 2021-Q1. The gateway endpoint currently includes shared tools in addition to the pack’s tools; its initialize response is the authoritative source for the exact scope shown on a given day.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Realestate

Realestate is an MCP server that connects AI clients to Japan’s MLIT 不動産情報ライブラリ for reported residential and commercial transaction data. Its main tools, realestate_transactions and realestate_municipalities, retrieve filtered prices and resolve Japanese municipality codes for prefecture and city-level searches.

Run `npx -y @pipeworx/mcp-realestate` for a local stdio server, or add the Pipeworx MCP URL to your client configuration. The remote endpoint is `https://gateway.pipeworx.io/realestate/mcp`, while the local package does not require a gateway account.

Yes, Realestate works with Cursor through its MCP configuration. Add the remote gateway URL as an MCP server, or configure Cursor to launch `npx -y @pipeworx/mcp-realestate` locally over stdio.

Reported transactions are available from 2005-Q3 onward, while agreed or contract prices are available from 2021-Q1 onward. Queries can be narrowed to a specific year and quarter.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRealestate AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/realestate?style=directory)](https://allmcps.com/mcp/realestate)
HTML Embed
<a href="https://allmcps.com/mcp/realestate"><img src="https://allmcps.com/api/badge/realestate?style=directory" alt="Realestate on AllMCPs" /></a>