mcp-registry/io.github.pipeworx-io/landprice/landprice_points / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/landprice/landprice_points

The best live alternatives to mcp-registry/io.github.pipeworx-io/landprice/landprice_points right now are mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_search, mcp-registry/io.github.pipeworx-io/realestate/realestate_transactions, mcp-registry/dev.infranode/infranode/land_values, mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/forecast_land_price_trend, mcp-registry/io.github.keibai-hub/keibai-hub-mcp/search_auctions — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/landprice/landprice_points itself is currently "healthy".

alternative	server
mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_search	com.mcp-revenue-empire/japan-public-ledgers	live status →
mcp-registry/io.github.pipeworx-io/realestate/realestate_transactions	io.github.pipeworx-io/realestate	live status →
mcp-registry/dev.infranode/infranode/land_values	dev.infranode/infranode	live status →
mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/forecast_land_price_trend	io.github.sugukurukabe/japan-real-estate-intel-mcp	live status →
mcp-registry/io.github.keibai-hub/keibai-hub-mcp/search_auctions	io.github.keibai-hub/keibai-hub-mcp	live status →
mcp-registry/io.github.n-3inc/reinfo/reinfolib-real-estate-price	io.github.n-3inc/reinfo	live status →
mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_recent_changes	com.mcp-revenue-empire/japan-public-ledgers	live status →
mcp-registry/dev.torify/japanese-locale-mcp/geo.geocode	dev.torify/japanese-locale-mcp	live status →
mcp-registry/io.github.ogasurfproject-jpg/horizon-shield/get_price_range	io.github.ogasurfproject-jpg/horizon-shield	live status →
mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/get_real_estate_macro_snapshot	io.github.sugukurukabe/japan-real-estate-intel-mcp	live status →
mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_get	com.mcp-revenue-empire/japan-public-ledgers	live status →
mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/cross_analyze_real_estate_market	io.github.sugukurukabe/japan-real-estate-intel-mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/landprice/landprice_points?

mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_search is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/realestate/realestate_transactions, mcp-registry/dev.infranode/infranode/land_values, mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/forecast_land_price_trend, mcp-registry/io.github.keibai-hub/keibai-hub-mcp/search_auctions. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/landprice/landprice_points down right now?

mcp-registry/io.github.pipeworx-io/landprice/landprice_points's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Flandprice%2Flandprice_points.

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%2Flandprice%2Flandprice_points or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/landprice/landprice_points's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/landprice/landprice_points.