# io.usefulapi/geoapify (remote · geoapify.usefulapi.io)

Geocode, reverse-geocode, autocomplete, route and search places.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `geoapify.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-geoapify/geoapify.md), [page](https://verifymcp.io/servers/io-usefulapi-geoapify/geoapify)

## Channel facts

- Endpoint: `https://geoapify.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 429, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 429.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### How do I install the io.usefulapi/geoapify MCP server?

io.usefulapi/geoapify is a hosted endpoint at https://geoapify.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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-geoapify 'https://geoapify.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-geoapify": {
      "url": "https://geoapify.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-geoapify": {
      "type": "http",
      "url": "https://geoapify.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-geoapify]
url = "https://geoapify.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-geoapify": {
      "type": "remote",
      "url": "https://geoapify.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-geoapify --url 'https://geoapify.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-geoapify:
    url: "https://geoapify.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-geoapify": {
      "Transport": "http",
      "Url": "https://geoapify.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-geoapify -t streamable-http -u 'https://geoapify.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-geoapify": {
      "type": "http",
      "url": "https://geoapify.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-03 (score 18, −56)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-02 (score 74, +56)

- [security improvement] HTTPS: unverified → pass
- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (8)

### `geoapify_geocode_search` (~216 tokens)

Forward geocoding

Forward geocoding — turn a free-form address or place name into coordinates and structured address parts. Geoapify REST: GET /v1/geocode/search.

Input parameters:

- `bias` (string): Bias results toward a location, e.g. 'proximity:13.4,52.5'.
- `filter` (string): Spatial filter, e.g. 'countrycode:de' or 'rect:lon1,lat1,lon2,lat2'.
- `format` (string): Response format — 'json' (default) or 'geojson'.
- `lang` (string): Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
- `limit` (integer): Max number of results to return.
- `text` (string, required): The free-form address or place name to geocode (required).
- `type` (string): Restrict to a location type, e.g. 'city', 'street', 'amenity', 'postcode'.

### `geoapify_geocode_reverse` (~148 tokens)

Reverse geocoding

Reverse geocoding — turn coordinates into the nearest address / place. Geoapify REST: GET /v1/geocode/reverse.

Input parameters:

- `format` (string): Response format — 'json' (default) or 'geojson'.
- `lang` (string): Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
- `lat` (number, required): Latitude (required).
- `limit` (integer): Max number of results to return.
- `lon` (number, required): Longitude (required).
- `type` (string): Restrict to a location type, e.g. 'city', 'street', 'amenity'.

### `geoapify_geocode_autocomplete` (~216 tokens)

Address autocomplete

Address autocomplete — suggest completed addresses/places for a partial query, ideal for as-you-type inputs. Geoapify REST: GET /v1/geocode/autocomplete.

Input parameters:

- `bias` (string): Bias results toward a location, e.g. 'proximity:13.4,52.5'.
- `filter` (string): Spatial filter, e.g. 'countrycode:de' or 'rect:lon1,lat1,lon2,lat2'.
- `format` (string): Response format — 'json' (default) or 'geojson'.
- `lang` (string): Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
- `limit` (integer): Max number of results to return.
- `text` (string, required): The partial address or place text to complete (required).
- `type` (string): Restrict to a location type, e.g. 'city', 'street', 'amenity', 'postcode'.

### `geoapify_places` (~231 tokens)

Places search

Search for places (POIs) by category within an area, optionally filtered by name/conditions. Returns a GeoJSON FeatureCollection. Geoapify REST: GET /v2/places.

Input parameters:

- `bias` (string): Bias results toward a location, e.g. 'proximity:13.4,52.5'.
- `categories` (string, required): Comma-separated Geoapify place categories, e.g. 'catering.restaurant,commercial' (required).
- `conditions` (string): Comma-separated conditions, e.g. 'named,internet_access'.
- `filter` (string): Spatial filter, e.g. 'circle:13.4,52.5,1000' or 'rect:...' or 'place:<placeId>'.
- `lang` (string): Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
- `limit` (integer): Max number of results to return.
- `name` (string): Filter places by (partial) name.
- `offset` (integer): Pagination offset (skip N results).

### `geoapify_place_details` (~179 tokens)

Place details

Get detailed information (and optionally geometry/features) for a place. Provide either `id` (the `place_id` returned by geoapify_places) OR both `lat` and `lon`. Geoapify REST: GET /v2/place-details.

Input parameters:

- `features` (string): Comma-separated detail feature sets, e.g. 'details,building,geometry'.
- `id` (string): The Geoapify place id (pass the `place_id` value from geoapify_places).
- `lang` (string): Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
- `lat` (number): Latitude (use with `lon` instead of `id`).
- `lon` (number): Longitude (use with `lat` instead of `id`).

### `geoapify_routing` (~196 tokens)

Routing

Compute a route between waypoints for a travel mode, returning distance, time and legs. Geoapify REST: GET /v1/routing.

Input parameters:

- `details` (string): Comma-separated route detail sets, e.g. 'instruction_details,route_details'.
- `format` (string): Response format — 'json' (default) or 'geojson'.
- `lang` (string): Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
- `mode` (string, required): Travel mode: drive, walk, bicycle, truck, hike, transit, etc. (required).
- `units` (string): Distance units — 'metric' or 'imperial'.
- `waypoints` (string, required): Pipe-separated 'lat,lon' waypoints, e.g. '52.5,13.4|52.6,13.5' (required).

### `geoapify_isoline` (~197 tokens)

Reachability isoline

Compute a reachability isoline (isochrone/isodistance) — the area reachable from a point within a time or distance budget. Geoapify REST: GET /v1/isoline.

Input parameters:

- `lang` (string): Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
- `lat` (number, required): Origin latitude (required).
- `lon` (number, required): Origin longitude (required).
- `mode` (string, required): Travel mode: drive, walk, bicycle, etc. (required).
- `range` (number, required): Budget for the isoline — seconds if type=time, meters if type=distance (required).
- `traffic` (string): Traffic model for driving, e.g. 'free_flow' or 'approximated'.
- `type` (string, required): Isoline type — 'time' (seconds) or 'distance' (meters) (required).

### `geoapify_ip_geolocation` (~88 tokens)

IP geolocation

Look up the approximate location (country, city, coordinates) of an IP address. Geoapify REST: GET /v1/ipinfo.

Input parameters:

- `ip` (string, required): The IPv4/IPv6 address to locate (required).
- `lang` (string): Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-geoapify/geoapify#diagnostics

## Score history

- 2026-10-04: 18
- 2026-10-03: 18
- 2026-10-02: 74
- 2026-10-01: 18
- 2026-09-30: 18
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/geoapify MCP server?

io.usefulapi/geoapify is an MCP server listed in the public MCP registry as io.usefulapi/geoapify. Geocode, reverse-geocode, autocomplete, route and search places. This page covers its hosted endpoint (https://geoapify.usefulapi.io/mcp).

### Is the io.usefulapi/geoapify MCP server safe to use?

io.usefulapi/geoapify 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 io.usefulapi/geoapify MCP server expose?

io.usefulapi/geoapify exposes 8 tools: geoapify_geocode_search, geoapify_geocode_reverse, geoapify_geocode_autocomplete, geoapify_places, geoapify_place_details, and 3 more. Their descriptions and schemas cost roughly 1,471 tokens of context every time the server is loaded.

### Does the io.usefulapi/geoapify MCP server require authentication?

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

### Is the io.usefulapi/geoapify MCP server still maintained?

io.usefulapi/geoapify is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://geoapify.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-geoapify/geoapify.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-geoapify/geoapify.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-geoapify/geoapify