
Japan Real Estate Intel
io.github.sugukurukabePublished by GitHub account sugukurukabev6.15.1Updated Oct 24, 2026
Japan real estate MCP: land price, risk, foot traffic, renovation. 10 prefectures.
Overview
Lets an assistant look up Japanese real estate data such as land prices, risk, foot traffic and renovation information across ten prefectures.
- What you can do
- This server exposes Japanese real estate intelligence to an assistant, covering land price, risk, foot traffic and renovation topics across ten prefectures. It can be reached as a remote HTTP endpoint or run locally as an npm package over stdio. The registry description names those four data areas but does not list individual tools.
- When to use it
- Worth adding when an assistant needs Japanese property context, for example comparing land prices or checking risk and foot traffic for an area. It is aimed at users working with real estate in the ten prefectures it covers.
- Requirements
- Either a remote endpoint at the provider's site or a local Node.js runtime to run the npm package with npx. Optional API_KEY for HTTP mode authentication, plus ESTAT_APP_ID for the e-Stat government statistics API and MLIT_API_KEY for the MLIT Real Estate Information Library API for live transaction data. Network access is needed for the remote endpoint and the upstream APIs.
Installation
In SourceWeft
- Open Japan Real Estate Intel in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.sugukurukabe%2Fjapan-real-estate-intel-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"japan-real-estate-intel": {
"type": "http",
"url": "https://realestate-mcp.jp/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v6.15.1LatestSep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.