mcp-registry/io.github.juancf/scrcpy-mcp/long_press / alternatives
mcp-registry/io.github.juancf/scrcpy-mcp/long_pressThe best live alternatives to mcp-registry/io.github.juancf/scrcpy-mcp/long_press right now are mcp-registry/io.github.pipeworx-io/photon/search, mcp-registry/io.github.pipeworx-io/transit-land/search_stops, mcp-registry/io.tinyfn/tinyfn/is_valid_coordinates, mcp-registry/io.github.pipeworx-io/nominatim/search_address, mcp-registry/io.github.pipeworx-io/mapbox/geocode_reverse — capability-matched and ranked by current reliability. mcp-registry/io.github.juancf/scrcpy-mcp/long_press itself is currently "unknown".
mcp-registry/io.github.pipeworx-io/photon/search is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/transit-land/search_stops, mcp-registry/io.tinyfn/tinyfn/is_valid_coordinates, mcp-registry/io.github.pipeworx-io/nominatim/search_address, mcp-registry/io.github.pipeworx-io/mapbox/geocode_reverse. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.juancf/scrcpy-mcp/long_press's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.juancf%2Fscrcpy-mcp%2Flong_press.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.juancf%2Fscrcpy-mcp%2Flong_press
or MCP find_alternatives. Check mcp-registry/io.github.juancf/scrcpy-mcp/long_press's live status: https://glimind.com/tool/mcp-registry/io.github.juancf/scrcpy-mcp/long_press.