← greenlandai.ai

INDIVIDUAL MCP TOOL

balance_proof

Cryptographic inclusion proof for YOUR wallet balance in the latest hourly transparency attestation (GET /wallet/balance-proof): leaf hash, Merkle sibling path, root, the anchoring BSV txid, and `verification` (the steps to recompute the root and check it on chain).

greenlandai.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.greenlandai.ai/mcp

No auth detected

Connect to this endpoint to inspect the live schema for balance_proof and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

greenlandai.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.greenlandai]
url = "https://mcp.greenlandai.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "greenlandai": {
      "type": "http",
      "url": "https://mcp.greenlandai.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: greenlandai
Remote MCP URL: https://mcp.greenlandai.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "greenlandai": {
      "url": "https://mcp.greenlandai.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "greenlandai": {
      "type": "http",
      "url": "https://mcp.greenlandai.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "greenlandai",
  "transport": "streamable-http",
  "url": "https://mcp.greenlandai.ai/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • look_from — Map lane: companies/infrastructure near a point (lat/lng + radius_km) or anchored on one entity `id`.
  • hops — Graph lane: labelled relationship hops between companies/entities (ownership, operates, supplies, …).
  • nearby — Entities near a location (the primitive `look_from` builds on).
  • mapdata — Map dataset (GET /mapdata).
  • map_viewport — Map lane: everything inside a bounding box — THE SCREEN (relays GET /api/v1/map.
  • company — One company's record and graph neighbourhood by id.
  • market_listings — Browse the RAREEAI marketplace: kind="providers" (listings) or "oracles".
  • market_match — Read one marketplace match by id, including its `escrow_terms` and this trade's typed fee/timeout fields.