Skip to content

Geoapify MCP by usefulapi

io.usefulapi/geoapifyusefulapi.iostreamable-httpv1.40.4Scanned

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

8 tools: 5 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 5 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Geoapify MCP by usefulapi can do

The Geoapify MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 8 tools. It can create or change data (5 tools: geoapify_geocode_reverse, geoapify_geocode_autocomplete, geoapify_routing, geoapify_isoline and 1 more), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 5Claude Code: ask
  • geoapify_geocode_autocompleteAddress autocomplete — suggest completed addresses/places for a partial query, ideal for as-you-type inputs.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Address autocomplete — suggest completed addresses/places for a partial query, ideal for as-you-type inputs. Geoapify REST: GET /v1/geocode/autocomplete.

    Annotations the server declares

    • title: Address autocomplete
    • readOnlyHint: true
  • geoapify_geocode_reverseReverse geocoding — turn coordinates into the nearest address / place.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Reverse geocoding — turn coordinates into the nearest address / place. Geoapify REST: GET /v1/geocode/reverse.

    Annotations the server declares

    • title: Reverse geocoding
    • readOnlyHint: true
  • geoapify_ip_geolocationLook up the approximate location (country, city, coordinates) of an IP address.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Look up the approximate location (country, city, coordinates) of an IP address. Geoapify REST: GET /v1/ipinfo.

    Annotations the server declares

    • title: IP geolocation
    • readOnlyHint: true
  • geoapify_isolineCompute a reachability isoline (isochrone/isodistance) — the area reachable from a point within a time or distance budget.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Compute a reachability isoline (isochrone/isodistance) — the area reachable from a point within a time or distance budget. Geoapify REST: GET /v1/isoline.

    Annotations the server declares

    • title: Reachability isoline
    • readOnlyHint: true
  • geoapify_routingCompute a route between waypoints for a travel mode, returning distance, time and legs.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Compute a route between waypoints for a travel mode, returning distance, time and legs. Geoapify REST: GET /v1/routing.

    Annotations the server declares

    • title: Routing
    • readOnlyHint: true
Only reads 3Show 3 read-only tools
  • geoapify_place_detailsGet detailed information (and optionally geometry/features) for a place.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Place details
    • readOnlyHint: true
  • geoapify_placesSearch for places (POIs) by category within an area, optionally filtered by name/conditions.No findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.
    Description, as the server wrote it
    Search for places (POIs) by category within an area, optionally filtered by name/conditions. Returns a GeoJSON FeatureCollection. Geoapify REST: GET /v2/places.

    Annotations the server declares

    • title: Places search
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://geoapify.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://geoapify.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://geoapify.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://geoapify.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__geoapify__geoapify_geocode_search",
      "mcp__geoapify__geoapify_places",
      "mcp__geoapify__geoapify_place_details"
    ],
    "ask": [
      "mcp__geoapify__geoapify_geocode_reverse",
      "mcp__geoapify__geoapify_geocode_autocomplete",
      "mcp__geoapify__geoapify_routing",
      "mcp__geoapify__geoapify_isoline",
      "mcp__geoapify__geoapify_ip_geolocation"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as geoapify. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/geoapify/verify?hash=4538426647057bedb42080d01d3b02aee106b8340330b352648c2c8ba2bceb34" | jq -e '.changed == false'

Pinned hash 453842664705, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/geoapify/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/geoapify
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/geoapify.svg)](https://radar.anlyon.com/servers/io.usefulapi/geoapify)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Geoapify MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Geoapify MCP by usefulapi safe?

No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Geoapify MCP by usefulapi delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Geoapify MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Geoapify MCP by usefulapi have?

8 tools: 5 write, 3 read. geoapify_geocode_reverse, geoapify_geocode_autocomplete, geoapify_routing, geoapify_isoline, geoapify_ip_geolocation, geoapify_geocode_search, geoapify_places and geoapify_place_details.

Does the Geoapify MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Geoapify MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Geoapify MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.