Japan Address & Geocoding
REMOTE · JUSHO-MCP.EASAKURA.WORKERS.DEV · 2 COMPONENTS · SCANNED AUG 3
Japanese address search and geocoding (official address registry): postal codes and coordinates.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 258 tokens (~86/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · jusho-mcp.easakura.workers.dev
claude mcp add --transport http easakura-japan-address-geocoding-mcp https://jusho-mcp.easakura.workers.dev/sse
[mcp_servers.easakura-japan-address-geocoding-mcp] url = "https://jusho-mcp.easakura.workers.dev/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"easakura-japan-address-geocoding-mcp": {
"type": "remote",
"url": "https://jusho-mcp.easakura.workers.dev/sse",
"enabled": true
}
}
} openclaw mcp add easakura-japan-address-geocoding-mcp --url https://jusho-mcp.easakura.workers.dev/sse --transport streamable-http
mcp_servers:
easakura-japan-address-geocoding-mcp:
url: "https://jusho-mcp.easakura.workers.dev/sse" {
"mcpServers": {
"easakura-japan-address-geocoding-mcp": {
"type": "http",
"url": "https://jusho-mcp.easakura.workers.dev/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://jusho-mcp.easakura.workers.dev/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=easakura.workers.dev | CN=WE1,O=Google Trust Services,C=US | 13 Jul 2026 | 11 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 997e95d4e676a1e20e6b46db6f16ffd5 |
| SANs: easakura.workers.dev, *.easakura.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of jusho-mcp.easakura.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://jusho-mcp.easakura.workers.dev/sse | Verified | 200 | |
| http (plaintext) | http://jusho-mcp.easakura.workers.dev/sse | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
geocode_address 住所から緯度経度を取得（ジオコーディング） ~94
日本の住所文字列から緯度経度と正規化された住所表記を取得する（国土地理院公式）。地図表示・距離計算・配送エリア判定などに使う。
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 住所（例: 東京都千代田区丸の内1-9-1） |
| max_results | integer | — | 最大件数 |
No output schema declared.
No examples provided.
reverse_geocode 緯度経度から住所を取得（逆ジオコーディング） ~78
緯度経度から日本の住所（都道府県・市区町村・町丁目）を取得する（国土地理院公式）。
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | 緯度（例: 35.681236） |
| longitude | number | yes | 経度（例: 139.767125） |
No output schema declared.
No examples provided.
zipcode_to_address 郵便番号から住所を取得 ~86
日本の郵便番号（7桁）から住所（都道府県・市区町村・町域、ふりがな付き）を取得する。フォーム入力支援・住所データクレンジングに使う。
| Name | Type | Req | Description |
|---|---|---|---|
| zipcode | string | yes | 郵便番号（例: 100-0001 または 1000001） |
No output schema declared.
No examples provided.