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.

io.github.uponex/gisgp

REMOTE · GISGP.COM · SCANNED SEP 20

GIS tools for AI agents: 65 free tools + 8 paid (hazard/site-scouting/GeoJSON export)

Available components

0 this week 76 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 Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 12675 tokens (~121/item across 104 items; 104 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (99% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "share_map" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 105 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 io.github.uponex/gisgp MCP server?

io.github.uponex/gisgp is a hosted endpoint at https://gisgp.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 · gisgp.com

# add to Claude Code
claude mcp add --transport http uponex-gisgp 'https://gisgp.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "uponex-gisgp": {
      "url": "https://gisgp.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "uponex-gisgp": {
      "type": "http",
      "url": "https://gisgp.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.uponex-gisgp]
url = "https://gisgp.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uponex-gisgp": {
      "type": "remote",
      "url": "https://gisgp.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add uponex-gisgp --url 'https://gisgp.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  uponex-gisgp:
    url: "https://gisgp.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "uponex-gisgp": {
      "Transport": "http",
      "Url": "https://gisgp.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add uponex-gisgp -t streamable-http -u 'https://gisgp.com/mcp'
// mcp.json
{
  "mcpServers": {
    "uponex-gisgp": {
      "type": "http",
      "url": "https://gisgp.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.

  • 16 Sept 26 0
    • New tool “discover_open_geodata_pro” functional
    • New tool “flatgeobuf_to_geojson” functional
    • New tool “geojson_to_flatgeobuf” functional
    • New tool “geojson_to_mapinfo_tab” functional
    • New tool “get_elevation_profile” functional
    • New tool “mapinfo_tab_to_geojson” functional
  • 13 Sept 26 0
    • New tool “get_river_flow_status” functional
  • 4 Sept 26 0
    • New tool “csv_to_gpx” functional
    • New tool “gpx_to_csv” functional
    • New tool “gpx_to_shapefile” functional
    • New tool “kml_to_gpx” functional
    • New tool “shapefile_to_gpx” functional
  • 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
  • 24 Aug 26 +1

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

  • 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
  • 10 Aug 26 0
    • Tool “centroids_geojson” rewrote its description, which is the text the model reads security
    • Tool “convex_hull_geojson” rewrote its description, which is the text the model reads security
    • Tool “csv_to_geojson” rewrote its description, which is the text the model reads security
    • Tool “envelope_geojson” rewrote its description, which is the text the model reads security
    • Tool “geojson_to_csv” rewrote its description, which is the text the model reads security
    • Tool “geojson_to_kml” rewrote its description, which is the text the model reads security
    • Tool “geojson_to_shapefile” rewrote its description, which is the text the model reads security
    • Tool “geojson_to_wkt” rewrote its description, which is the text the model reads security
    • Tool “get_terrain_profile” rewrote its description, which is the text the model reads security
    • Tool “gpx_to_geojson” rewrote its description, which is the text the model reads security
    • Tool “gpx_to_kml” rewrote its description, which is the text the model reads security
    • Tool “kml_to_geojson” rewrote its description, which is the text the model reads security
    • Tool “kml_to_shapefile” rewrote its description, which is the text the model reads security
    • Tool “minimum_rotated_rectangle” rewrote its description, which is the text the model reads security
    • Tool “reduce_precision” rewrote its description, which is the text the model reads security
    • Tool “reproject_geojson” rewrote its description, which is the text the model reads security
    • Tool “simplify_geometry” rewrote its description, which is the text the model reads security
    • Tool “validate_geojson” rewrote its description, which is the text the model reads security
    • Tool “voronoi_geojson” rewrote its description, which is the text the model reads security
    • Tool “wkt_to_geojson” rewrote its description, which is the text the model reads security
    • Schema quality: 107 → 120 functional
    • New tool “assess_airspace_obstruction_proximity” functional
    • New tool “bundle_geocode_enrich” functional
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 20 Sept 2026 · Probed https://gisgp.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gisgp.com CN=WE1,O=Google Trust Services,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA256 2254d5df6d28d0750e02817bd4583f35
SANs: gisgp.com, *.gisgp.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of gisgp.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
gisgp.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=63072000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: blob: https:; font-src 'self' data: https:; media-src 'self' https:; connect-src 'self' https: wss: data:; frame-src 'self' https:; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self' https:; frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), camera=(), microphone=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gisgp.com/mcp Verified 200
http (plaintext) http://gisgp.com/mcp HTTPS enforced 301 https://gisgp.com/mcp
MCP tools · 104 exposed · ~12,582 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
tile_math ~85

Convert a WGS84 lon/lat + zoom level to Slippy Map (XYZ) tile x/y, that tile's lon/lat bbox, and its Bing quadkey. Returns JSON {ok, zoom, x, y, tile_bbox, quadkey}.

NameTypeReqDescription
latnumberyes
lonnumberyes
zoomintegeryes
NameTypeReqDescription
resultstringyes

No examples provided.

validate_geojson ~119

Check whether a GeoJSON file/string is valid — catches broken geometry, malformed structure, self-intersections, and out-of-range coordinates before you try to use the file elsewhere (e.g. "is this GeoJSON valid", "why won't my GeoJSON load", "lint my GeoJSON", "check topology errors"). Validates RFC 7946 structure, topology, and WGS84 coordinate ranges. Returns a JSON report: {valid, errors, warnings, stats}.

NameTypeReqDescription
geojsonstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

voronoi_geojson ~97

Divide space into regions closest to each input point (Voronoi diagram) — e.g. "find the service area for each location", "which points are closest to which store", "Voronoi/Thiessen polygons". Non-point features use their centroid. Needs at least 2 points. Returns JSON {ok, cell_count, geojson}.

NameTypeReqDescription
geojsonstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

wkt_to_geojson ~80

Convert a WKT (Well-Known Text) geometry string — the format PostGIS/SQL geometry columns print by default — to GeoJSON (e.g. "this came from a PostGIS query", "WKT to GeoJSON", "parse this POLYGON(...) string").

NameTypeReqDescription
wktstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the io.github.uponex/gisgp MCP server?

io.github.uponex/gisgp is an MCP server listed in the public MCP registry as io.github.uponex/gisgp. GIS tools for AI agents: 65 free tools + 8 paid (hazard/site-scouting/GeoJSON export). This page covers its hosted endpoint (https://gisgp.com/mcp).

Is the io.github.uponex/gisgp MCP server safe to use?

io.github.uponex/gisgp scores 76 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 io.github.uponex/gisgp MCP server expose?

io.github.uponex/gisgp exposes 104 tools: convert_coordinates, validate_geojson, geojson_to_csv, count_features, extract_domains, and 99 more. Their descriptions and schemas cost roughly 12,582 tokens of context every time the server is loaded.

Does the io.github.uponex/gisgp MCP server require authentication?

No. We connected to io.github.uponex/gisgp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.uponex/gisgp MCP server still maintained?

io.github.uponex/gisgp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.