Skip to main content
Glama
Sign In
jp-address-mcp

jp-address-mcp

by MasaBigBrother
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Japanese Address Normalizer & Verifier (MCP Server)

An MCP server that normalizes and verifies Japanese postal addresses. Splits messy Japanese address strings (full-width characters, mixed hyphens, romaji, building/room names) into structured fields, with a verification flag and lat/lng.

Built for AI agents doing cross-border commerce, logistics, or CRM involving Japan.

Endpoint (remote, no install)

Streamable HTTP:https://jp-addr.streamfront.net/mcp

Related MCP server: mcp-server-zipcode-jp

Tool

normalize_jp_address

Structure & verify a raw Japanese address string.

Input: { "address": "東京都新宿区西新宿2-8-1 パークタワー1503号" }

Output (example):

{
  "ok": true,
  "normalized": {
    "pref": "東京都", "city": "新宿区", "town": "西新宿二丁目",
    "banchi": "8-1", "building": "パークタワー", "room": "1503"
  },
  "geo": { "lat": 35.68945, "lng": 139.691774 },
  "level": 3, "verified": true
}

How it works

Wraps the open-source @geolonia/normalize-japanese-addresses engine and adds a preprocessing/structuring layer: full-width→half-width, hyphen normalization, chome/banchi boundary detection via engine metadata, building & room separation, and a verification flag.

Status

Early. Single tool. Tested mainly on residential/urban addresses. Feedback welcome.

Registry

Published to the official MCP Registry as net.streamfront/jp-address.

Available Tools

1 tool
normalize_jp_addressA

Normalize and verify a Japanese postal address. Splits a raw Japanese address string into structured fields (prefecture, city, town, block number, building, room) and returns a verification flag plus lat/lng. Handles messy input: full-width chars, mixed hyphens, romaji, and building/room separation that generic parsers miss. Use whenever you need to register, validate, or route a Japanese address reliably.

Inputs: address (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion. The tool's purpose is unambiguous and clearly described.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern (normalize_jp_address), which is predictable and consistent with common conventions.

    Tool Count3/5

    With only one tool, the server feels minimal for a dedicated address utility. It earns its place, but the scope is thin and borderline.

    Completeness5/5

    The tool consolidates parsing, verification, and geocoding into one operation, covering the full address normalization workflow. There are no obvious gaps for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers