
Good Earth
io.github.lonnievPublished by GitHub account lonnievv0.6.0Updated Oct 29, 2026
Climate timing for gardens and small farms: frost, heat, soil and planting dates for your plot.
Overview
Remote MCP server giving an assistant climate and agronomic analytics for a grower's saved plot: frost, heat, soil, planting dates and pests.
- What you can do
- Save, list, transform and delete named plots (polygons or pins) and record what is grown or observed on them
- Compute season timing per plot: heat accumulation, frost windows, soil temperature, planting windows, crop suitability, almanac, drying and water balance, sunlight
- Look up pest and disease models, nearby species and wildlife calendars
- Check tree suitability and chill, and suggest companion plantings
- Plan the season, review a roster, calibrate the model from field reports, and manage a task list
- Build and publish dated calendar feeds for a plot
- When to use it
- Useful when helping gardeners or small farms decide planting dates, frost risk, crop choice or pest timing for a specific piece of ground rather than a single weather pin, and when the assistant should compare variation across a plot.
- Requirements
- A remote streamable HTTP endpoint; no local install. No account or API key is needed to connect, but paid tools require a Nostr npub proven by DM, plus credits topped up by paying a Bitcoin Lightning invoice. Network access to the endpoint is required.
Installation
In SourceWeft
- Open Good Earth in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.lonniev%2Fgoodearth-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"good-earth": {
"type": "http",
"url": "https://goodearth-mcp.fastmcp.app/mcp"
}
}
}README
Good Earth
Region-scoped climate analytics for small specialty-crop and flower farms, monetized with Tollbooth DPYC™ Bitcoin Lightning micropayments.
Sibling of the Good Brew store.
- For growers: the web app at https://goodearth.tollbooth-dpyc.com
- For AI agents: the MCP server at
https://goodearth-mcp.fastmcp.app/mcp(streamable HTTP) — the same tools the web app calls.
Connect an AI agent
Any MCP client that takes a remote server URL can connect; there is no account and no API key.
server.json at the repo root is the entry for the official
MCP Registry, as
io.github.lonniev/goodearth-mcp — the namespace the rest of the DPYC fleet
is listed under. .github/workflows/publish-mcp-registry.yml publishes it on
every v* tag, logging in with GitHub OIDC and taking the version from the
tag, so there is no key to keep. A test holds the committed version to
pyproject.toml.
First connection walkthrough
- Ask the grower for their Nostr npub — never their nsec.
goodearth_request_npub_proof(patron_npub=…)sends them a DM. They reply from their Nostr client; then callgoodearth_receive_npub_proof(patron_npub=…, nonce=…)once with the nonce the request returned. The connection then holds the npub: pass onlynpubon every paid call.goodearth_check_balance; top up withgoodearth_purchase_credits(a Lightning invoice the grower pays) andgoodearth_check_payment.goodearth_block_list— their saved ground, or a worked example to start from.
Free with no proof: goodearth_service_status and the goodearth_oracle_*
tools. goodearth_check_price previews a fare. The server's own
instructions repeat all of this for an agent that connects cold.
The idea
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. A grower saves a plot once as a block —
a GeoJSON polygon or a {lat, lon, radius_m} pin, with a name — using
goodearth_block_save. Every other tool then takes that block by its id,
its name, an alias, or any part of its name that only one block has. Each tool
samples the terrain inside the block 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.
Blocks may overlap or nest: a bed inside a field is its own block. What a
grower grows, watches for and has seen is recorded per block with
goodearth_block_item_save, so the season tools need no lists passed in.
How the spread is actually produced
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 2 km at best (archived high-resolution model runs) and 9 km for the ERA5 reanalysis. Two sample points on one farm can 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 30 m, and terrain is what varies within a farm.
So Good Earth reads the regional signal from the gridded feeds and derives within-region variation from elevation:
Every response carries the native resolution of each feed it used, so a grower is never sold precision the data does not contain.
Tools
Every tool below takes a saved block unless noted.
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.
Data sources
All public. Every one is free, and only the EIA feed needs a key: an optional
eia_api_key the operator delivers by Secure Courier, so the Sun page can
quote what a kWh sells for in the block's state.
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.
Onboarding roadmap
- 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(and, optionally,eia_api_key) viagoodearth_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.jsonis 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.
The SPA
frontend/ carries the Good Earth app (the taxsort-mcp pattern — one repo,
React app inside). Sign-in and the Nostr profile panel come from the fleet's
shared @tollbooth-dpyc/web package. There are no accounts: a grower is an
npub.
A grower's blocks, what is recorded on them, tasks and published calendar
feeds are stored in the operator's Neon database under their npub. A block's
name, aliases and boundary are encrypted with the SDK's vault cipher; the items
recorded on a block (crop names, species, field reports) are stored in the
clear so they can be sorted and searched. goodearth_forget_my_ground deletes
all of it; the grower's balance and purchase history stay with the patron.
Develop
License
Apache-2.0
Source: README.md at commit b37bf8a
Tools
0Version history
4- v0.6.0LatestOct 29, 2026
- v0.4.0Oct 21, 2026
- v0.3.0Sep 19, 2026
- v0.2.0Sep 16, 2026
Score
85% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- 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