mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/evaluate_store_location / alternatives

Live alternatives to mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/evaluate_store_location

The best live alternatives to mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/evaluate_store_location right now are mcp-registry/io.github.kingbbs/yiditu-mcp/analyze_location, mcp-registry/io.github.n-3inc/reinfo/reinfolib-city-list, mcp-registry/io.github.localgov-jp/mcp-server/compare_municipal_subsidies, mcp-registry/io.github.mcflamingo/local-intel/local_intel_compare, mcp-registry/house.bim/bimhouse/match_contractors — capability-matched and ranked by current reliability. mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/evaluate_store_location itself is currently "healthy".

alternative	server
mcp-registry/io.github.kingbbs/yiditu-mcp/analyze_location	io.github.kingbbs/yiditu-mcp	live status →
mcp-registry/io.github.n-3inc/reinfo/reinfolib-city-list	io.github.n-3inc/reinfo	live status →
mcp-registry/io.github.localgov-jp/mcp-server/compare_municipal_subsidies	io.github.localgov-jp/mcp-server	live status →
mcp-registry/io.github.mcflamingo/local-intel/local_intel_compare	io.github.MCFLAMINGO/local-intel	live status →
mcp-registry/house.bim/bimhouse/match_contractors	house.bim/bimhouse	live status →
mcp-registry/io.github.pipeworx-io/landprice/landprice_points	io.github.pipeworx-io/landprice	live status →
mcp-registry/io.github.n-3inc/kkj/kkj-search	io.github.n-3inc/kkj	live status →
mcp-registry/net.settro/sales-team/assess_social_ordering_readiness	net.settro/sales-team	live status →
mcp-registry/com.webotee/amazon-product-research-mcp/evaluate_brand	com.webotee/amazon-product-research-mcp	live status →
mcp-registry/io.github.laundromatic/shopgraph/score_product	io.github.laundromatic/shopgraph	live status →
mcp-registry/com.partstable/partstable/score-listing	com.partstable/partstable	live status →
mcp-registry/io.github.pipeworx-io/realestate/realestate_municipalities	io.github.pipeworx-io/realestate	live status →

FAQ

What is the best alternative to mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/evaluate_store_location?

mcp-registry/io.github.kingbbs/yiditu-mcp/analyze_location is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.n-3inc/reinfo/reinfolib-city-list, mcp-registry/io.github.localgov-jp/mcp-server/compare_municipal_subsidies, mcp-registry/io.github.mcflamingo/local-intel/local_intel_compare, mcp-registry/house.bim/bimhouse/match_contractors. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/evaluate_store_location down right now?

mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/evaluate_store_location's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.sugukurukabe%2Fjapan-real-estate-intel-mcp%2Fevaluate_store_location.

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.sugukurukabe%2Fjapan-real-estate-intel-mcp%2Fevaluate_store_location or MCP find_alternatives. Check mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/evaluate_store_location's live status: https://glimind.com/tool/mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/evaluate_store_location.