io.github.cyanheads/openstreetmap-mcp-server

The listed variables—OSM_NOMINATIM_BASE_URL, OSM_USER_AGENT, OSM_OVERPASS_BASE_URL, and MCP_LOG_LEVEL—look more like configuration values than typical secrets. However, if the User-Agent or service URLs are misconfigured to internal or unexpected endpoints, they could still create attribution or traffic-redirection risks.

The tool is described as performing geocoding, reverse geocoding, and Overpass queries, so it will send query content to the remote endpoint openstreetmap.caseyjhand.com. This is standard network behavior for a mapping/query MCP tool, and the provided material does not show clear evidence of unrelated third-party exfiltration or covert transmission.

The system checks indicate that the tool executes code or starts a local process, which is normal for MCP tools. The available material does not show requests for system privileges beyond its mapping-query purpose, so this warrants standard caution rather than a high-risk rating.

Based on the material, its data access should mainly involve user-provided place, coordinate, or spatial query inputs and retrieval of OpenStreetMap results over the network. There is no explicit indication of broad local file, database, or system resource access, but the host environment should still restrict visibility as a precaution.

The source is an official registry entry with an open-source repository and updates within the last year, providing meaningful auditability and maintenance signals. Although community stars are low and the license is unspecified, these do not currently amount to a high-risk supply-chain red flag.