io.github.winds3753/landbenchmark-mcp
Satellite land due-diligence: a green/caution/walk-away verdict with cited signals for any parcel.
Open source Open in the app JSON README (API)
About
Satellite land due-diligence: a green/caution/walk-away verdict with cited signals for any parcel.
Details
- Kind
- MCP servers
- Topic
- No topic detected
- Publisher
- winds3753
- Origin
- official
- Category
- ferramentas
- Transport
- local
- Version
- 0.1.1
- Last push
- 2026-07-30T06:20:42Z
- Repository state
- ativo
- Language
- JavaScript
- License
- MIT
- Added
- 2026-08-29 04:01:40
- Updated
- 2026-08-29 04:01:40
- Origin id
io.github.winds3753/landbenchmark-mcp
README
# landbenchmark-mcp
An [MCP](https://modelcontextprotocol.io) server that lets AI agents run **satellite land due-diligence** through [LandBenchmark](https://www.landbenchmark.com). 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
1. Get an API key at [landbenchmark.com/account](https://www.landbenchmark.com/account) → **API keys**.
2. 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"
}
}
}
}
```
**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
```sh
npm install
npm run build # → dist/index.js
npm test # verifies the API-key safety guard
```
## Links
- Product: <https://www.landbenchmark.com>
- API & MCP docs: <https://www.landbenchmark.com/developers>
> Informational only — not a survey, flood determination, or a substitute for on-site inspection and professional advice.