io.usefulapi/maptiler
REMOTE · MAPTILER.USEFULAPI.IO · SCANNED SEP 20
Geocoding, elevation, IP geolocation and coordinate transforms from the MapTiler Cloud API.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1116 tokens (~139/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/maptiler MCP server?
io.usefulapi/maptiler 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
claude mcp add --transport http io-usefulapi-maptiler 'https://maptiler.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-maptiler": {
"url": "https://maptiler.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-maptiler": {
"type": "http",
"url": "https://maptiler.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-maptiler] url = "https://maptiler.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-maptiler": {
"type": "remote",
"url": "https://maptiler.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-maptiler --url 'https://maptiler.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-maptiler:
url: "https://maptiler.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-maptiler": {
"Transport": "http",
"Url": "https://maptiler.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-maptiler -t streamable-http -u 'https://maptiler.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-maptiler": {
"type": "http",
"url": "https://maptiler.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 0
- Stability: pass → 0.97 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 0
- Stability: pass → 0.97 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 0
- Stability: pass → 0.97 functional
- 7 Sept 26 0
- Stability: 0.97 → pass security
- 6 Sept 26 0
- Stability: pass → 0.97 functional
- 3 Sept 26 0
- Stability: 0.97 → pass security
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 20 Sept 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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 64ff4d42edbcbb05137dcc1aecc5236a |
| SANs: usefulapi.io, maptiler.usefulapi.io, *.maptiler.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 | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://maptiler.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://maptiler.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://maptiler.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://maptiler.usefulapi.io/mcp |
| Authorisation server | https://maptiler.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://maptiler.usefulapi.io/mcp | Inconclusive | 401 |
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 →
maptiler_batch_geocode Batch forward 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.
| Name | Type | Req | Description |
|---|---|---|---|
| autocomplete | boolean | – | Treat the last term of each query as a prefix. |
| country | string | – | Comma-separated ISO 3166-1 alpha-2 country codes to restrict to. |
| language | string | – | Comma-separated ISO 639-1 language codes for results. |
| limit | integer | – | Max results per query (1-10). |
| queries | array | yes | 1-50 place/address strings to geocode. |
| types | string | – | Comma-separated place types to include. |
| worldview | string | – | Disputed-border worldview: default | auto | ch | us. |
No output schema declared.
No examples provided.
maptiler_geocode Forward geocode (search place by name) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| autocomplete | boolean | – | Treat the last term as a prefix for as-you-type search. |
| bbox | string | – | Bounding box "west,south,east,north" to restrict results. |
| country | string | – | Comma-separated ISO 3166-1 alpha-2 country codes to restrict to. |
| excludeTypes | boolean | – | If true, `types` becomes an exclude list instead. |
| fuzzyMatch | boolean | – | Allow approximate matching of the query terms. |
| language | string | – | Comma-separated ISO 639-1 language codes for results. |
| limit | integer | – | Max results (1-10). Default 5. |
| proximity | string | – | Bias toward a point: "lon,lat" or the literal "ip". |
| query | string | yes | Place/address/POI to search for (goes in the URL path). |
| types | string | – | Comma-separated place types to include (e.g. address,poi,city). |
| worldview | string | – | Disputed-border worldview: default | auto | ch | us. |
No output schema declared.
No examples provided.
maptiler_geolocate_ip Geolocate IP address ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| elevation | boolean | – | Include elevation of the located point. |
No output schema declared.
No examples provided.
maptiler_get_data_features Get dataset features (GeoJSON) ~64
Fetch the GeoJSON FeatureCollection of a MapTiler-hosted dataset by its data id. API: GET /data/{dataId}/features.json.
| Name | Type | Req | Description |
|---|---|---|---|
| dataId | string | yes | MapTiler dataset id (from your MapTiler Cloud account). |
No output schema declared.
No examples provided.
maptiler_get_elevation Get elevation at coordinates ~83
Look up ground elevation at up to 50 coordinates. Returns an array of [lng, lat, elevation] triples. API: GET /elevation/{locations}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| locations | array | yes | 1-50 [longitude, latitude] pairs (latitude -85..85). |
| unit | string | – | Elevation unit. Default meters. |
No output schema declared.
No examples provided.
maptiler_reverse_geocode Reverse geocode (place at coordinates) ~158
Find the place(s) at a given longitude/latitude, returned as GeoJSON features. API: GET /geocoding/{longitude},{latitude}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeTypes | boolean | – | If true, `types` becomes an exclude list instead. |
| language | string | – | Comma-separated ISO 639-1 language codes for results. |
| latitude | number | yes | Latitude, -90..90. |
| limit | integer | – | Max results (1-10). Default 5. |
| longitude | number | yes | Longitude, -180..180. |
| types | string | – | Comma-separated place types to include. |
| worldview | string | – | Disputed-border worldview: default | auto | ch | us. |
No output schema declared.
No examples provided.
maptiler_search_coordinate_systems Search coordinate reference 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.
| Name | Type | Req | Description |
|---|---|---|---|
| exports | boolean | – | Include WKT / Proj4 export strings for each CRS. |
| limit | integer | – | Max results (1-50). Default 10. |
| offset | integer | – | Pagination offset. Default 0. |
| query | string | yes | Search terms; supports filters like "code:4326" or "kind:CRS-PROJCRS". |
| transformations | boolean | – | Include available transformations for each CRS. |
No output schema declared.
No examples provided.
maptiler_transform_coordinates Transform coordinates between CRS ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| coordinates | array | yes | 1-50 [x, y] coordinate pairs in the source CRS. |
| ops | string | – | Pipe-separated transformation operation codes to force a path. |
| s_srs | integer | – | Source CRS / EPSG code. Default 4326 (WGS84). |
| t_srs | integer | – | Target CRS / EPSG code. Default 4326 (WGS84). |
No output schema declared.
No examples provided.
What is the io.usefulapi/maptiler MCP server?
io.usefulapi/maptiler is an MCP server 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 io.usefulapi/maptiler MCP server safe to use?
io.usefulapi/maptiler scores 85 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 io.usefulapi/maptiler MCP server expose?
io.usefulapi/maptiler 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,116 tokens of context every time the server is loaded.
Does the io.usefulapi/maptiler MCP server require authentication?
Yes. io.usefulapi/maptiler asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/maptiler MCP server still maintained?
io.usefulapi/maptiler is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.