GeoSpark
io.github.Maz2580/geosparkVersion 0.10.0Verifiable geospatial tools: distances, topology, isochrones, Overture Maps, with sources.
Status
Responds955 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:40 UTC
- Latency
- 955 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://geospark.terrascout.app/mcpResponds955 msNo sign-in
Claude Code
claude mcp add --transport http geospark https://geospark.terrascout.app/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: geospark
Remote MCP server URL: https://geospark.terrascout.app/mcpCursor
{
"mcpServers": {
"geospark": {
"url": "https://geospark.terrascout.app/mcp"
}
}
}VS Code
code --add-mcp '{"name":"geospark","type":"http","url":"https://geospark.terrascout.app/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
21 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
calculate_distanceExact geodesic distance between two places or geometries on the WGS84 ellipsoid.
Use for any "how far" question instead of estimating. For NAMED places pass place_a and
place_b; the server geocodes them, so never type coordinates for a place yourself. Use
point_a/point_b only for coordinates the user gave or another tool returned. For lines
and polygons the distance is between their nearest points. Returns metres and kilometres.
| No | Yes | Yes | Yes |
check_spatial_relationshipGround-truth topology: does geometry_a <relationship> geometry_b?
Use instead of guessing containment, overlap or adjacency. Invalid geometries (for
example self-intersecting polygons) are refused with the reason.
| No | Yes | Yes | No |
convert_heightConvert a height between the ellipsoid (GNSS, drones) and a national height datum with the
official geoid model: AHD (AUSGeoid2020), ODN (OSGM15), NZVD2016 (NZGeoid2016), NAVD88
(GEOID18), or global EGM2008. Never estimate a geoid separation from memory: it is often
tens of metres and varies by metres across a region. | No | Yes | Yes | Yes |
geocodeFind coordinates for an address or place name (OpenStreetMap Nominatim).
Check `geospark.warnings` for ambiguous names (e.g. "Springfield") and ask the user
which one they mean, or add a region.
| No | Yes | Yes | Yes |
get_active_firesSatellite active-fire detections near a point (NASA FIRMS; the server needs a FIRMS_MAP_KEY). | No | Yes | Yes | Yes |
get_air_qualityLatest PM2.5, NO2, O3 from the nearest monitoring stations (OpenAQ; the server needs
an OPENAQ_API_KEY), with each station's data licence. | No | Yes | Yes | Yes |
get_elevationGround elevation in metres (Copernicus GLO-30, Open Elevation fallback), with its
vertical datum and accuracy. | No | Yes | Yes | Yes |
get_weatherCurrent weather and a daily forecast for a point (Open-Meteo, no key needed). | No | Yes | Yes | Yes |
isochroneWhere can you get to from a point within N minutes on foot, by bike or by car?
Returns one polygon per contour with its geodesic area (Valhalla over OpenStreetMap). | No | Yes | Yes | Yes |
line_of_sightWhether A and B can see each other over the terrain (Copernicus 30 m DEM, curvature and
refraction), the minimum clearance and where it occurs; with frequency_mhz, the first Fresnel
zone clearance of a radio link (60% clear is the usual rule). | No | Yes | Yes | Yes |
location_reportA dossier for a place: address, elevation, weather, and nearby amenities with exact
distances, as a GeoJSON map layer listing every data source used. Takes ~10-30 s. | No | Yes | Yes | Yes |
overture_featuresOpen global map data from Overture Maps, no API key: points of interest (with
categories), building footprints (height, floors, geodesic footprint area), road and path
segments (geodesic length), or `divisions`, the administrative areas containing the point
(country, region, city, neighbourhood). Results are nearest first, with distances in metres.
Can take 5-20 s on a cold cache. | No | Yes | Yes | Yes |
reverse_geocodeFind the address or place at a coordinate (OpenStreetMap Nominatim). | No | Yes | Yes | Yes |
routeDriving route between two points (OSRM over OpenStreetMap): line geometry, distance
in metres and duration in seconds. | No | Yes | Yes | Yes |
select_siteRank candidate sites in an area by geodesic distance to amenities you want nearby and
away from ones to avoid (OpenStreetMap data). Takes ~10-30 s. | No | Yes | Yes | Yes |
spatial_operationCompute a buffer (shape-preserving, metres), geodesic area or length, centroid or convex hull.
Returns the resulting geometry as GeoJSON with its measurements and units.
| No | Yes | Yes | No |
sun_positionThe Sun's apparent elevation and azimuth (from true north) at a place and time, and the
shadow a vertical object casts on level ground (NOAA solar position, refraction included). | No | Yes | Yes | Yes |
sun_timesSunrise, solar noon, sunset and day length on a date for a flat horizon; with terrain=True,
also the hours of direct sun once hills are taken into account. | No | Yes | Yes | Yes |
terrain_horizonThe skyline the terrain makes around a point: for each azimuth, the elevation angle of the
horizon and how far away the blocking terrain is (Copernicus 30 m DEM, Earth curvature and
refraction). Use for solar-panel shading, valley sunlight, or what hills hide. ~10-60 s. | No | Yes | Yes | Yes |
transform_coordinatesConvert coordinates between CRSs as the official transformation does: GDA94 to GDA2020,
MGA zones, British National Grid (OSTN15), NAD27 to NAD83 (NADCON), ITRF at an epoch, and
any other EPSG pair. Uses national grids (downloaded once), refuses PROJ's ballpark
approximations, and returns the operation and its stated accuracy. Use this instead of
applying datum parameters yourself. | No | Yes | Yes | Yes |
travel_time_matrixNetwork travel time (minutes) and distance (metres) from each origin to each destination.
Note: points here are [latitude, longitude] pairs. | No | Yes | Yes | Yes |
Details
- Registry status
- Active
- Published
- Nov 10, 2026
- Updated
- Nov 10, 2026
- Categories (suggested)
- Data and analyticsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared