MCP.Market

Good Earth MCP server

online · 100% uptime
by lonniev·io.github.lonniev/goodearth-mcp·v0.6.0

Climate timing for gardens and small farms: frost, heat, soil and planting dates for your plot.

B81/100grade B
What users say
No reviews yet
Be the first
Safety scan
B81/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Good Earth yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Good Earth tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Good Earth compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
81/100
higher than 62% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
420 ms
faster than 35% of 30,031 servers

Release history: 5 versions in the registry since 2026-09-14, latest 2026-10-28, typically one every 6 days.

Install Good Earth in Claude Code, Cursor or VS Code

claude mcp add --transport http goodearth-mcp https://goodearth-mcp.fastmcp.app/mcp
Add to Cursor

What the publisher says

From the Good Earth repository's README, as published. We do not edit it. Read it on GitHub

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.

(streamable HTTP) — the same tools the web app calls.

  • For growers: the web app at
  • For AI agents: the MCP server at https://goodearth-mcp.fastmcp.app/mcp

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

from their Nostr client; then call goodearthreceivenpubproof(patronnpub=…, dpoptoken=…) once, and pass npub + dpoptoken on every paid call.

  1. Ask the grower for their Nostr npub — never their nsec.
  2. goodearthrequestnpubproof(patronnpub=…) sends them a DM. They reply

Lightning invoice the grower pays) and goodearthcheckpayment.

  1. goodearthcheckbalance; top up with goodearthpurchasecredits (a
  1. goodearthblocklist — their saved ground, or a worked example to start from.

Free with no proof: goodearthservicestatus and the goodearthoracle tools. goodearthcheckprice 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. Every tool accepts a GeoJSON polygon or a {lat, lon, radiusm} 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.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Good Earth: common questions

Is Good Earth MCP server safe?
Mostly: it is graded B (81/100). Read the Good Earth safety report
How do I install Good Earth?
It runs remotely at goodearth-mcp.fastmcp.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Good Earth need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Good Earth maintained?
The last commit was 33 days ago (2026-10-02). The latest release is v0.6.0.
Is Good Earth up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Good Earth compare with other MCP servers?
safety score 81/100 (higher than 62% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 420 ms (faster than 35% of 30,031 servers). Full comparison.

More from lonniev →