
Good Earth
io.github.lonniev由 GitHub 账号 lonniev 发布v0.6.0更新于 Oct 29, 2026
Climate timing for gardens and small farms: frost, heat, soil and planting dates for your plot.
概览
远程 MCP 服务器,为种植者保存的地块提供气候与农艺分析:霜冻、积温、土壤、播期和病虫害。
- 可以做什么
- 保存、列出、变换和删除命名地块(多边形或坐标点),并记录种植与观察内容
- 按地块计算季节时序:积温、霜冻窗口、土壤温度、播种窗口、作物适宜性、农事历、干燥与水分平衡、日照
- 查询病虫害模型、周边物种记录和野生动物日历
- 评估树木适宜性与需冷量,并推荐伴生种植
- 规划整个季节、审核种植清单、用田间记录校准模型,并管理任务清单
- 为地块生成并发布带日期的日历订阅
- 适用场景
- 适合帮助园艺爱好者或小型农场针对某一块具体土地(而非单个天气坐标点)判断播期、霜冻风险、作物选择和病虫害时机,也适合需要比较地块内部差异的场景。
- 运行要求
- 远程 streamable HTTP 端点,无需本地安装。连接不需要账号或 API 密钥,但付费工具需要先通过私信验证 Nostr npub,并支付比特币闪电发票充值额度。需要能访问该端点的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Good Earth,将其添加到工作区。
- 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.lonniev%2Fgoodearth-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。
{
"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
来源:README.md,提交 b37bf8a
工具
0版本历史
4- v0.6.0最新Oct 29, 2026
- v0.4.0Oct 21, 2026
- v0.3.0Sep 19, 2026
- v0.2.0Sep 16, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分