Japan Real Estate Market Data

io.github.KoumeKoubouPublished by GitHub account KoumeKoubouv1.0.0Updated Oct 27, 2026

Japan real estate data: transactions, land prices, vacancy, hazard, zoning & more.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server giving assistants access to Japanese real estate data such as transactions, land prices, vacancy, hazard and zoning.

What you can do
  • Look up Japanese real estate market data through a hosted endpoint.
  • Coverage named in the description includes property transactions, land prices, vacancy, hazard information and zoning.
  • No individual tools are listed, so the exact queries and output formats are not documented here.
When to use it
Useful when you need Japanese property or land market context — comparing transaction and land price data, checking hazard or zoning details, or researching vacancy — without building your own data pipeline.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. Authentication is OAuth and required, so the client must support the OAuth flow. No environment variables or headers are declared.
Before you install
Access requires an OAuth sign-in, so the server receives account identity information. The data is informational market and hazard information and should not be treated as legal, valuation or safety advice. No tool list is published, so what the server can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Japan Real Estate Market Data in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.KoumeKoubou%2Fjapan-realestate/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "japan-real-estate-market-data": {
      "type": "http",
      "url": "https://mcp-server-japan-realestate.x7k9m.workers.dev/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.