Landbenchmark Mcp

io.github.winds3753Published by GitHub account winds3753v0.1.1Updated Oct 24, 2026

Satellite land due-diligence: a green/caution/walk-away verdict with cited signals for any parcel.

VerifiedSTDIODesktop onlyLocation & Lifestyle Data & Analytics

Server details

Identifier: io.github.winds3753/landbenchmark-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account winds3753 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.winds3753%2Flandbenchmark-mcp.svg)](https://sourceweft.com/mcp/io.github.winds3753%2Flandbenchmark-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant run satellite land due-diligence on a parcel and return a green, caution, or walk-away verdict with cited signals.

What you can do: Exposes one tool, analyze_parcel, which takes a parcel centre as latitude and longitude or a GeoJSON geometry, plus an optional label and a lite or full mode. It returns a plain-text verdict summary listing flagged signals such as flooding, slope and buildability, soil, hazards, and access, along with a link to the full report. Lite mode takes about a minute; full mode produces a deeper multi-year satellite report in roughly three to four minutes.
When to use it: Useful when someone asks an assistant whether a piece of land is worth buying and wants an answer grounded in observed satellite data rather than guesswork. Suited to early due-diligence screening of parcels before commissioning surveys or site visits.
Requirements: Runs locally over stdio, typically via npx from the npm package landbenchmark-mcp, so Node.js is needed. Requires a LandBenchmark API key in TERRAIN_API_KEY and a base URL in TERRAIN_BASE_URL; both are required and there is no default base URL. Network access to the configured host is needed, and the client must be desktop-based.

Before you install

The API key in TERRAIN_API_KEY is sent to the host named in TERRAIN_BASE_URL in an Authorization header, so that host receives the key; the server refuses to start without a base URL and refuses plain http except to localhost. The tool sends parcel coordinates or geometry to a third-party service. Output is informational only and is not a survey, flood determination, or a substitute for on-site inspection and professional advice.

Installation

In SourceWeft

Open Landbenchmark Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

landbenchmark-mcp

An MCP server that lets AI agents run satellite land due-diligence through LandBenchmark. It exposes one tool, analyze_parcel, that returns a green / caution / walk-away verdict with cited signals (flooding, slope & buildability, soil, hazards, access) for any parcel.

Why

When someone asks their AI assistant "is this land any good to buy?", the agent can call LandBenchmark and answer with observed, cited satellite data instead of guessing.

Setup

Get an API key at landbenchmark.com/account → API keys.
Add the server to your MCP client config:

json

{  "mcpServers": {    "terrain": {      "command": "npx",      "args": ["-y", "landbenchmark-mcp"],      "env": {        "TERRAIN_API_KEY": "tk_live_...",        "TERRAIN_BASE_URL": "https://www.landbenchmark.com"      }    }  }}

{  "mcpServers": {    "terrain": {      "command": "npx",      "args": ["-y", "landbenchmark-mcp"],      "env": {        "TERRAIN_API_KEY": "tk_live_...",        "TERRAIN_BASE_URL": "https://www.landbenchmark.com"      }    }  }}

Both env vars are required. (TERRAIN_* is the internal engine name — LandBenchmark runs on the Terrain analysis engine.) TERRAIN_BASE_URL has no default on purpose: every request sends your API key to that host in an Authorization header, so the server refuses to start rather than guess where it goes. It also refuses to send a key over plain http:// to anything but localhost.

Works with any MCP-capable client — Claude Desktop, Claude Code, and agent frameworks.

Tool: `analyze_parcel`

Param	Type	Notes
`lat`, `lon`	number	Parcel centre (WGS84). Provide these or `geometry`.
`geometry`	GeoJSON	Polygon or Point (alternative to lat/lon).
`label`	string	Optional parcel name.
`mode`	`"lite"` \| `"full"`	`lite` (default) ≈ 1 min; `full` = deep multi-year satellite report ≈ 3–4 min.

Returns a plain-text verdict summary with the flagged signals and a link to the full report.

Build

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts