jp.addresstozip/address-to-zip
REMOTE · ADDRESSTOZIP.JP · SCANNED SEP 21
日本の住所⇄郵便番号を変換。表記ゆれも吸収。Japan address ⇄ postal code, handles messy input. Free tier, no API key.
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 → Why this is hard to score →
Endpoint Security63
- 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 2 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 512 tokens (~256/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the jp.addresstozip/address-to-zip MCP server?
jp.addresstozip/address-to-zip is a hosted endpoint at https://addresstozip.jp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · addresstozip.jp
claude mcp add --transport http jp-addresstozip-address-to-zip 'https://addresstozip.jp/mcp'
{
"mcpServers": {
"jp-addresstozip-address-to-zip": {
"url": "https://addresstozip.jp/mcp"
}
}
} {
"servers": {
"jp-addresstozip-address-to-zip": {
"type": "http",
"url": "https://addresstozip.jp/mcp"
}
}
} [mcp_servers.jp-addresstozip-address-to-zip] url = "https://addresstozip.jp/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jp-addresstozip-address-to-zip": {
"type": "remote",
"url": "https://addresstozip.jp/mcp",
"enabled": true
}
}
} openclaw mcp add jp-addresstozip-address-to-zip --url 'https://addresstozip.jp/mcp' --transport streamable-http
mcp_servers:
jp-addresstozip-address-to-zip:
url: "https://addresstozip.jp/mcp" {
"McpServers": {
"jp-addresstozip-address-to-zip": {
"Transport": "http",
"Url": "https://addresstozip.jp/mcp"
}
}
} assistant mcp add jp-addresstozip-address-to-zip -t streamable-http -u 'https://addresstozip.jp/mcp'
{
"mcpServers": {
"jp-addresstozip-address-to-zip": {
"type": "http",
"url": "https://addresstozip.jp/mcp"
}
}
} 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.
- 9 Sept 26 −3
- The server rewrote its instructions, which are the text every model session reads security
- Tool “lookup_zipcode” rewrote its description, which is the text the model reads security
- Tool “search_address” rewrote its description, which is the text the model reads security
- Schema quality: 156 → 256 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- “lookup_zipcode” reworded the description of “zipcode” cosmetic
- “search_address” reworded the description of “address” cosmetic
- “search_address” reworded the description of “limit” cosmetic
- 26 Aug 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
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- 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 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- 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 0
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 21 Sept 2026 · Probed https://addresstozip.jp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=addresstozip.jp | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 36104d0b8cc1c1511366cd8a4923e31a |
| SANs: addresstozip.jp, *.addresstozip.jp | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of addresstozip.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| addresstozip.jp. | 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 | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; img-src 'self' data: https://*.googletagmanager.com https://*.google-analytics.com https://*.clarity.ms https://c.bing.com; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com https://static.cloudflareinsights.com https://*.googletagmanager.com https://*.clarity.ms; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; frame-src https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com https://cloudflareinsights.com https://*.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com https://analytics.google.com https://*.clarity.ms https://c.bing.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://addresstozip.jp/mcp | Verified | 200 | |
| http (plaintext) | http://addresstozip.jp/mcp | HTTPS enforced | 301 | https://addresstozip.jp/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lookup_zipcode ~163
郵便番号から住所を逆引きする。100-0005 または 1000005 形式に対応(全角数字・ハイフン有無は不問)。結果には日本郵便準拠のローマ字表記(romaji)を含む。 / Reverse lookup: get the Japanese address for a postal code. Accepts 100-0005 or 1000005 (full-width digits and missing hyphens are fine). Results include Japan Post romaji.
| Name | Type | Req | Description |
|---|---|---|---|
| zipcode | string | yes | 郵便番号(例: 100-0005 または 1000005。全角数字・ハイフン有無も可) / Japanese postal code, 7 digits. |
No output schema declared.
No examples provided.
search_address ~218
日本の住所文字列から郵便番号を検索する。番地・建物名付きでも町名まで解釈する。ローマ字・英語表記(例: Marunouchi, Chiyoda-ku, Tokyo)でも検索可。結果には日本郵便準拠のローマ字表記(romaji)を含む。 / Look up a Japanese postal code from an address string. Tolerates messy input (full-width digits, hyphen variants, street numbers and building names) and resolves down to the town level. Romaji/English input is accepted. Results include Japan Post romaji.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 検索する住所(例: 東京都千代田区丸の内 / Marunouchi, Chiyoda-ku, Tokyo) / Japanese address to look up. |
| limit | integer | – | 返却件数の上限(1-50・既定10) / Max results (1-50, default 10). |
No output schema declared.
No examples provided.
What is the jp.addresstozip/address-to-zip MCP server?
jp.addresstozip/address-to-zip is an MCP server listed in the public MCP registry as jp.addresstozip/address-to-zip. 日本の住所⇄郵便番号を変換。表記ゆれも吸収。Japan address ⇄ postal code, handles messy input. Free tier, no API key. This page covers its hosted endpoint (https://addresstozip.jp/mcp).
Is the jp.addresstozip/address-to-zip MCP server safe to use?
jp.addresstozip/address-to-zip scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the jp.addresstozip/address-to-zip MCP server expose?
jp.addresstozip/address-to-zip exposes 2 tools: search_address, lookup_zipcode. Their descriptions and schemas cost roughly 381 tokens of context every time the server is loaded.
Does the jp.addresstozip/address-to-zip MCP server require authentication?
No. We connected to jp.addresstozip/address-to-zip without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the jp.addresstozip/address-to-zip MCP server still maintained?
jp.addresstozip/address-to-zip is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.