Should my agent depend on the MCP server io.github.uponex/gisgp?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

gisgp

io.github.uponex/gisgp

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

— the operator's own registry description reported

Publisher io.github.uponex · first seen 2026-08-12 · endpoint https://gisgp.com/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-solo — safe to depend on

Cluster rich-slow-solo · distinctiveness 0.805 (unusual). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency373 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools92

vs populationhigh

capabilities4

harnessB

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_a14a5bf5f55ce6208775c206 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

analyze_location assess_airspace_obstruction_proximity assess_datacenter_site assess_energy_community_credit assess_ev_charging_site assess_grid_exposure assess_pipeline_proximity assess_portfolio_climate_disclosure assess_property_hazard assess_property_hazard_x402 assess_protected_area_proximity assess_reforestation_site assess_renewable_site assess_site_due_diligence assess_supply_chain_redundancy assess_telecom_site assess_wildfire_risk audit_service buffer_geojson bundle_create_export_schedule bundle_export_fixed bundle_export_multi_format bundle_geocode_enrich bundle_migrate_convert bundle_migration_readiness calculate_route cancel_export_schedule centroids_geojson check_field_types check_service_health check_wallet_balance classify_land_cover compare_schemas convert_coordinates convex_hull_geojson count_features csv_to_geojson detect_coordinate_order discover_open_geodata dissolve_geojson dxf_to_geojson dxf_to_pdf_report embed_map_snippet envelope_geojson epsg_suggest estimate_cost export_geojson_to_excel export_geojson_to_pdf extract_domains find_layer_issues fix_geometry full_service_audit generate_static_map_image geocode_address geojson_diff geojson_to_csv geojson_to_dxf geojson_to_gpx geojson_to_kml geojson_to_shapefile geojson_to_wkt geometry_health_report geometry_stats georeference_dxf get_climate_history get_terrain_profile gpx_to_geojson gpx_to_kml grade_service guess_crs_from_coordinates kml_to_geojson kml_to_shapefile list_dxf_layers minimum_rotated_rectangle nearest_features_geojson offset_coordinates overlay_geojson query_features query_statistics rank_hazard_safe_sites rank_renewable_sites reduce_precision reproject_geojson rest_explore shapefile_to_geojson share_map simplify_geometry spatial_join_geojson tile_math validate_geojson voronoi_geojson wkt_to_geojson

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	92/92	✓
has a description	92/92	✓
description is substantive	92/92	✓
parameters are typed	92/92	✓
parameters are described	1/92	1/92

92 of 92 tools graded · 92 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.28.1

server version GISGP

Capabilities: experimental prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T20:00:17Z	ok_tools	200	373	2025-06-18
2026-08-12T05:35:29Z	ok_tools	200	376	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.uponex/gisgp.svg)](https://robinsaige.com/s/io.github.uponex/gisgp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview