Liveability MCP

io.github.whitepepper355Published by GitHub account whitepepper355v1.4.0Updated Oct 24, 2026

Liveability scoring for Japanese addresses: shopping, medical, transit, education, nature, safety.

VerifiedSSEWeb executableLocation & Lifestyle

Overview

AI-generated overview

Scores Japanese addresses for liveability across shopping, medical, transit, education, nature and safety.

What you can do
Score a Japanese address for overall liveability and its component categories: shopping, medical care, transit, education, nature and safety.
When to use it
Useful when comparing Japanese neighborhoods or addresses for relocation, property research, or assessing how well served a location is. It is specific to Japan. No tool list was provided, so confirm the exact operations before installing. It is a hosted service reached over SSE, so it needs network access and a valid key. The key is sent as the X-API-Key header; keep it private and check the provider's usage terms. No tool list was provided, so confirm the exact operations before installing. It
Requirements
A remote SSE endpoint at the provider's site, plus an API key supplied in the X-API-Key header. The key is obtained through the provider's signup page.
Before you install
Requires an API key sent in the X-API-Key header; the key is obtained from the provider's signup page, so treat it as a secret and check the provider's terms and any usage limits before relying on it.

Installation

In SourceWeft

  1. Open Liveability MCP in the dashboard and add it to a workspace.
  2. Connect X-API-Key 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 SSE. 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.whitepepper355%2Fliveability-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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "liveability": {
      "type": "sse",
      "url": "https://liveability.jp/mcp/sse",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.4.0LatestSep 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.