mcp-registry/com.geospatialsystem/location-profile · v3.3.1
Verdict. Geospatialsystem Location Profile MCP server answered 99.97% of Glimind's liveness checks over 30 days, better than 40% of MCP servers, with 1035 ms median handshake and 5 outages in 90 days. Its agent-readiness grade is A (90/100) across 9 tools, costing an agent about 1,486 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.97% | 40% of MCP servers |
| Median handshake latency | 1035 ms | 22% of MCP servers |
| p95 handshake latency | 3149 ms | — |
| Checks in 30 days | 4,892 | — |
| Outages, 90 days | 5 | — |
| Median recovery | 2 min | — |
| Agent-readiness score | 90/100 (A) | 69% of MCP servers |
| Tools | 9 | — |
| Tool-list size for an agent | ~1,486 tokens | 59% of MCP servers |
| Days observed | 29 | — |
As of 2026-10-26 18:42 UTC, the Geospatialsystem Location Profile MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 2 minutes.
Elevation, slope, terrain maps & 3-D surfaces for any site — near-global 30 m, US 10 m, AU/NZ 5 m.
Claude Code
claude mcp add --transport http geospatialsystem-location-profile-mcp-se https://api.geospatialsystem.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"geospatialsystem-location-profile-mcp-se": {
"type": "http",
"url": "https://api.geospatialsystem.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.geospatialsystem%2Flocation-profile/fixes
{
"name": "LP_Get_Elevation",
"description": "Get the elevation in metres at a specific lat/lon coordinate.\nAvailable on all tiers including Free.",
"inputSchema": {
"type": "object",
"required": [
"lat",
"lon",
"dataset_id"
],
"properties": {
"lat": {
"type": "number",
"description": "Latitude in decimal degrees (WGS-84)."
},
"lon": {
"type": "number",
"description": "Longitude in decimal degrees (WGS-84)."
},
"dataset_id": {
"type": "string",
"description": "Dataset identifier (see list_datasets)."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "LP_Get_Elevation_Batch",
"description": "Get elevation for up to 100 points in one call.\nPass a list of objects: [{\"lat\":…,\"lon\":…,\"dataset_id\":…}, …]\nAvailable on all tiers including Free.",
"inputSchema": {
"type": "object",
"required": [
"queries"
],
"properties": {
"queries": {
"type": "array",
"items": {},
"description": "List of point dicts with lat, lon, dataset_id."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "LP_Get_Elevation_Chart",
"description": "Generate a range-box chart showing elevation Min/Avg/Max across three\nneighbourhood window sizes. Returns a URL to the chart image.\nRequires Pro key. Supports PNG / SVG / PDF.",
"inputSchema": {
"type": "object",
"required": [
"lat",
"lon",
"dataset_id"
],
"properties": {
"fmt": {
"type": "string",
"default": "png",
"description": "Output format — 'png' (default), 'svg', or 'pdf'."
},
"lat": {
"type": "number",
"description": "Latitude in decimal degrees (WGS-84)."
},
"lon": {
"type": "number",
"description": "Longitude in decimal degrees (WGS-84)."
},
"dataset_id": {
"type": "string",
"description": "Dataset identifier."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.geospatialsystem/location-profile"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.geospatialsystem/location-profile"}) over MCP.
LP_Get_Terrain_3D ~266 tokensLP_Get_Terrain_Map ~252 tokensLP_Get_Elevation_Chart ~187 tokensLP_Get_Slope_Chart ~184 tokensLP_Get_Elevation_Stats ~147 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.geospatialsystem%2Flocation-profile?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.geospatialsystem%2Flocation-profile?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.geospatialsystem%2Flocation-profile.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.geospatialsystem%2Flocation-profile.svg :target: https://glimind.com/server/mcp-registry%2Fcom.geospatialsystem%2Flocation-profile?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b936bdd89989e744…, first seen 2026-10-17, included at leaf 4051 of 74,788. Version history · verify what your client received.
Compare: most reliable data servers · most reliable media servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 18:42 UTC, the Geospatialsystem Location Profile MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 2 minutes.
Geospatialsystem Location Profile MCP server advertises 9 tools, including LP_Get_Elevation, LP_Get_Elevation_Batch, LP_Get_Elevation_Chart, LP_Get_Elevation_Stats, LP_Get_Slope_Chart.
Point your MCP client at this streamable-http endpoint: https://api.geospatialsystem.com/mcp
Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.