Enables Bitcoin Lightning micropayments for paying per use of climate analytics tools, including credit purchases and balance checks via the Tollbooth DPYC payment system.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Good Earth Show the GDD season curve for my farm polygon compared to last 10 seasons."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Region-scoped climate analytics for small specialty-crop and flower farms, monetized with Tollbooth DPYC™ Bitcoin Lightning micropayments.
Sibling of the Good Brew store.
A farm is not a point. A bench and a hollow on the same acreage do not share a frost date, and every free weather calculator answers for a pin.
Good Earth answers for ground. Every tool accepts a GeoJSON polygon or a
{lat, lon, radius_m} pin, samples the terrain inside it, and returns an
aggregate plus the spread across it. That spread is the product: it tells
a grower whether one planting date serves the whole block.
YOU (operator, human in the loop)
│ │
│ set & tune prices │ drive credential intake
▼ ▼
┌───────────────┐ ┌──────────────────────────────────────────────┐
│ Pricing Studio│ prices │ Good Earth — OPERATOR MCP │
│ (iOS) ├───────▶│ FastMCP · deployed on Horizon │
└───────────────┘ Neon │ ┌────────────────────────────────────────┐ │
│ │ region · sources · gdd · season │ │
Patron (Citizen) │ │ @runtime.paid_tool(FROZEN_UUID) tools │ │
+ MCP client ─────────▶│ ├────────────────────────────────────────┤ │
(Claude, the SPA) npub │ │ tollbooth-dpyc SDK (the wheel) │ │
+sats │ │ ledger · vault (AES-256-GCM) · pricing │ │
│ │ ConstraintGate · Secure Courier·audit │ │
│ └────────────────────────────────────────┘ │
└───┬─────────┬──────────┬───────────┬─────────┘
▼ ▼ ▼ ▼
Neon Postgres BTCPay▶ Sponsor Nostr relays
(your schema) Lightning Authority proofs·courier
ledger+pricing invoices certify + DMs·audit
provision │
Open-Meteo archive ◀── domain │ ▼
forecast · elevation calls └──▶ DPYC Oracle +
dpyc-communityRelated MCP server: CropProphEU
This is the design decision the whole product rests on, so it is stated plainly rather than buried.
The free gridded temperature feeds resolve about 9 km. Two sample points on one farm land in the same cell and return byte-identical numbers — reporting that as "the range across your region" would be a lie dressed as data. Terrain, however, resolves at 90 m, and terrain is what varies within a farm.
So Good Earth reads the regional signal from the coarse feed and derives within-region variation from elevation:
Effect | Applies to | Why |
Lapse rate (3.57 °F / 1000 ft) | max and min | Higher ground is colder |
Cold-air drainage (capped at 6 °F) | min only | Dense cold air pools in hollows on the still, clear nights when frost happens |
Every response carries the native resolution of each feed it used, so a grower is never sold precision the data does not contain.
Tool | Phase | Answers |
| T1 — shipped | Heat accumulation across a region, vs the last 10 seasons |
| T2 | Heat + water + light in one priced call |
| T2 | First-frost dates and near-term risk, with drainage spread |
| T3 | Light and water lenses |
| T4 | Per-planting timing |
| T5 | Model GDD vs accumulated; crossing dates |
| T6 | Per-region bias correction from patron field reports |
Standard DPYC tools (check_balance, purchase_credits, Secure Courier,
Oracle, pricing, constraints) come from the wheel via
register_standard_tools — none of it is reimplemented here.
All free, all public, no API key.
Source | Role | Native resolution |
Open-Meteo archive (ERA5) | Observed daily max/min | ~9 km |
Open-Meteo forecast | 7-day extension | ~11 km |
Open-Meteo elevation (SRTM) | Terrain downscaling | ~90 m |
A whole-region season read costs three upstream requests regardless of sample count: sample points are folded onto the archive's own grid so a distinct cell is fetched once, and the ten-season normals band is one span request sliced locally rather than ten separate calls.
Nostr keypair — generate one (nak key generate); the nsec is the
single env var the server needs (TOLLBOOTH_NOSTR_OPERATOR_NSEC).
Sponsor Authority — register; it provisions your Neon database.
Secure Courier — deliver btcpay_host, btcpay_api_key,
btcpay_store_id via goodearth_request_credential_channel. Never as
env vars, never in code.
Set prices in Pricing Studio — new tools start unpriced and nobody can call an unpriced tool.
Deploy on Horizon — fastmcp.json is already wired.
Get Pricing Studio (iOS). It reads and writes the pricing model live in Neon, so prices never live in code — surge, happy-hour, loyalty discounts and free trials are the thing a flat paywall can never give you.
frontend/ carries the Good Earth app (the taxsort-mcp pattern — one repo,
React app inside). Sign-in, the proof envelope, and the Nostr profile panel
are the fleet's existing modules, borrowed rather than rewritten. Patron
state lives on Nostr as NIP-44-encrypted NIP-78 events under the
goodearth/* namespace — no accounts, and the farm's data never lives on
the operator's server.
uv venv --python python3.12 # coincurve has no 3.14 wheel
uv pip install -e ".[dev]"
ruff check .
pytest -v
python -m goodearth_mcp.server # runs the validate_operator_tools guard
cd frontend && npm install && npm run buildApache-2.0
This server cannot be deployed
Weather, climate, terrain, fire and flood risk data for any point or polygon on Earth. Free tier.
Generate and run high performance queries on open and private spatial data at-scale in the cloud
Weather data, forecast API, climate data, historical weather, alerts, agricultural & travel weather.
Query 4,300+ ranked metros across sixteen dimensions: profiles, search, and head-to-head comparisons
