Dataset context
List datasets, inspect metadata, and fetch bounded GeoJSON.
terminode.xyz
TermiNode exposes safe MCP tools for agents that need context without write, custody, market, or token-operation access.
Agent surface
The MCP server runs outside the asset canister and connects to source-of-truth canisters through operator configuration.
List datasets, inspect metadata, and fetch bounded GeoJSON.
Read feature versions, audit events, snapshot checksums, and proof-ready records.
Resolve safe fields such as external_reference, partner_feature_id, proof_receipt_id, or asset_boundary_id to either a sample fixture or the live canister-indexed spatial record after the customer dataset is indexed.
Read metrics and verification results without creating write risk.
Agent example
A local MCP-capable agent can answer which TermiNode polygon, version, and proof receipt are linked to an external reference. The answer can come from a built-in fixture during evaluation or from the live spatial canister index after deployment, without copying private partner payloads into the DApp.
external_reference=QGIS-ZONE-0426-A, external_reference=CAST-DEMO-001, or proof_receipt_id=TRMG-PROOF-IST-0426-A
Dataset, feature id, bbox, centroid, proof receipt id, and recommended read-only canister calls.
search_partner_evidence_page resolves indexed public metadata fields from the spatial canister once the index is built or rebuilt.
No write tools, token transfers, swap actions, custody flows, or private raw evidence payloads.