Address To Zip
jp.addresstozipPublished by addresstozip.jpOfficial publisherv1.2.0Updated Oct 24, 2026
日本の住所⇄郵便番号を変換。表記ゆれも吸収。Japan address ⇄ postal code, handles messy input. Free tier, no API key.
Overview
Lets an assistant convert between Japanese addresses and postal codes, tolerating inconsistent input formats.
- What you can do
- This remote MCP server converts Japanese addresses to postal codes and postal codes back to addresses. The description states it absorbs notation variations, so messy or inconsistently formatted input is handled. No individual tools are listed in the manifest, and the description mentions a free tier with no API key.
- When to use it
- Useful when an assistant needs to look up or normalize Japanese postal addresses, for example filling in a postal code from a written address or expanding a postal code into an address. It suits occasional lookups where a hosted service is preferable to maintaining local address data.
- Requirements
- A remote MCP endpoint at over streamable HTTP. No packages, environment variables, headers, or authentication are declared, and the description states there is a free tier with no API key. Network access to the provider is required.
Installation
In SourceWeft
- Open Address To Zip in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. 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/jp.addresstozip%2Faddress-to-zip/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"address-to-zip": {
"type": "http",
"url": "https://addresstozip.jp/mcp"
}
}
}Tools
0Version history
1- v1.2.0LatestSep 16, 2026
Score
17% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 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
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.