mcp-registry/jp.addresstozip/address-to-zip/lookup_zipcode / alternatives

Live alternatives to mcp-registry/jp.addresstozip/address-to-zip/lookup_zipcode

The best live alternatives to mcp-registry/jp.addresstozip/address-to-zip/lookup_zipcode right now are pulsemcp/address-to-zip/lookup_zipcode, pulsemcp/address-to-zip/search_address, mcp-registry/io.github.pipeworx-io/zippopotam/lookup_zipcode, mcp-registry/dev.torify/japanese-locale-mcp/torify_postal.lookup, mcp-registry/dev.torify/japanese-locale-mcp/postal.lookup — capability-matched and ranked by current reliability. mcp-registry/jp.addresstozip/address-to-zip/lookup_zipcode itself is currently "healthy".

alternative	server
pulsemcp/address-to-zip/lookup_zipcode	Address to Zip	live status →
pulsemcp/address-to-zip/search_address	Address to Zip	live status →
mcp-registry/io.github.pipeworx-io/zippopotam/lookup_zipcode	io.github.pipeworx-io/zippopotam	live status →
mcp-registry/dev.torify/japanese-locale-mcp/torify_postal.lookup	dev.torify/japanese-locale-mcp	live status →
mcp-registry/dev.torify/japanese-locale-mcp/postal.lookup	dev.torify/japanese-locale-mcp	live status →
mcp-registry/io.github.andrew-sondgeroth/zipexplore-mcp/reverse_geocode	io.github.andrew-sondgeroth/zipexplore-mcp	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/lookup_zip	io.github.ColinHughes2121/gocreative-agent-api	live status →
mcp-registry/com.dfetcher/vitamin-d/geocode	com.dfetcher/vitamin-d	live status →
mcp-registry/work.latlng.mcp/latlng/reverse_geocode	work.latlng.mcp/latlng	live status →
mcp-registry/io.github.pipeworx-io/geonames/find_postal_codes	io.github.pipeworx-io/geonames	live status →
mcp-registry/io.github.pipeworx-io/geoapify/reverse_geocode	io.github.pipeworx-io/geoapify	live status →
mcp-registry/io.github.pipeworx-io/tomtom/reverse_geocode	io.github.pipeworx-io/tomtom	live status →

FAQ

What is the best alternative to mcp-registry/jp.addresstozip/address-to-zip/lookup_zipcode?

pulsemcp/address-to-zip/lookup_zipcode is the top capability-matched alternative that's live right now. Other options: pulsemcp/address-to-zip/search_address, mcp-registry/io.github.pipeworx-io/zippopotam/lookup_zipcode, mcp-registry/dev.torify/japanese-locale-mcp/torify_postal.lookup, mcp-registry/dev.torify/japanese-locale-mcp/postal.lookup. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/jp.addresstozip/address-to-zip/lookup_zipcode down right now?

mcp-registry/jp.addresstozip/address-to-zip/lookup_zipcode's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fjp.addresstozip%2Faddress-to-zip%2Flookup_zipcode.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fjp.addresstozip%2Faddress-to-zip%2Flookup_zipcode or MCP find_alternatives. Check mcp-registry/jp.addresstozip/address-to-zip/lookup_zipcode's live status: https://glimind.com/tool/mcp-registry/jp.addresstozip/address-to-zip/lookup_zipcode.