Model Context Protocol moderate risk

Geo

The MCP-Geo server provides geocoding and reverse geocoding services using the GeoPy library, allowing LLMs to convert addresses to coordinates and vice versa.

Connections & Capabilities

Connects To

GitHub

Capabilities

read

Quickstart

Config

{
    "mcp-geo": {
        "command": "uv",
        "args": [
          "--directory",
          "MCP-Geo",
          "run",
          "geo.py"
        ],
        "env": {
        "NOMINATIM_URL": "${NOMINATIM_URL}",
        "SCHEME": "http",
        "GEOCODER_PROVIDER": "nominatim"
        }
    }
}

Exposed MCP Tools (7)

safe

geocode_location

Converts an address or place name into latitude, longitude, and a formatted address.

Read-only operation; retrieves geocoding information.

safe

reverse_geocode

Converts latitude and longitude coordinates into the nearest address.

Read-only operation; retrieves address information.

safe

geocode_with_details

Similar to geocode_location, but returns additional geocoding details.

Read-only operation; retrieves detailed geocoding information.

safe

geocode_multiple_locations

Geocodes a list of addresses, returning lat/lon/address for each.

Read-only operation; retrieves geocoding information for multiple locations.

safe

reverse_geocode_multiple_locations

Reverse geocodes a list of lat/lon pairs, returning address information for each.

Read-only operation; retrieves address information for multiple locations.

safe

distance_between_addresses

Calculates the distance between two addresses or place names.

Read-only operation; calculates distance based on geocoded locations.

safe

distance_between_coords

Calculates the distance between two lat/lon coordinate pairs.

Read-only operation; calculates distance based on coordinates.

Safety Assessment

This server is relatively safe for geocoding tasks, as it primarily performs read operations and includes rate limiting and error handling. However, the reliance on external geocoding services and the potential need for API keys introduce some risk, requiring careful configuration and monitoring.

Rate limiting is implemented to prevent abuse of geocoding services.
Error handling is in place to gracefully manage geocoding exceptions.
The server primarily performs read operations related to geocoding.
Environment variables are used for configuration, minimizing hardcoded secrets.

Internet access is required for geocoding, which introduces external dependencies.
Incorrectly configured environment variables could lead to unexpected behavior.
The server relies on external geocoding services, which may have their own security vulnerabilities.
Depending on the geocoding provider used, API keys or credentials might be required, which need secure handling.