mcp-registry/io.github.pipeworx-io/geonames/find_postal_codes / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/geonames/find_postal_codes

The best live alternatives to mcp-registry/io.github.pipeworx-io/geonames/find_postal_codes right now are mcp-registry/io.github.pipeworx-io/zippopotam/lookup_zipcode, mcp-registry/com.dfetcher/vitamin-d/geocode, mcp-registry/io.github.pipeworx-io/zippopotam/lookup_city, mcp-registry/io.github.lazymac2x/govdata-korea/lookup_postal_code, mcp-registry/io.github.colinhughes2121/gocreative-agent-api/lookup_postal — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/geonames/find_postal_codes itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/zippopotam/lookup_zipcode	io.github.pipeworx-io/zippopotam	live status →
mcp-registry/com.dfetcher/vitamin-d/geocode	com.dfetcher/vitamin-d	live status →
mcp-registry/io.github.pipeworx-io/zippopotam/lookup_city	io.github.pipeworx-io/zippopotam	live status →
mcp-registry/io.github.lazymac2x/govdata-korea/lookup_postal_code	io.github.lazymac2x/govdata-korea	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/lookup_postal	io.github.ColinHughes2121/gocreative-agent-api	live status →
mcp-registry/io.github.pipeworx-io/open-meteo/geocode	io.github.pipeworx-io/open-meteo	live status →
mcp-registry/io.github.pipeworx-io/geo/reverse_geocode	io.github.pipeworx-io/geo	live status →
mcp-registry/io.github.pipeworx-io/postcodes/lookup_postcode	io.github.pipeworx-io/postcodes	live status →
mcp-registry/io.github.pipeworx-io/geoapify/geocode	io.github.pipeworx-io/geoapify	live status →
mcp-registry/dev.torify/japanese-locale-mcp/torify_postal.lookup	dev.torify/japanese-locale-mcp	live status →
pulsemcp/adbutler/get_postal_code_target	AdButler	live status →
mcp-registry/com.adbutler/mcp-server/get_postal_code_target	com.adbutler/mcp-server	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/geonames/find_postal_codes?

mcp-registry/io.github.pipeworx-io/zippopotam/lookup_zipcode is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.dfetcher/vitamin-d/geocode, mcp-registry/io.github.pipeworx-io/zippopotam/lookup_city, mcp-registry/io.github.lazymac2x/govdata-korea/lookup_postal_code, mcp-registry/io.github.colinhughes2121/gocreative-agent-api/lookup_postal. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/geonames/find_postal_codes down right now?

mcp-registry/io.github.pipeworx-io/geonames/find_postal_codes's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fgeonames%2Ffind_postal_codes.

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%2Fio.github.pipeworx-io%2Fgeonames%2Ffind_postal_codes or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/geonames/find_postal_codes's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/geonames/find_postal_codes.