Japan Property Hazard Mcp

io.github.atushi1841Published by GitHub account atushi1841v0.1.5Updated Oct 24, 2026

Japan property hazard Apify:apify.com/fruitful_quintessence | Gumroad:atushi5.gumroad.com/l/kutuxe

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

A local desktop MCP server for Japan property hazard data, pointing to Apify and Gumroad sources; its tools are not documented.

What you can do
  • The listing names no tools, so the assistant-facing capabilities cannot be confirmed.
  • The description and README only point to external data sources: an Apify store page and a Gumroad dataset page.
  • It appears intended to relate Japanese property information to hazard data, but no tool names, inputs or outputs are given.
  • It runs as a local stdio process on the user's machine.
When to use it
Only worth considering if you specifically want Japanese property hazard information and are willing to check the linked Apify and Gumroad sources yourself, since the server's actual tools are undocumented.
Requirements
Runs as a local process over stdio, packaged as an MCP bundle for desktop clients. No authentication, environment variables or headers are declared. Access to the external Apify and Gumroad pages may be needed.
Before you install
The tool set is not documented, so what the assistant can read or change is unknown. The README points to third-party Apify and Gumroad pages, and the Gumroad listing suggests paid datasets; verify costs and data terms before relying on it.

Installation

In SourceWeft

  1. Open Japan Property Hazard Mcp in the dashboard and add it to a workspace.
  2. 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

Data & Store

Source: README.md at commit 9c1dc29

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

3
  1. v0.1.5LatestOct 22, 2026
  2. v0.1.1Oct 18, 2026
  3. v0.1.0Oct 10, 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.