Japan Real Estate Intel MCP server
not respondingJapan real estate MCP: land price, risk, foot traffic, renovation. 10 prefectures.
1 stars81 downloads/wk
Reviews
Write oneNobody has reviewed Japan Real Estate Intel yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Japan Real Estate Intel tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-11-04 · same rubric, same numbers if you re-run it
- Code scan216 source files scanned25/25
- Live reliabilityremote unreachable: fetch failed0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancerepository not readable: repo not found3/15
- Maintainer identityno repository or website to verify2/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachablefetch failed
How Japan Real Estate Intel compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 49/100
- higher than 9% of 48,243 servers
- Uptime
- 0%
- of our recent checks; the typical remote server answers 100%
- GitHub stars
- 1
- more than 65% of 28,706 servers
- Downloads a week
- 81
- more than 57% of 12,306 servers with a package
Install Japan Real Estate Intel in Claude Code, Cursor or VS Code
claude mcp add --transport http japan-real-estate-intel-mcp https://realestate-mcp.jp/mcp
What the publisher says
From the Japan Real Estate Intel repository's README, as published. We do not edit it. Read it on GitHub
Japan Real Estate Intel MCP
Cross-analyze Japanese real estate data across 10 prefectures via MCP. Land prices, disaster risk, population, foot traffic, education, corporate presence, PLATEAU 3D buildings, renovation yield, and contract support — all accessible through Claude, ChatGPT, Cursor, or any MCP client.
Registry: io.github.sugukurukabe/japan-real-estate-intel-mcp · Growth / listings: docs/growth-playbook.md
Try in 60 seconds (Free tier — safe for demos)
Copy into Claude, Cursor, or ChatGPT after npx @sugukuru/japan-real-estate-intel-mcp:
discover_opportunities で愛知県の investment 向けエリアを探して。limit=5More copy-paste prompts (3 demos, no Pro tools): docs/free-demo-prompts.md Map only: Dashboard (Aichi)
Do not demo PDF reports, Linear numeric sim, or contract tools on the default Free plan — they require Pro. See tiers and pro-demo-setup.md.
Data freshness & trust
Quick Install
Claude Desktop (stdio):
npx @sugukuru/japan-real-estate-intel-mcpClaude Desktop (remote — no login/API key required):
{
"mcpServers": {
"japan-real-estate-intel": {
"url": "https://realestate-mcp.jp/mcp"
}
}
}https://realestate-mcp.jp is an authless public connector — no headers needed. X-Api-Key only applies if you self-host with APIKEY set (see docs/deploy.md); X-License-Key / licenseKey unlocks Pro/Enterprise tiers on any instance (see pro-demo-setup.md) — the two are unrelated.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-11-04downgradeC → Dscore 49: Remote endpoint did not respond
Japan Real Estate Intel: common questions
- Is Japan Real Estate Intel MCP server safe?
- Not recommended: it is graded D (49/100). Read the Japan Real Estate Intel safety report
- How do I install Japan Real Estate Intel?
- It runs remotely at realestate-mcp.jp. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Japan Real Estate Intel need an API key?
- No secret keys are declared. It reads 3 settings from the environment.
- Is Japan Real Estate Intel maintained?
- The last commit was 45 days ago (2026-09-21). The latest release is v6.15.1.
- Is Japan Real Estate Intel up?
- 0% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Japan Real Estate Intel compare with other MCP servers?
- safety score 49/100 (higher than 9% of 48,243 servers); uptime 0% (of our recent checks; the typical remote server answers 100%); github stars 1 (more than 65% of 28,706 servers). Full comparison.