pulsemcp/computer-control/click_screen / alternatives
pulsemcp/computer-control/click_screenThe best live alternatives to pulsemcp/computer-control/click_screen right now are mcp-registry/io.tinyfn/tinyfn/is_valid_coordinates, mcp-registry/io.github.pipeworx-io/timeapi-io/current_time_coordinate, mcp-registry/com.googleapis.container/mcp/update_cluster, mcp-registry/io.tinyfn/tinyfn/geohash_decode, mcp-registry/io.tinyfn/tinyfn/geohash_encode — capability-matched and ranked by current reliability. pulsemcp/computer-control/click_screen itself is currently "unknown".
mcp-registry/io.tinyfn/tinyfn/is_valid_coordinates is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/timeapi-io/current_time_coordinate, mcp-registry/com.googleapis.container/mcp/update_cluster, mcp-registry/io.tinyfn/tinyfn/geohash_decode, mcp-registry/io.tinyfn/tinyfn/geohash_encode. Glimind ranks alternatives by semantic similarity and live health.
pulsemcp/computer-control/click_screen's current verdict is "unknown". See its live status and score at https://glimind.com/tool/pulsemcp%2Fcomputer-control%2Fclick_screen.
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/pulsemcp%2Fcomputer-control%2Fclick_screen
or MCP find_alternatives. Check pulsemcp/computer-control/click_screen's live status: https://glimind.com/tool/pulsemcp/computer-control/click_screen.