Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MapTiler MCP by usefulapi

REMOTE · MAPTILER.USEFULAPI.IO

Geocoding, elevation, IP geolocation and coordinate transforms from the MapTiler Cloud API.

−58 this week 18 Trust /100

Last scanned (1 hour ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 −61
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “convert_coordinates_between_coordinate_systems” functional
    • New prompt “find_coordinates_for_a_place_or_address_or_the_reverse” functional
    • New prompt “geocode_a_list_of_addresses_in_one_go” functional
    • New prompt “look_up_the_elevation_of_points” functional
    • New prompt “read_the_features_of_a_hosted_dataset” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.32.0 → 1.34.0 functional
    • Server version: 1.31.0 → 1.32.0 functional
    • Server version: 1.30.2 → 1.31.0 functional
  • 30 Oct 26 0
    • Server version: 1.30.1 → 1.30.2 functional
    • Server version: 1.30.0 → 1.30.1 functional
  • 29 Oct 26 0
    • Server version: 1.29.0 → 1.30.0 functional
    • Server version: 1.28.0 → 1.29.0 functional
    • Server version: 1.27.0 → 1.28.0 functional
    • “maptiler_reverse_geocode” reworded the description of “limit” cosmetic
  • 28 Oct 26 0
    • Server version: 1.25.0 → 1.27.0 functional
  • 27 Oct 26 0
    • Server version: 1.24.0 → 1.25.0 functional
  • 25 Oct 26 0
    • Server version: 1.23.0 → 1.24.0 functional
    • Server version: 1.22.0 → 1.23.0 functional
    • Server version: 1.21.3 → 1.22.0 functional
    • Server version: 1.21.0 → 1.21.3 functional
  • 24 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 1.20.0 → 1.21.0 functional
    • Server version: 1.19.0 → 1.20.0 functional
    • Server version: 1.17.0 → 1.19.0 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://maptiler.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of maptiler.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://maptiler.usefulapi.io/mcp Redirected 302 https://usefulapi.io/maptiler/
http (plaintext) http://maptiler.usefulapi.io/mcp Inconclusive 302 http://maptiler.usefulapi.io/mcp
MCP tools · 8 exposed · ~1,131 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
maptiler_batch_geocode ~183

Forward-geocode up to 50 queries in one request. Returns a JSON ARRAY of GeoJSON FeatureCollections, one per query, in order. API: GET /geocoding/{q1;q2;...}.json.

NameTypeReqDescription
autocompleteboolean–Treat the last term of each query as a prefix.
countrystring–Comma-separated ISO 3166-1 alpha-2 country codes to restrict to.
languagestring–Comma-separated ISO 639-1 language codes for results.
limitinteger–Max results per query (1-10).
queriesarrayyes1-50 place/address strings to geocode.
typesstring–Comma-separated place types to include.
worldviewstring–Disputed-border worldview: default | auto | ch | us.

No output schema declared.

No examples provided.

maptiler_geocode ~278

Search for a place, address, or POI by name and get matching locations as GeoJSON features. e.g. 'Zurich' or '1600 Pennsylvania Ave'. API: GET /geocoding/{query}.json.

NameTypeReqDescription
autocompleteboolean–Treat the last term as a prefix for as-you-type search.
bboxstring–Bounding box "west,south,east,north" to restrict results.
countrystring–Comma-separated ISO 3166-1 alpha-2 country codes to restrict to.
excludeTypesboolean–If true, `types` becomes an exclude list instead.
fuzzyMatchboolean–Allow approximate matching of the query terms.
languagestring–Comma-separated ISO 639-1 language codes for results.
limitinteger–Max results (1-10). Default 5.
proximitystring–Bias toward a point: "lon,lat" or the literal "ip".
querystringyesPlace/address/POI to search for (goes in the URL path).
typesstring–Comma-separated place types to include (e.g. address,poi,city).
worldviewstring–Disputed-border worldview: default | auto | ch | us.

No output schema declared.

No examples provided.

maptiler_geolocate_ip ~65

Geolocates the IP address making the request — from a hosted Worker this is the server's egress IP, not the end-user's. API: GET /geolocation/ip.json.

NameTypeReqDescription
elevationboolean–Include elevation of the located point.

No output schema declared.

No examples provided.

maptiler_get_data_features ~64

Fetch the GeoJSON FeatureCollection of a MapTiler-hosted dataset by its data id. API: GET /data/{dataId}/features.json.

NameTypeReqDescription
dataIdstringyesMapTiler dataset id (from your MapTiler Cloud account).

No output schema declared.

No examples provided.

maptiler_get_elevation ~83

Look up ground elevation at up to 50 coordinates. Returns an array of [lng, lat, elevation] triples. API: GET /elevation/{locations}.json.

NameTypeReqDescription
locationsarrayyes1-50 [longitude, latitude] pairs (latitude -85..85).
unitstring–Elevation unit. Default meters.

No output schema declared.

No examples provided.

maptiler_reverse_geocode ~173

Find the place(s) at a given longitude/latitude, returned as GeoJSON features. API: GET /geocoding/{longitude},{latitude}.json.

NameTypeReqDescription
excludeTypesboolean–If true, `types` becomes an exclude list instead.
languagestring–Comma-separated ISO 639-1 language codes for results.
latitudenumberyesLatitude, -90..90.
limitinteger–Max results (1-10). Default 1. A limit greater than 1 requires exactly one included place type in types.
longitudenumberyesLongitude, -180..180.
typesstring–Comma-separated place types to include.
worldviewstring–Disputed-border worldview: default | auto | ch | us.

No output schema declared.

No examples provided.

maptiler_search_coordinate_systems ~154

Search MapTiler's CRS/EPSG database by free text or key:value filters (e.g. 'code:4326', 'kind:CRS-PROJCRS'). API: GET /coordinates/search/{query}.json.

NameTypeReqDescription
exportsboolean–Include WKT / Proj4 export strings for each CRS.
limitinteger–Max results (1-50). Default 10.
offsetinteger–Pagination offset. Default 0.
querystringyesSearch terms; supports filters like "code:4326" or "kind:CRS-PROJCRS".
transformationsboolean–Include available transformations for each CRS.

No output schema declared.

No examples provided.

maptiler_transform_coordinates ~131

Transform up to 50 coordinate pairs from a source coordinate reference system to a target one (EPSG codes). API: GET /coordinates/transform/{coordinates}.json.

NameTypeReqDescription
coordinatesarrayyes1-50 [x, y] coordinate pairs in the source CRS.
opsstring–Pipe-separated transformation operation codes to force a path.
s_srsinteger–Source CRS / EPSG code. Default 4326 (WGS84).
t_srsinteger–Target CRS / EPSG code. Default 4326 (WGS84).

No output schema declared.

No examples provided.

Install

How do I install the MapTiler MCP by usefulapi server?

MapTiler MCP by usefulapi is a hosted endpoint at https://maptiler.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · maptiler.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-maptiler 'https://maptiler.usefulapi.io/mcp'
Common questions

What is the MapTiler MCP by usefulapi server?

MapTiler MCP by usefulapi is listed in the public MCP registry as io.usefulapi/maptiler. Geocoding, elevation, IP geolocation and coordinate transforms from the MapTiler Cloud API. This page covers its hosted endpoint (https://maptiler.usefulapi.io/mcp).

Is the MapTiler MCP by usefulapi server safe to use?

MapTiler MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MapTiler MCP by usefulapi server expose?

MapTiler MCP by usefulapi exposes 8 tools: maptiler_geocode, maptiler_reverse_geocode, maptiler_batch_geocode, maptiler_geolocate_ip, maptiler_get_elevation, and 3 more. Their descriptions and schemas cost roughly 1,131 tokens of context every time the server is loaded.

Does the MapTiler MCP by usefulapi server require authentication?

Its publisher declares no required credentials for MapTiler MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the MapTiler MCP by usefulapi server still maintained?

MapTiler MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.