Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Geospatial System — Location Profile

REMOTE · API.GEOSPATIALSYSTEM.COM · SCANNED SEP 22

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

Available components

remote · api.geospatialsystem.com 82
0 this week 82 Trust /100
Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability84
  • 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Geospatial System — Location Profile MCP server?

Geospatial System — Location Profile is a hosted endpoint at https://api.geospatialsystem.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.geospatialsystem.com

# add to Claude Code
claude mcp add --transport http com-geospatialsystem-location-profile 'https://api.geospatialsystem.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-geospatialsystem-location-profile": {
      "url": "https://api.geospatialsystem.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-geospatialsystem-location-profile": {
      "type": "http",
      "url": "https://api.geospatialsystem.com/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-geospatialsystem-location-profile --url 'https://api.geospatialsystem.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-geospatialsystem-location-profile:
    url: "https://api.geospatialsystem.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-geospatialsystem-location-profile": {
      "Transport": "http",
      "Url": "https://api.geospatialsystem.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-geospatialsystem-location-profile -t streamable-http -u 'https://api.geospatialsystem.com/mcp'
// mcp.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 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.

  • 26 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 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
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 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
  • 27 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
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 22 Sept 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 20 Sept 2026 19 Dec 2026 ECDSA 256 ECDSA-SHA384 675168916c40feda17ac6d88808cbba3092
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

Background: What to check on a remote MCP endpoint →

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

Background: How OAuth 2.1 works in the 2026 MCP spec →

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
MCP tools · 9 exposed · ~903 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_datasets ~21

List all available elevation datasets on the Geospatial System server.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

LP_Get_Elevation ~77

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

NameTypeReqDescription
dataset_idstringyesDataset identifier (see list_datasets).
latnumberyesLatitude in decimal degrees (WGS-84).
lonnumberyesLongitude in decimal degrees (WGS-84).
NameTypeReqDescription
resultstringyes–

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.

NameTypeReqDescription
queriesarrayyesList of point dicts with lat, lon, dataset_id.
NameTypeReqDescription
resultstringyes–

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.

NameTypeReqDescription
dataset_idstringyesDataset identifier.
fmtstring–Output format — 'png' (default), 'svg', or 'pdf'.
latnumberyesLatitude in decimal degrees (WGS-84).
lonnumberyesLongitude in decimal degrees (WGS-84).
NameTypeReqDescription
resultstringyes–

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.

NameTypeReqDescription
dataset_idstringyesDataset identifier.
latnumberyesLatitude in decimal degrees (WGS-84).
lonnumberyesLongitude in decimal degrees (WGS-84).
NameTypeReqDescription
resultstringyes–

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.

NameTypeReqDescription
dataset_idstringyesDataset identifier.
fmtstring–Output format — 'png', 'svg', or 'pdf'.
latnumberyesLatitude in decimal degrees (WGS-84).
lonnumberyesLongitude in decimal degrees (WGS-84).
NameTypeReqDescription
resultstringyes–

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.

NameTypeReqDescription
dataset_idstringyesDataset identifier.
latnumberyesLatitude in decimal degrees (WGS-84).
lonnumberyesLongitude in decimal degrees (WGS-84).
NameTypeReqDescription
resultstringyes–

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.

NameTypeReqDescription
azim_anglenumber–Camera azimuth angle in degrees (default 135).
dataset_idstringyesDataset identifier.
elev_anglenumber–Camera elevation angle in degrees (default 45).
fmtstring–Output format — 'png', or 'html'.
latnumberyesLatitude in decimal degrees (WGS-84).
lonnumberyesLongitude in decimal degrees (WGS-84).
offsetinteger–Half-window pixels (default 20).
NameTypeReqDescription
resultstringyes–

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.

NameTypeReqDescription
dataset_idstringyesDataset identifier.
fmtstring–Output format — 'png'.
latnumberyesLatitude in decimal degrees (WGS-84).
lonnumberyesLongitude in decimal degrees (WGS-84).
n_arrowsinteger–Flow arrow grid density (default 11).
offsetinteger–Half-window pixels (default 20 → 41×41 px area).
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the Geospatial System — Location Profile MCP server?

Geospatial System — Location Profile is an MCP server listed in the public MCP registry as com.geospatialsystem/location-profile. Elevation, slope, terrain maps & 3-D surfaces for any site, near-global 30 m, US 10 m, AU/NZ 5 m. This page covers its hosted endpoint (https://api.geospatialsystem.com/mcp).

Is the Geospatial System — Location Profile MCP server safe to use?

Geospatial System — Location Profile scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Geospatial System — Location Profile MCP server expose?

Geospatial System — Location Profile exposes 9 tools: list_datasets, LP_Get_Elevation, LP_Get_Elevation_Batch, LP_Get_Elevation_Stats, LP_Get_Slope_Stats, and 4 more. Their descriptions and schemas cost roughly 903 tokens of context every time the server is loaded.

Does the Geospatial System — Location Profile MCP server require authentication?

No. We connected to Geospatial System — Location Profile without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Geospatial System — Location Profile MCP server still maintained?

Geospatial System — Location Profile is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.