mcp-registry/io.github.pipeworx-io/mapbox/tilequery / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/mapbox/tilequery

The best live alternatives to mcp-registry/io.github.pipeworx-io/mapbox/tilequery right now are mcp-registry/io.github.pipeworx-io/maptiler/tiles_json, mcp-registry/io.github.pipeworx-io/maptiler/geocode, mcp-registry/io.github.mapbox/mcp-docs-server/search_mapbox_docs_tool, mcp-registry/io.github.pipeworx-io/overpass/query, mcp-registry/io.github.pipeworx-io/wikidata-sparql/entities_at — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/mapbox/tilequery itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/maptiler/tiles_json	io.github.pipeworx-io/maptiler	live status →
mcp-registry/io.github.pipeworx-io/maptiler/geocode	io.github.pipeworx-io/maptiler	live status →
mcp-registry/io.github.mapbox/mcp-docs-server/search_mapbox_docs_tool	io.github.mapbox/mcp-docs-server	live status →
mcp-registry/io.github.pipeworx-io/overpass/query	io.github.pipeworx-io/overpass	live status →
mcp-registry/io.github.pipeworx-io/wikidata-sparql/entities_at	io.github.pipeworx-io/wikidata-sparql	live status →
mcp-registry/io.github.pipeworx-io/maptiler/geocode_by_id	io.github.pipeworx-io/maptiler	live status →
mcp-registry/io.github.pipeworx-io/maptiler/geocode_reverse	io.github.pipeworx-io/maptiler	live status →
mcp-registry/io.github.pipeworx-io/osrm/match	io.github.pipeworx-io/osrm	live status →
mcp-registry/io.github.pipeworx-io/photon/search	io.github.pipeworx-io/photon	live status →
mcp-registry/io.github.pipeworx-io/tomtom/search_poi	io.github.pipeworx-io/tomtom	live status →
mcp-registry/io.github.pipeworx-io/arcgis-phoenix/query_layer	io.github.pipeworx-io/arcgis-phoenix	live status →
mcp-registry/io.github.pipeworx-io/arcgis-montana/query_layer	io.github.pipeworx-io/arcgis-montana	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/mapbox/tilequery?

mcp-registry/io.github.pipeworx-io/maptiler/tiles_json is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/maptiler/geocode, mcp-registry/io.github.mapbox/mcp-docs-server/search_mapbox_docs_tool, mcp-registry/io.github.pipeworx-io/overpass/query, mcp-registry/io.github.pipeworx-io/wikidata-sparql/entities_at. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/mapbox/tilequery down right now?

mcp-registry/io.github.pipeworx-io/mapbox/tilequery's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fmapbox%2Ftilequery.

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%2Fio.github.pipeworx-io%2Fmapbox%2Ftilequery or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/mapbox/tilequery's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/mapbox/tilequery.