Landbenchmark MCP server
io.github.winds3753/landbenchmark-mcp·v0.1.1Satellite land due-diligence: a green/caution/walk-away verdict with cited signals for any parcel.
0 stars21 downloads/wk
Reviews
Write oneNobody has reviewed Landbenchmark yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Landbenchmark tools (1, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
analyze_parcelwrite actionRun a satellite land due-diligence analysis on a parcel of land and return a
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 56 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How Landbenchmark compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 45% of 48,255 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 100%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 21
- more than 8% of 12,191 servers with a package
What its tools let an agent do: 1 change
Install Landbenchmark in Claude Code, Cursor or VS Code
Runs npx -y landbenchmark-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add landbenchmark-mcp -- npx -y landbenchmark-mcp
What the publisher says
From the Landbenchmark repository's README, as published. We do not edit it. Read it on GitHub
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:
{
"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.) TERRAINBASE_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
Returns a plain-text verdict summary with the flagged signals and a link to the full report.
Build
npm install
npm run build # → dist/index.js
npm test # verifies the API-key safety guardLinks
- Product:
- API & MCP docs:
Informational only — not a survey, flood determination, or a substitute for on-site inspection and professional advice.
Nothing above is checked by us. What we check is on the safety report.
Landbenchmark: common questions
- Is Landbenchmark MCP server safe?
- Mostly: it is graded B (75/100). Read the Landbenchmark safety report
- How do I install Landbenchmark?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Landbenchmark need an API key?
- Yes. The registry entry asks for
TERRAIN_API_KEY. - Is Landbenchmark maintained?
- The last commit was 97 days ago (2026-07-30). The latest release is v0.1.1.
- How does Landbenchmark compare with other MCP servers?
- safety score 75/100 (higher than 45% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 100% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.