mcp-registry/io.github.vikramgorla/swiss/postcode_lookup / alternatives

Live alternatives to mcp-registry/io.github.vikramgorla/swiss/postcode_lookup

The best live alternatives to mcp-registry/io.github.vikramgorla/swiss/postcode_lookup right now are mcp-registry/ch.swisslivingindex/swiss-living-index/search_commune, mcp-registry/io.github.pipeworx-io/postcodes/lookup_postcode, mcp-registry/dev.torify/japanese-locale-mcp/postal_lookup, mcp-registry/io.github.eins78/meteoswiss-mcp/meteoswissLocalForecast, mcp-registry/io.github.pipeworx-io/zippopotam/lookup_city — capability-matched and ranked by current reliability. mcp-registry/io.github.vikramgorla/swiss/postcode_lookup itself is currently "unknown".

alternative	server
mcp-registry/ch.swisslivingindex/swiss-living-index/search_commune	ch.swisslivingindex/swiss-living-index	live status →
mcp-registry/io.github.pipeworx-io/postcodes/lookup_postcode	io.github.pipeworx-io/postcodes	live status →
mcp-registry/dev.torify/japanese-locale-mcp/postal_lookup	dev.torify/japanese-locale-mcp	live status →
mcp-registry/io.github.eins78/meteoswiss-mcp/meteoswissLocalForecast	io.github.eins78/meteoswiss-mcp	live status →
mcp-registry/io.github.pipeworx-io/zippopotam/lookup_city	io.github.pipeworx-io/zippopotam	live status →
mcp-registry/io.github.pipeworx-io/zippopotam/lookup_zipcode	io.github.pipeworx-io/zippopotam	live status →
mcp-registry/io.github.paulieb89/property-shared/planning_lookup	io.github.paulieb89/property-shared	live status →
mcp-registry/ch.opencaselaw/swiss-caselaw/get_law	ch.opencaselaw/swiss-caselaw	live status →
mcp-registry/io.github.pipeworx-io/postcodes/random_postcode	io.github.pipeworx-io/postcodes	live status →
mcp-registry/ch.immoswipe/immoswipe-ai/search_listings	ch.immoswipe/immoswipe-ai	live status →

FAQ

What is the best alternative to mcp-registry/io.github.vikramgorla/swiss/postcode_lookup?

mcp-registry/ch.swisslivingindex/swiss-living-index/search_commune is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/postcodes/lookup_postcode, mcp-registry/dev.torify/japanese-locale-mcp/postal_lookup, mcp-registry/io.github.eins78/meteoswiss-mcp/meteoswissLocalForecast, mcp-registry/io.github.pipeworx-io/zippopotam/lookup_city. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.vikramgorla/swiss/postcode_lookup down right now?

mcp-registry/io.github.vikramgorla/swiss/postcode_lookup's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.vikramgorla%2Fswiss%2Fpostcode_lookup.

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.vikramgorla%2Fswiss%2Fpostcode_lookup or MCP find_alternatives. Check mcp-registry/io.github.vikramgorla/swiss/postcode_lookup's live status: https://glimind.com/tool/mcp-registry/io.github.vikramgorla/swiss/postcode_lookup.