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.

io.usefulapi/geoapify

REMOTE · GEOAPIFY.USEFULAPI.IO · SCANNED OCT 4

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

Available components

remote · geoapify.usefulapi.io 18
18 Trust /100
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.

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.

remote · geoapify.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-geoapify 'https://geoapify.usefulapi.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-geoapify": {
      "url": "https://geoapify.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-geoapify": {
      "type": "http",
      "url": "https://geoapify.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-geoapify --url 'https://geoapify.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-geoapify:
    url: "https://geoapify.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-geoapify": {
      "Transport": "http",
      "Url": "https://geoapify.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-geoapify -t streamable-http -u 'https://geoapify.usefulapi.io/mcp'
// mcp.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 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.

  • 3 Oct 26 −56
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • HTTPS: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 2 Oct 26 +56
    • HTTPS: unverified → pass ▲ security
    • Authorization: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • First check of Authorization: partial security
    • MCP protocol: unverified → fail ▼ functional
    • 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 functional
  • 29 Sept 26 18

    First indexed and scored.

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 4 Oct 2026 · Probed https://geoapify.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 geoapify.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 Inconclusive

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

Result Inconclusive
HTTP status 429
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://geoapify.usefulapi.io/mcp HTTP error 429
http (plaintext) http://geoapify.usefulapi.io/mcp Inconclusive 429
MCP tools · 8 exposed · ~1,471 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
geoapify_geocode_autocomplete ~216

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

NameTypeReqDescription
biasstring–Bias results toward a location, e.g. 'proximity:13.4,52.5'.
filterstring–Spatial filter, e.g. 'countrycode:de' or 'rect:lon1,lat1,lon2,lat2'.
formatstring–Response format — 'json' (default) or 'geojson'.
langstring–Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
limitinteger–Max number of results to return.
textstringyesThe partial address or place text to complete (required).
typestring–Restrict to a location type, e.g. 'city', 'street', 'amenity', 'postcode'.

No output schema declared.

No examples provided.

geoapify_geocode_reverse ~148

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

NameTypeReqDescription
formatstring–Response format — 'json' (default) or 'geojson'.
langstring–Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
latnumberyesLatitude (required).
limitinteger–Max number of results to return.
lonnumberyesLongitude (required).
typestring–Restrict to a location type, e.g. 'city', 'street', 'amenity'.

No output schema declared.

No examples provided.

geoapify_geocode_search ~216

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

NameTypeReqDescription
biasstring–Bias results toward a location, e.g. 'proximity:13.4,52.5'.
filterstring–Spatial filter, e.g. 'countrycode:de' or 'rect:lon1,lat1,lon2,lat2'.
formatstring–Response format — 'json' (default) or 'geojson'.
langstring–Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
limitinteger–Max number of results to return.
textstringyesThe free-form address or place name to geocode (required).
typestring–Restrict to a location type, e.g. 'city', 'street', 'amenity', 'postcode'.

No output schema declared.

No examples provided.

geoapify_ip_geolocation ~88

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

NameTypeReqDescription
ipstringyesThe IPv4/IPv6 address to locate (required).
langstring–Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.

No output schema declared.

No examples provided.

geoapify_isoline ~197

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

NameTypeReqDescription
langstring–Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
latnumberyesOrigin latitude (required).
lonnumberyesOrigin longitude (required).
modestringyesTravel mode: drive, walk, bicycle, etc. (required).
rangenumberyesBudget for the isoline — seconds if type=time, meters if type=distance (required).
trafficstring–Traffic model for driving, e.g. 'free_flow' or 'approximated'.
typestringyesIsoline type — 'time' (seconds) or 'distance' (meters) (required).

No output schema declared.

No examples provided.

geoapify_place_details ~179

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.

NameTypeReqDescription
featuresstring–Comma-separated detail feature sets, e.g. 'details,building,geometry'.
idstring–The Geoapify place id (pass the `place_id` value from geoapify_places).
langstring–Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
latnumber–Latitude (use with `lon` instead of `id`).
lonnumber–Longitude (use with `lat` instead of `id`).

No output schema declared.

No examples provided.

geoapify_places ~231

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

NameTypeReqDescription
biasstring–Bias results toward a location, e.g. 'proximity:13.4,52.5'.
categoriesstringyesComma-separated Geoapify place categories, e.g. 'catering.restaurant,commercial' (required).
conditionsstring–Comma-separated conditions, e.g. 'named,internet_access'.
filterstring–Spatial filter, e.g. 'circle:13.4,52.5,1000' or 'rect:...' or 'place:<placeId>'.
langstring–Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
limitinteger–Max number of results to return.
namestring–Filter places by (partial) name.
offsetinteger–Pagination offset (skip N results).

No output schema declared.

No examples provided.

geoapify_routing ~196

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

NameTypeReqDescription
detailsstring–Comma-separated route detail sets, e.g. 'instruction_details,route_details'.
formatstring–Response format — 'json' (default) or 'geojson'.
langstring–Result language as an ISO 639-1 code, e.g. 'en', 'de', 'fr'.
modestringyesTravel mode: drive, walk, bicycle, truck, hike, transit, etc. (required).
unitsstring–Distance units — 'metric' or 'imperial'.
waypointsstringyesPipe-separated 'lat,lon' waypoints, e.g. '52.5,13.4|52.6,13.5' (required).

No output schema declared.

No examples provided.

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.