
Japan Rent Market Mcp
io.github.atushi1841Published by GitHub account atushi1841v1.0.0Updated Nov 2, 2026
Japan rental prices SUUMO/at_home/LIFULL cross-shop via Apify
Overview
Local MCP server that scrapes Tokyo 23-ward rental listings from SUUMO, at home and LIFULL HOME'S via Apify for cross-portal rent comparison.
- What you can do
- Collect rental listings for a chosen Tokyo 23 ward from SUUMO, at home and optionally LIFULL HOME'S, with limits on items and pages per source.
- Return structured listing data: rent, management fee, deposit, layout, area, floor, address, stations and walking distance, building age and listing URL.
- Tag each item with its source and shop so the same station or layout can be compared across portals.
- Optionally route requests through an Apify proxy configuration.
- When to use it
- Useful when researching Tokyo rents, comparing the same station or layout across Japan's three main property portals, planning a move to Japan, or tracking ward-level rent trends over repeated runs.
- Requirements
- Runs as a local process (stdio) on the user's machine, packaged as an MCP bundle; the README also shows a Python launch command. Scraping is backed by an Apify actor, so an Apify account and its credentials are needed, and network access is required. No environment variables or headers are declared in the manifest.
Installation
In SourceWeft
- Open Japan Rent Market Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Japan Rent Market — 3-Site Cross-Shop Comparison (SUUMO + at home + LIFULL HOME'S)
Compare Tokyo 23-ward rental prices across Japan's top 3 property portals in a single dataset.
Scrapes rental listings from SUUMO (スーモ) — Japan's #1 property portal — at home (アットホーム) — the #2 portal — and LIFULL HOME'S (ホームズ) — the #3 portal. Each item is tagged with its source so you can compare rent for the same station/layout across portals.
Why this is useful
- Cross-portal price comparison — the same 1DK near Shibuya station often differs by 5-20% between portals
- Market research — track Tokyo rent trends by ward over time
- Relocation planning — find the best-priced listing before moving to Japan
- Investment analysis — identify underpriced/overpriced areas
Input
Output Sample
The source + shop fields let you compare the same station/layout across portals.
Use Cases
- Cross-portal arbitrage — find the same building listed cheaper on another portal
- Rent trend tracking — schedule daily runs to monitor ward-level rent movements
- Relocation research — one dataset covering all 3 major portals
Pricing
Pay-per-event — $0.00005/run start + $0.002/item.
Data Source
Public rental listings from SUUMO, at home, and LIFULL HOME'S (address, rent, layout, area, station distance).
Connect
Connect to your workflow via Apify Connectors: Google Sheets, Slack, or webhooks — automate rent monitoring without code.
Related Actors
This actor is part of the fruitful_quintessence Apify suite. Datasets in the same category are available from sibling actors:
- suumo-japan-real-estate-scraper — Scrapes rental and used-condo sale listings from SUUMO (スーモ), Japan's #1 property portal.
- japan-property-market-scraper — Used condo sale price comparison across SUUMO and at home.
- japan-kakaku-price-search — Price.com.jp search: product name, lowest price, shop count & review score.
See the full suite on the Apify profile.
MCP Server & Registry
This scraper is also available as an MCP server for AI agents:
- MCP Registry:
io.github.atushi1841/japan-rent-market-mcp - Apify Store: https://apify.com/fruitful_quintessence/japan-rent-market-scraper
- Gumroad: https://atushi5.gumroad.com/l/kutuxe
Install via MCP: add to your MCP config:
Smithery
Install via Smithery:
Source: README.md at commit 60061b8
Tools
0Version history
1- v1.0.0LatestOct 19, 2026
Score
40% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.