mcp-registry/io.github.pipeworx-io/maptiler/tiles_json / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/maptiler/tiles_json

The best live alternatives to mcp-registry/io.github.pipeworx-io/maptiler/tiles_json right now are mcp-registry/io.github.pipeworx-io/mapbox/tilequery, mcp-registry/io.github.pipeworx-io/mapbox/static_image_url, mcp-registry/io.github.pipeworx-io/nasa-eonet/geojson, mcp-registry/io.github.pipeworx-io/wikimedia-rest/page_pdf, mcp-registry/io.github.pipeworx-io/gdacs/geojson — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/maptiler/tiles_json itself is currently "healthy".

alternativeserver
mcp-registry/io.github.pipeworx-io/mapbox/tilequeryio.github.pipeworx-io/mapboxlive status →
mcp-registry/io.github.pipeworx-io/mapbox/static_image_urlio.github.pipeworx-io/mapboxlive status →
mcp-registry/io.github.pipeworx-io/nasa-eonet/geojsonio.github.pipeworx-io/nasa-eonetlive status →
mcp-registry/io.github.pipeworx-io/wikimedia-rest/page_pdfio.github.pipeworx-io/wikimedia-restlive status →
mcp-registry/io.github.pipeworx-io/gdacs/geojsonio.github.pipeworx-io/gdacslive status →
mcp-registry/io.github.pipeworx-io/arcgis-peoria/layer_infoio.github.pipeworx-io/arcgis-peorialive status →
mcp-registry/io.github.pipeworx-io/arcgis-novi/layer_infoio.github.pipeworx-io/arcgis-novilive status →
mcp-registry/io.github.pipeworx-io/arcgis-grandchute/layer_infoio.github.pipeworx-io/arcgis-grandchutelive status →
mcp-registry/io.github.pipeworx-io/arcgis-aurora/layer_infoio.github.pipeworx-io/arcgis-auroralive status →
mcp-registry/io.github.pipeworx-io/arcgis-brampton/layer_infoio.github.pipeworx-io/arcgis-bramptonlive status →
mcp-registry/io.github.pipeworx-io/arcgis-pittsburgh/layer_infoio.github.pipeworx-io/arcgis-pittsburghlive status →
mcp-registry/io.github.pipeworx-io/arcgis-maricopa/layer_infoio.github.pipeworx-io/arcgis-maricopalive status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/maptiler/tiles_json?

mcp-registry/io.github.pipeworx-io/mapbox/tilequery is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/mapbox/static_image_url, mcp-registry/io.github.pipeworx-io/nasa-eonet/geojson, mcp-registry/io.github.pipeworx-io/wikimedia-rest/page_pdf, mcp-registry/io.github.pipeworx-io/gdacs/geojson. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/maptiler/tiles_json down right now?

mcp-registry/io.github.pipeworx-io/maptiler/tiles_json's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fmaptiler%2Ftiles_json.

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%2Fmaptiler%2Ftiles_json or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/maptiler/tiles_json's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/maptiler/tiles_json.