mcp-registry/com.daedalmap/geocoding/loc_id_hierarchy / alternatives

Live alternatives to mcp-registry/com.daedalmap/geocoding/loc_id_hierarchy

The best live alternatives to mcp-registry/com.daedalmap/geocoding/loc_id_hierarchy right now are mcp-registry/com.daedalmap/county-map/loc_id_hierarchy, mcp-registry/com.daedalmap/county-map/loc_id_info, mcp-registry/com.daedalmap/boundaries/loc_id_info, mcp-registry/com.daedalmap/reverse-geocoding/resolve_point, mcp-registry/com.daedalmap/county-map/resolve_point — capability-matched and ranked by current reliability. mcp-registry/com.daedalmap/geocoding/loc_id_hierarchy itself is currently "healthy".

alternative	server
mcp-registry/com.daedalmap/county-map/loc_id_hierarchy	com.daedalmap/county-map	live status →
mcp-registry/com.daedalmap/county-map/loc_id_info	com.daedalmap/county-map	live status →
mcp-registry/com.daedalmap/boundaries/loc_id_info	com.daedalmap/boundaries	live status →
mcp-registry/com.daedalmap/reverse-geocoding/resolve_point	com.daedalmap/reverse-geocoding	live status →
mcp-registry/com.daedalmap/county-map/resolve_point	com.daedalmap/county-map	live status →
mcp-registry/com.daedalmap/boundaries/get_boundary	com.daedalmap/boundaries	live status →
mcp-registry/com.daedalmap/county-map/get_boundary	com.daedalmap/county-map	live status →
mcp-registry/io.github.1145-am/syracuse-mcp-server/location_groups_list	io.github.1145-am/syracuse-mcp-server	live status →
mcp-registry/io.github.pcmarts/recruiter-roles-mcp/list_locations	io.github.pcmarts/recruiter-roles-mcp	live status →
mcp-registry/io.github.pipeworx-io/gleif/get_lei_relationships	io.github.pipeworx-io/gleif	live status →
mcp-registry/ai.datamerge/mcp/get_company_hierarchy	ai.datamerge/mcp	live status →
mcp-registry/io.github.soapyred/freightutils/unlocode_lookup	io.github.SoapyRED/freightutils	live status →

FAQ

What is the best alternative to mcp-registry/com.daedalmap/geocoding/loc_id_hierarchy?

mcp-registry/com.daedalmap/county-map/loc_id_hierarchy is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.daedalmap/county-map/loc_id_info, mcp-registry/com.daedalmap/boundaries/loc_id_info, mcp-registry/com.daedalmap/reverse-geocoding/resolve_point, mcp-registry/com.daedalmap/county-map/resolve_point. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.daedalmap/geocoding/loc_id_hierarchy down right now?

mcp-registry/com.daedalmap/geocoding/loc_id_hierarchy's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.daedalmap%2Fgeocoding%2Floc_id_hierarchy.

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.daedalmap%2Fgeocoding%2Floc_id_hierarchy or MCP find_alternatives. Check mcp-registry/com.daedalmap/geocoding/loc_id_hierarchy's live status: https://glimind.com/tool/mcp-registry/com.daedalmap/geocoding/loc_id_hierarchy.