mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_recent_changes / alternatives

Live alternatives to mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_recent_changes

The best live alternatives to mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_recent_changes right now are mcp-registry/io.github.pipeworx-io/landprice/landprice_points, mcp-registry/io.github.paulieb89/uk-due-diligence-mcp/land_title_search, mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/forecast_land_price_trend, mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/get_real_estate_macro_snapshot, mcp-registry/io.github.n-3inc/reinfo/reinfolib-real-estate-price — capability-matched and ranked by current reliability. mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_recent_changes itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/landprice/landprice_points	io.github.pipeworx-io/landprice	live status →
mcp-registry/io.github.paulieb89/uk-due-diligence-mcp/land_title_search	io.github.paulieb89/uk-due-diligence-mcp	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.sugukurukabe/japan-real-estate-intel-mcp/get_real_estate_macro_snapshot	io.github.sugukurukabe/japan-real-estate-intel-mcp	live status →
mcp-registry/io.github.n-3inc/reinfo/reinfolib-real-estate-price	io.github.n-3inc/reinfo	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.paulieb89/property-shared/ppd_transactions	io.github.paulieb89/property-shared	live status →
mcp-registry/io.github.pipeworx-io/landregistry-uk/search_transactions	io.github.pipeworx-io/landregistry-uk	live status →
mcp-registry/io.github.pipeworx-io/landregistry-uk/lookup_postcode	io.github.pipeworx-io/landregistry-uk	live status →
mcp-registry/io.tooloracle/priceoracle/price_history	io.tooloracle/priceoracle	live status →
mcp-registry/dev.infranode/infranode/land_values	dev.infranode/infranode	live status →
mcp-registry/io.github.mirabello-consultancy/mcp-server/get_availability_updates	io.github.mirabello-consultancy/mcp-server	live status →

FAQ

What is the best alternative to mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_recent_changes?

mcp-registry/io.github.pipeworx-io/landprice/landprice_points is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.paulieb89/uk-due-diligence-mcp/land_title_search, mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/forecast_land_price_trend, mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/get_real_estate_macro_snapshot, mcp-registry/io.github.n-3inc/reinfo/reinfolib-real-estate-price. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_recent_changes down right now?

mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_recent_changes's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.mcp-revenue-empire%2Fjapan-public-ledgers%2Flandprice_watch_recent_changes.

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%2Fcom.mcp-revenue-empire%2Fjapan-public-ledgers%2Flandprice_watch_recent_changes or MCP find_alternatives. Check mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_recent_changes's live status: https://glimind.com/tool/mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/landprice_watch_recent_changes.