Geospatial System — Location Profile
REMOTE · API.GEOSPATIALSYSTEM.COM · SCANNED AUG 3
Elevation, slope, terrain maps & 3-D surfaces for any site — near-global 30 m, US 10 m, AU/NZ 5 m.
Available components
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. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 903 tokens (~100/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.geospatialsystem.com
claude mcp add --transport http com-geospatialsystem-location-profile https://api.geospatialsystem.com/mcp
[mcp_servers.com-geospatialsystem-location-profile] url = "https://api.geospatialsystem.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-geospatialsystem-location-profile": {
"type": "remote",
"url": "https://api.geospatialsystem.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-geospatialsystem-location-profile --url https://api.geospatialsystem.com/mcp --transport streamable-http
mcp_servers:
com-geospatialsystem-location-profile:
url: "https://api.geospatialsystem.com/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +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.
- 29 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://api.geospatialsystem.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=geospatialsystem.com | CN=YE1,O=Let's Encrypt,C=US | 22 Jul 2026 | 20 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 57210c1c5a8d3e6c4c083f17482aacd1594 |
| SANs: api.geospatialsystem.com, geospatialsystem.com, www.geospatialsystem.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of api.geospatialsystem.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| geospatialsystem.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.geospatialsystem.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.geospatialsystem.com/mcp | HTTPS enforced | 301 | https://api.geospatialsystem.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
list_datasets ~21
List all available elevation datasets on the Geospatial System server.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
LP_Get_Elevation ~77
Get the elevation in metres at a specific lat/lon coordinate. Available on all tiers including Free.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Dataset identifier (see list_datasets). |
| lat | number | yes | Latitude in decimal degrees (WGS-84). |
| lon | number | yes | Longitude in decimal degrees (WGS-84). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
LP_Get_Elevation_Batch ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| queries | array | yes | List of point dicts with lat, lon, dataset_id. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
LP_Get_Elevation_Chart ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Dataset identifier. |
| fmt | string | — | Output format — 'png' (default), 'svg', or 'pdf'. |
| lat | number | yes | Latitude in decimal degrees (WGS-84). |
| lon | number | yes | Longitude in decimal degrees (WGS-84). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
LP_Get_Elevation_Stats ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Dataset identifier. |
| lat | number | yes | Latitude in decimal degrees (WGS-84). |
| lon | number | yes | Longitude in decimal degrees (WGS-84). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
LP_Get_Slope_Chart ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Dataset identifier. |
| fmt | string | — | Output format — 'png', 'svg', or 'pdf'. |
| lat | number | yes | Latitude in decimal degrees (WGS-84). |
| lon | number | yes | Longitude in decimal degrees (WGS-84). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
LP_Get_Slope_Stats ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Dataset identifier. |
| lat | number | yes | Latitude in decimal degrees (WGS-84). |
| lon | number | yes | Longitude in decimal degrees (WGS-84). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
LP_Get_Terrain_3D ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| azim_angle | number | — | Camera azimuth angle in degrees (default 135). |
| dataset_id | string | yes | Dataset identifier. |
| elev_angle | number | — | Camera elevation angle in degrees (default 45). |
| fmt | string | — | Output format — 'png', or 'html'. |
| lat | number | yes | Latitude in decimal degrees (WGS-84). |
| lon | number | yes | Longitude in decimal degrees (WGS-84). |
| offset | integer | — | Half-window pixels (default 20). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
LP_Get_Terrain_Map ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Dataset identifier. |
| fmt | string | — | Output format — 'png'. |
| lat | number | yes | Latitude in decimal degrees (WGS-84). |
| lon | number | yes | 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.