mcp-registry/io.github.juancf/scrcpy-mcp/screen_on / alternatives
mcp-registry/io.github.juancf/scrcpy-mcp/screen_onThe best live alternatives to mcp-registry/io.github.juancf/scrcpy-mcp/screen_on right now are mcp-registry/io.github.pipeworx-io/httpbin/delay, mcp-registry/com.googleapis.stitch/mcp/get_screen, mcp-registry/com.googleapis.stitch/mcp/generate_screen_from_text — capability-matched and ranked by current reliability. mcp-registry/io.github.juancf/scrcpy-mcp/screen_on itself is currently "unknown".
| alternative | server | |
|---|---|---|
| mcp-registry/io.github.pipeworx-io/httpbin/delay | io.github.pipeworx-io/httpbin | live status → |
| mcp-registry/com.googleapis.stitch/mcp/get_screen | com.googleapis.stitch/mcp | live status → |
| mcp-registry/com.googleapis.stitch/mcp/generate_screen_from_text | com.googleapis.stitch/mcp | live status → |
mcp-registry/io.github.pipeworx-io/httpbin/delay is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.googleapis.stitch/mcp/get_screen, mcp-registry/com.googleapis.stitch/mcp/generate_screen_from_text. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.juancf/scrcpy-mcp/screen_on's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.juancf%2Fscrcpy-mcp%2Fscreen_on.
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%2Fscreen_on
or MCP find_alternatives. Check mcp-registry/io.github.juancf/scrcpy-mcp/screen_on's live status: https://glimind.com/tool/mcp-registry/io.github.juancf/scrcpy-mcp/screen_on.