mcp-registry/io.github.obscuritysrl/bun-uia/element.boundingRectangle / alternatives
mcp-registry/io.github.obscuritysrl/bun-uia/element.boundingRectangleThe best live alternatives to mcp-registry/io.github.obscuritysrl/bun-uia/element.boundingRectangle right now are mcp-registry/io.tinyfn/tinyfn/bounding_box, mcp-registry/design.reprise/reprise/autodetect, mcp-registry/com.daedalmap/county-map/get_boundary, mcp-registry/com.daedalmap/geocoding/get_boundary, mcp-registry/com.daedalmap/boundaries/get_boundary — capability-matched and ranked by current reliability. mcp-registry/io.github.obscuritysrl/bun-uia/element.boundingRectangle itself is currently "unknown".
mcp-registry/io.tinyfn/tinyfn/bounding_box is the top capability-matched alternative that's live right now. Other options: mcp-registry/design.reprise/reprise/autodetect, mcp-registry/com.daedalmap/county-map/get_boundary, mcp-registry/com.daedalmap/geocoding/get_boundary, mcp-registry/com.daedalmap/boundaries/get_boundary. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.obscuritysrl/bun-uia/element.boundingRectangle's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.obscuritysrl%2Fbun-uia%2Felement.boundingRectangle.
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.obscuritysrl%2Fbun-uia%2Felement.boundingRectangle
or MCP find_alternatives. Check mcp-registry/io.github.obscuritysrl/bun-uia/element.boundingRectangle's live status: https://glimind.com/tool/mcp-registry/io.github.obscuritysrl/bun-uia/element.boundingRectangle.