Is the Uponex Gisgp MCP server down?

mcp-registry/io.github.uponex/gisgp · v1.28.1

Also listed as glama/uponex/gisgp-gis-tools

healthy
Last checked 2026-10-21 11:33 UTC · handshake 512ms

As of 2026-10-21 11:33 UTC, the Uponex Gisgp MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 69 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
99.7%
checks observed
4,106
outages (90d)
69
tools
112

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

Install Uponex Gisgp MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http uponex-gisgp-mcp-server https://gisgp.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "uponex-gisgp-mcp-server": {
      "type": "http",
      "url": "https://gisgp.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (62/100)

D (62/100): 0 error(s), 6 warning(s) across 112 tool(s); ~19,723 tokens of tool definitions.
Scores higher than 0% of 15,467 MCP servers Glimind has audited.
Its tool list costs an agent ~19,723 tokens per session — more than 95% of servers.
62 → 62 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints18
Token cost35
Client compatibility100
Protocol100
Reliability85
Stability100

What to fix (6)

112 of 112 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 →

Tools: analyze_location, assess_airspace_obstruction_proximity, assess_datacenter_site, assess_energy_community_credit, assess_ev_charging_site and 107 more

112 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

252 parameter(s) across 111 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: analyze_location, assess_airspace_obstruction_proximity, assess_datacenter_site, assess_energy_community_credit, assess_ev_charging_site and 106 more

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: bundle_create_export_schedule, cancel_export_schedule, detect_coordinate_order

Loading this server's tool list costs an agent ~19,723 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

Handshake + tools/list takes ~1,775 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Auto-fix: 34 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 111 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.uponex%2Fgisgp/fixes

analyze_location 1 change
{
  "name": "analyze_location",
  "description": "Reverse-geocode a WGS84 point to country/region/locality via OSM\n    Nominatim (no key, free — fair-use rate limited, best-effort). Returns\n    JSON: {ok, display_name, country, country_code, region, locality, source}.\n    ",
  "inputSchema": {
    "type": "object",
    "title": "analyze_locationArguments",
    "required": [
      "lon",
      "lat"
    ],
    "properties": {
      "lat": {
        "type": "number",
        "title": "Lat"
      },
      "lon": {
        "type": "number",
        "title": "Lon"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
bundle_create_export_schedule 1 change
{
  "name": "bundle_create_export_schedule",
  "description": "PAID PER DELIVERY (30 credits each time it fires, NOT at creation — free to\n    create/cancel) — the only MCP tool that exposes GISGP's core recurring-export\n    product to agents: creates a schedule that re-exports a FeatureServer layer on\n    its own and POSTs the file straight to your own webhook_url, no email/web UI\n    account needed beyond the API key. Reuses the same scheduler that runs the paid\n    web app's scheduled exports (fires within ~5 min of the due time).\n\n    format: \"csv\", \"ge",
  "inputSchema": {
    "type": "object",
    "title": "bundle_create_export_scheduleArguments",
    "required": [
      "service_url",
      "format",
      "webhook_url"
    ],
    "properties": {
      "token": {
        "type": "string",
        "title": "Token",
        "default": ""
      },
      "where": {
        "type": "string",
        "title": "Where",
        "default": "1=1"
      },
      "format": {
        "type": "string",
        "title": "Format"
      },
      "weekday": {
        "type": "integer",
        "title": "Weekday",
        "default": 0
      },
      "monthday": {
        "type": "integer",
        "title": "Monthday",
        "default": 1
      },
      "run_hour": {
        "type": "integer",
        "title": "Run Hour",
        "default": 6
      },
      "frequency": {
        "type": "string",
        "title": "Frequency",
        "default": "daily"
      },
      "service_url": {
        "type": "string",
        "title": "Service Url"
      },
      "webhook_url": {
        "type": "string",
        "title": "Webhook Url"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
bundle_export_fixed 1 change
{
  "name": "bundle_export_fixed",
  "description": "PAID (150 credits) — fetch ALL records from a live FeatureServer layer\n    (no 50-record preview cap), auto-repair invalid geometries (GEOS\n    make_valid), and scan for common problems, in one call. Replaces an\n    uncapped query_features call (itself a paid-only capability) plus\n    fix_geometry plus find_layer_issues. Requires Authorization: Bearer\n    <api_key> and sufficient credits balance.\n\n    Returns JSON: {ok, feature_count, fixed_count, truncated, issues,\n    issue_count, geojson} — g",
  "inputSchema": {
    "type": "object",
    "title": "bundle_export_fixedArguments",
    "required": [
      "service_url"
    ],
    "properties": {
      "token": {
        "type": "string",
        "title": "Token",
        "default": ""
      },
      "where": {
        "type": "string",
        "title": "Where",
        "default": "1=1"
      },
      "service_url": {
        "type": "string",
        "title": "Service Url"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

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/io.github.uponex/gisgp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.uponex/gisgp"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.uponex%2Fgisgp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.uponex%2Fgisgp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.uponex%2Fgisgp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.uponex%2Fgisgp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.uponex%2Fgisgp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.uponex%2Fgisgp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:979c6233e674bc62…, first seen 2026-10-18, included at leaf 22539 of 39,284. Version history · verify what your client received.

Tools (112)

Compare: most reliable data servers · most reliable other servers · most reliable finance servers · most reliable productivity servers · most reliable web servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Uponex Gisgp MCP server down right now?

As of 2026-10-21 11:33 UTC, the Uponex Gisgp MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 69 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Uponex Gisgp MCP server provide?

Uponex Gisgp MCP server advertises 112 tools, including analyze_location, assess_airspace_obstruction_proximity, assess_datacenter_site, assess_energy_community_credit, assess_ev_charging_site.

How do I install Uponex Gisgp MCP server?

Point your MCP client at this streamable-http endpoint: https://gisgp.com/mcp

Is the Uponex Gisgp MCP server safe to connect to an AI agent?

Glimind scanned all 112 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.

Operator of Uponex Gisgp MCP server?

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.

Feedback
Help us improve