# Geospatial System — Location Profile (remote · api.geospatialsystem.com)

Elevation, slope, terrain maps & 3-D surfaces for any site — near-global 30 m, US 10 m, AU/NZ 5 m.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.geospatialsystem.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-geospatialsystem-location-profile/api.md), [page](https://verifymcp.io/servers/com-geospatialsystem-location-profile/api)

## Channel facts

- Endpoint: `https://api.geospatialsystem.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `3.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 903 tokens (~100/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-geospatialsystem-location-profile https://api.geospatialsystem.com/mcp
```

### Codex

```toml
[mcp_servers.com-geospatialsystem-location-profile]
url = "https://api.geospatialsystem.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-geospatialsystem-location-profile": {
      "type": "remote",
      "url": "https://api.geospatialsystem.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-geospatialsystem-location-profile --url https://api.geospatialsystem.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-geospatialsystem-location-profile:
    url: "https://api.geospatialsystem.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-geospatialsystem-location-profile": {
      "type": "http",
      "url": "https://api.geospatialsystem.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (9)

### `list_datasets` (~21 tokens)

List all available elevation datasets on the Geospatial System server.

Output parameters:

- `result` (string)

### `LP_Get_Elevation` (~77 tokens)

Get the elevation in metres at a specific lat/lon coordinate.
Available on all tiers including Free.

Input parameters:

- `dataset_id` (string, required): Dataset identifier (see list_datasets).
- `lat` (number, required): Latitude in decimal degrees (WGS-84).
- `lon` (number, required): Longitude in decimal degrees (WGS-84).

Output parameters:

- `result` (string)

### `LP_Get_Elevation_Batch` (~72 tokens)

Get elevation for up to 100 points in one call.
Pass a list of objects: [{"lat":…,"lon":…,"dataset_id":…}, …]
Available on all tiers including Free.

Input parameters:

- `queries` (array, required): List of point dicts with lat, lon, dataset_id.

Output parameters:

- `result` (string)

### `LP_Get_Elevation_Stats` (~93 tokens)

Get elevation statistics (Min, Average, Max) for 3×3, 5×5 and 7×7 pixel
windows centred on the coordinates. Requires Pro or Enterprise key.

Input parameters:

- `dataset_id` (string, required): Dataset identifier.
- `lat` (number, required): Latitude in decimal degrees (WGS-84).
- `lon` (number, required): Longitude in decimal degrees (WGS-84).

Output parameters:

- `result` (string)

### `LP_Get_Slope_Stats` (~94 tokens)

Get terrain slope statistics (Min, Average, Max) in degrees for 3×3,
5×5 and 7×7 pixel windows. WGS-84 corrected. Requires Pro key.

Input parameters:

- `dataset_id` (string, required): Dataset identifier.
- `lat` (number, required): Latitude in decimal degrees (WGS-84).
- `lon` (number, required): Longitude in decimal degrees (WGS-84).

Output parameters:

- `result` (string)

### `LP_Get_Elevation_Chart` (~116 tokens)

Generate a range-box chart showing elevation Min/Avg/Max across three
neighbourhood window sizes. Returns a URL to the chart image.
Requires Pro key. Supports PNG / SVG / PDF.

Input parameters:

- `dataset_id` (string, required): Dataset identifier.
- `fmt` (string): Output format — 'png' (default), 'svg', or 'pdf'.
- `lat` (number, required): Latitude in decimal degrees (WGS-84).
- `lon` (number, required): Longitude in decimal degrees (WGS-84).

Output parameters:

- `result` (string)

### `LP_Get_Slope_Chart` (~114 tokens)

Generate a range-box chart showing terrain slope Min/Avg/Max across three
neighbourhood window sizes. Returns a URL to the chart image.
Requires Pro key. Supports PNG / SVG / PDF.

Input parameters:

- `dataset_id` (string, required): Dataset identifier.
- `fmt` (string): Output format — 'png', 'svg', or 'pdf'.
- `lat` (number, required): Latitude in decimal degrees (WGS-84).
- `lon` (number, required): Longitude in decimal degrees (WGS-84).

Output parameters:

- `result` (string)

### `LP_Get_Terrain_Map` (~157 tokens)

Generate a composite terrain map: Google Hybrid satellite (EPSG:3857) +
smoothed contours with labels + flow-direction arrows + location pin.
All layers are reprojected to EPSG:3857 — no overlay mismatch.
Requires Pro key. Supports PNG.

Input parameters:

- `dataset_id` (string, required): Dataset identifier.
- `fmt` (string): Output format — 'png'.
- `lat` (number, required): Latitude in decimal degrees (WGS-84).
- `lon` (number, required): Longitude in decimal degrees (WGS-84).
- `n_arrows` (integer): Flow arrow grid density (default 11).
- `offset` (integer): Half-window pixels (default 20 → 41×41 px area).

Output parameters:

- `result` (string)

### `LP_Get_Terrain_3D` (~159 tokens)

Generate a 3-D perspective terrain surface map (Plotly go.Surface)
coloured by elevation with a red spike pin marking the query location.
Requires Pro key. Supports PNG / HTML.

Input parameters:

- `azim_angle` (number): Camera azimuth angle in degrees (default 135).
- `dataset_id` (string, required): Dataset identifier.
- `elev_angle` (number): Camera elevation angle in degrees (default 45).
- `fmt` (string): Output format — 'png', or 'html'.
- `lat` (number, required): Latitude in decimal degrees (WGS-84).
- `lon` (number, required): Longitude in decimal degrees (WGS-84).
- `offset` (integer): Half-window pixels (default 20).

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-geospatialsystem-location-profile/api#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://api.geospatialsystem.com/mcp
- Authorisation metadata: https://api.geospatialsystem.com/.well-known/oauth-protected-resource/mcp
- Website: https://api.geospatialsystem.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-geospatialsystem-location-profile/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-geospatialsystem-location-profile/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-geospatialsystem-location-profile/api