1. Conduid
  2. Maps
  3. io.github.wtronk/geolocation-mcp
MCP server · Maps

io.github.wtronk/geolocation-mcp

Geolocation tools (reverse geocoding, ip lookup, etc) using Jeleo Geolocation API

Unclaimed maps
34Low

Scored 6 months ago · breakdown

About io.github.wtronk/geolocation-mcp

io.github.wtronk/geolocation-mcp is an MCP server in the Maps category: geolocation tools (reverse geocoding, ip lookup, etc) using Jeleo Geolocation API.

Install

From source
git clone https://github.com/wtronk/geolocation-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (2)

batch_reverse_geocodeResolve a list of multiple geographic coordinates in a single request.

Parameters not published.

reverse_geocodeGet rich location metadata (city, country, population metrics, economic data) from latitude/longitude coordinates.

Parameters not published.

Ask AI

✦

Ask AI about io.github.wtronk/geolocation-mcp

Powered by Claude · Grounded in docs

I know everything about io.github.wtronk/geolocation-mcp. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

geolocation-mcp

This is a Model Context Protocol (MCP) server that acts as a wrapper around the GeoLocation API. It provides tools for LLMs (like Claude) to perform fast reverse geocoding and batch reverse geocoding (via IP and coordinates).

Tools

  • reverse_geocode: Get rich location metadata (city, country, population metrics, economic data) from latitude/longitude coordinates.
  • batch_reverse_geocode: Resolve a list of multiple geographic coordinates in a single request.

Configuration

The MCP server requires an API Key and an API Base URL. You can retrieve them from https://jeleo.zone.id/. They are provided to the server as command-line arguments:

  • -apikey: Your Jeleo API Key
  • -url: Base URL for the Jeleo API (default: https://www.jeleo.zone.id/api/geolocation)

Building and Running Locally

The server runs on standard input/output (stdio), which is standard for MCP. It's designed to be run as an executable or via Docker.

Using Docker (Recommended for Registry)

To build the Docker image:

docker build -t geolocation-mcp .

To run it locally via Docker:

docker run -i --rm geolocation-mcp -apikey YOUR_API_KEY

Direct Execution

If you have Go installed, you can build and run it directly:

go build -o geolocation-mcp main.go
./geolocation-mcp -apikey YOUR_API_KEY

Adding to an MCP Client (e.g. Claude Desktop)

If you have published the image to a container registry, or just using it locally, add it to your claude_desktop_config.json:

Local Docker:

{
  "mcpServers": {
    "geolocation": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "geolocation-mcp", "-apikey", "YOUR_API_KEY", "-url", "https://www.jeleo.zone.id/api/geolocation"]
    }
  }
}

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About io.github.wtronk/geolocation-mcp

How do I install io.github.wtronk/geolocation-mcp?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is io.github.wtronk/geolocation-mcp safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is io.github.wtronk/geolocation-mcp still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.