# Good Earth (remote · goodearth-mcp.fastmcp.app)

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

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `goodearth-mcp.fastmcp.app`: 68/100 (this document), [markdown](https://verifymcp.io/servers/lonniev-goodearth-mcp/goodearth-mcp.md), [page](https://verifymcp.io/servers/lonniev-goodearth-mcp/goodearth-mcp)

## Channel facts

- Endpoint: `https://goodearth-mcp.fastmcp.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 81 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 18901 tokens (~233/item across 81 items; 81 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "goodearth_forget_credentials" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 82 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Good Earth MCP server?

Good Earth is a hosted endpoint at https://goodearth-mcp.fastmcp.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http lonniev-goodearth-mcp 'https://goodearth-mcp.fastmcp.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lonniev-goodearth-mcp": {
      "url": "https://goodearth-mcp.fastmcp.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lonniev-goodearth-mcp": {
      "type": "http",
      "url": "https://goodearth-mcp.fastmcp.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lonniev-goodearth-mcp]
url = "https://goodearth-mcp.fastmcp.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lonniev-goodearth-mcp": {
      "type": "remote",
      "url": "https://goodearth-mcp.fastmcp.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lonniev-goodearth-mcp --url 'https://goodearth-mcp.fastmcp.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lonniev-goodearth-mcp:
    url: "https://goodearth-mcp.fastmcp.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lonniev-goodearth-mcp": {
      "Transport": "http",
      "Url": "https://goodearth-mcp.fastmcp.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lonniev-goodearth-mcp -t streamable-http -u 'https://goodearth-mcp.fastmcp.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lonniev-goodearth-mcp": {
      "type": "http",
      "url": "https://goodearth-mcp.fastmcp.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-26 (score 68, +1)

- [functional] Server version: 4.0.9 → 4.0.10

### 2026-09-25 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 67, +1)

- [functional] Server version: 4.0.5 → 4.0.7

### 2026-09-22 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 64, 0)

- [functional] Server version: 4.0.4 → 4.0.5

### 2026-09-18 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 63, +1)

- [security] Tool “goodearth_block_item_save” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 4.0.3 → 4.0.4
- [cosmetic] “goodearth_block_item_list” reworded the description of “kind”
- [cosmetic] “goodearth_block_item_list” reworded the description of “season”
- [cosmetic] “goodearth_block_item_save” reworded the description of “items”
- [cosmetic] “goodearth_block_item_save” reworded the description of “kind”
- [cosmetic] “goodearth_block_item_save” reworded the description of “season”

## MCP tools (81)

### `goodearth_check_balance` (~210 tokens)

Goodearth Check Balance

Check a patron's credit balance at this operator.

This is the patron's spending balance — credits purchased via
Lightning for tool calls at this operator. For the operator's
own balance at the Authority (needed to certify patron purchases),
use authority_check_balance instead.

Free — no credits required. Proof of npub ownership is required
to prevent anyone-with-the-registry from enumerating balances.

Input parameters:

- `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL…
- `npub` (string, required): The Nostr public key (npub1...) whose balance to check.

### `goodearth_purchase_credits` (~200 tokens)

Goodearth Purchase Credits

Buy credits via Bitcoin Lightning.

Creates a Lightning invoice. Pay it with any Lightning wallet,
then call check_payment to confirm. Proof of npub ownership is
required so credits land in the correct ledger.

Free — no credits required to call.

Input parameters:

- `amount_sats` (integer): Satoshis to purchase (default 1000).
- `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL…
- `npub` (string, required): The Nostr public key (npub1...) the credits will fund.

### `goodearth_check_payment` (~196 tokens)

Goodearth Check Payment

Check the payment status of a Lightning invoice.

Call after paying the invoice from purchase_credits.
Free — no credits required. Proof of npub ownership is required
to prevent credit-grant front-running by an observer of the
invoice ID.

Input parameters:

- `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL…
- `invoice_id` (string, required): The invoice ID returned by purchase_credits.
- `npub` (string, required): The Nostr public key (npub1...) that purchased the invoice.

### `goodearth_restore_credits` (~235 tokens)

Goodearth Restore Credits

Credit a patron's ledger from a BTCPay-settled invoice.

\**RESTRICTED to the operator** — the operator owns the books and is
the only party who can issue a manual credit grant. Patrons who
believe they paid but never got credits must escalate to the
operator's support, who then invokes this tool on their behalf.

Use cases: cold-start vault races during check_payment, ncred
delivery hiccups, patrons closing Top-Off sheets before settle,
any infrastructure incident that left an invoice settled at BTCPay
but uncredited on the operator's ledger.

Idempotent — if the invoice is already credited (in the patron's
\``credited_invoices``), returns success with credits_granted=0.

Input parameters:

- `dpop_token` (string, required): A kind-27235 Nostr event signed by the OPERATOR's nsec for this tool. Patron proofs are rejected.
- `invoice_id` (string, required): The BTCPay invoice ID to verify and credit.
- `patron_npub` (string, required): The patron's npub whose ledger receives the grant.

### `goodearth_account_statement` (~224 tokens)

Goodearth Account Statement

Generate a patron's account statement at this operator.

Returns the patron's purchase history, active credit tranches,
per-tool usage breakdown, and recent daily usage logs. This is
the patron's spending account — not the operator's Authority
tax balance.

Free — no credits consumed. Proof of npub ownership is required
to prevent statement-scraping of arbitrary patrons.

Input parameters:

- `days` (integer): Number of days of daily usage history to include (default 30).
- `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL…
- `npub` (string, required): The patron's Nostr public key (npub1...).

### `goodearth_account_statement_infographic` (~224 tokens)

Goodearth Account Statement Infographic

Generate a visual SVG infographic of your account statement.

Returns the same data as account_statement, rendered as a dark-themed
SVG graphic with balance hero, metrics cards, health gauge, tranche
table, and tool usage breakdown. Costs 1 api_sat per call. Proof is
verified by ``debit_or_deny`` before any cost is incurred.

Input parameters:

- `days` (integer): Number of days of daily usage history to include (default 30).
- `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL…
- `npub` (string, required): The Nostr public key (npub1...) whose statement to render.

### `goodearth_report_issue` (~349 tokens)

Goodearth Report Issue

File a field report about this service as a GitHub issue on the operator's repo.

Found a tool's metadata or response wrong or confusing? Report it where the tool
lives. The **author of record is your npub** — no npub / no proof, no issue — and it
is stamped into the issue so the report is attributed to you, not the operator. Costs
a small fee (a free write to an issue tracker would be abused). The report is PUBLIC
and goes to the maintainers' normal triage; nothing is verified here.

Returns the filed issue's repo, number, and url. If this operator has not enabled
field reports, returns an "issue reporting not configured" situation and you are not
charged.

Input parameters:

- `body` (string, required): The details — which tool, what was wrong, what you expected.
- `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL…
- `npub` (string, required): Your Nostr public key (npub1...); the report's author of record.
- `title` (string, required): One-line summary of the problem.
- `tool_name` (string): Optional: the specific tool the report is about (e.g. "schwab_get_option_chain").

### `goodearth_service_status` (~22 tokens)

Goodearth Service Status

Check the health and configuration of this service. Free.

### `goodearth_get_operator_onboarding_status` (~58 tokens)

Goodearth Get Operator Onboarding Status

Report this operator's configuration readiness.

Shows which operator settings are configured, which are missing,
and how to deliver each missing value. For patron-level credential
status, use get_patron_onboarding_status instead. Free.

### `goodearth_get_patron_onboarding_status` (~139 tokens)

Goodearth Get Patron Onboarding Status

Report a patron's credential readiness for this operator.

For set-once services (eXcalibur, TheBrain), shows which patron
secrets are configured and which are missing. For dynamic/OAuth2
services (Schwab), reports that no patron credentials are needed.
Free. Proof of npub ownership is required because credential
presence is sensitive information about the patron's setup.

Input parameters:

- `dpop_token` (string, required): A kind-27235 Nostr event signed by patron_npub for this tool.
- `patron_npub` (string, required): The patron's Nostr public key (npub1...).

### `goodearth_session_status` (~287 tokens)

Goodearth Session Status

Check operator readiness. Returns the operator lifecycle
state and clear guidance on what to do next. Free.

Lifecycle states:
\- ready: Operator is warm and fully operational — vault AND pricing
  model verified. Proceed with tool calls.
\- warming_up: Operator is initializing (cold start). Try a tool call — it will warm up on demand.
\- misconfigured: Persistence rejected a query with a permanent SQL
  error (permission denied, missing relation). Paid tools will fail
  until the operator repairs the database — retrying does not help.
\- quota_exceeded: The persistence provider (Neon) answered HTTP 402 —
  the operator's database has exhausted its compute/storage quota, so
  the books are locked for billing. Paid tools fail; retrying does NOT
  help. The operator's Authority must restore capacity (upgrade the
  plan or wait for the quota reset). Free tools remain available.
\- not_registered: Operator has no Authority relationship yet. Call register_operator first.
\- no_identity: Operator nsec is not configured. Deployment issue.

Input parameters:

- `patron_npub` (string): Optional. If supplied, the response includes an ``upstream_oauth`` block with the patron's stored OAuth token expiry (runtime-derived from vault state) so a client can refresh proactively rather than…

### `goodearth_request_credential_channel` (~252 tokens)

Goodearth Request Credential Channel

Open a Secure Courier channel for credential delivery.

This is the CREDENTIAL-DELIVERY flow — use it to hand over a service
secret (API keys, tokens). To merely prove you control an npub (the
usual answer to a ``proof_required`` error), use ``request_npub_proof``
instead. Note: dynamic/OAuth2 services (e.g. Schwab) need NO couriered
secret — check ``service_status`` first.

Sends a welcome DM with a credential template. The recipient
must read the DM in their Nostr client, fill in the fields,
and reply manually. **This is a human-in-the-loop flow.**

After calling this tool, STOP and tell the user what to do.
Wait for the user to confirm they have replied before calling
\``receive_credentials``. Do NOT poll or retry — each
\``receive_credentials`` call destructively drains the relay
mailbox.

Input parameters:

- `sender_npub` (string): Required. The npub to send the template to.
- `service` (string): Required. The credential service name (e.g., from get_operator_onboarding_status or get_patron_onboarding_status).

### `goodearth_receive_credentials` (~324 tokens)

Goodearth Receive Credentials

Pick up credentials from the Secure Courier.

Completes the CREDENTIAL-DELIVERY flow (the ownership-proof
counterpart is ``receive_npub_proof``).

\**Call this only after the user confirms they have replied.**
Deterministic, one-shot retrieval: name the response you want with
\``(sender_npub, service, dpop_token)`` and the tool drains ONLY the
rendezvous relay that channel was pinned to. Every popped DM with the
wrong session phrase is deleted and its sender is NACK'd; the first DM
with the matching phrase is accepted (ACK'd) and the scan stops. If
none match, the queue is drained and a ``courier_not_found`` result is
returned. Do NOT poll, loop, or retry.

If a credential_card (ncred1...) is provided, it is redeemed directly
without any relay access (dpop_token not required for that path). On
success, the payment processor client is reinitialized from the new
credentials — no server restart needed.

Input parameters:

- `credential_card` (string): Optional. An ncred1... card to redeem directly (bypasses the relay drain; dpop_token not needed).
- `dpop_token` (string): Required. The session phrase returned by request_credential_channel for this exact channel.
- `sender_npub` (string): Required. The npub that sent the credentials.
- `service` (string): Required. The credential service name (must match the service used in request_credential_channel).

### `goodearth_forget_credentials` (~197 tokens)

Goodearth Forget Credentials

Delete vaulted credentials for a specific service and npub.

For operator credentials, pass the operator's own npub. For patron
credentials, pass the patron's npub. Always requires proof of
npub ownership — a deletion is as destructive as a write.

Input parameters:

- `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL…
- `npub` (string, required): The Nostr public key (npub1...) whose credentials to forget.
- `service` (string, required): The credential service to forget.

### `goodearth_update_patron_credential` (~219 tokens)

Goodearth Update Patron Credential

Add or update a single patron credential field.

Merges into existing stored credentials without affecting
other fields. Useful for setting an account identifier
after OAuth, changing a default brain, etc. Free. Proof of
npub ownership is required — this is a write to the patron's
sensitive credential vault.

Input parameters:

- `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL…
- `field` (string, required): The credential field name to set.
- `npub` (string, required): The patron's Nostr public key (npub1...).
- `value` (string, required): The value to store.

### `goodearth_update_operator_credential` (~183 tokens)

Goodearth Update Operator Credential

Add or update a single operator secret field.

Merges into the operator's stored credentials without touching the
others — the field-level counterpart to re-delivering the whole
bundle over Secure Courier. Use it to rotate one secret (a reissued
\``btcpay_api_key``, say) without restating the six you did not
change, where any field omitted from a courier reply is destroyed.

The value is never echoed back. RESTRICTED to the operator —
requires proof (nsec-signed kind-27235 or a cached dpop_token
phrase); patron proofs are rejected.

Input parameters:

- `dpop_token` (string, required): Operator proof for this tool.
- `field` (string, required): The operator credential field to set. Must be declared in the operator's credential template.
- `value` (string, required): The value to store.

### `goodearth_delete_patron_credential` (~186 tokens)

Goodearth Delete Patron Credential

Remove a single patron credential field.

Deletes one field from stored credentials without affecting
other fields. Free. Proof of npub ownership is required —
this is a write to the patron's sensitive credential vault.

Input parameters:

- `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL…
- `field` (string, required): The credential field name to remove.
- `npub` (string, required): The patron's Nostr public key (npub1...).

### `goodearth_delete_operator_credential` (~228 tokens)

Goodearth Delete Operator Credential

Remove a single operator secret field.

Deletes one key from the operator's encrypted credential blob without
touching the others — the field-level counterpart to
\``forget_credentials``, which wipes the whole row. Use it to retire a
leftover after an SDK cutover (a Prefect key after Modal, or a stored
but untemplated orphan like ``anthropic_api_key``) without taking the
operator down for a full re-delivery.

Stored-but-untemplated fields are first-class: the delete is keyed on
what is vaulted, not on what the current template declares. Idempotent
— already-absent fields report ``removed: false`` without rewriting
the vault. RESTRICTED to the operator — requires proof (nsec-signed
kind-27235 or a cached dpop_token phrase); patron proofs are rejected.
A deletion is as destructive as a write.

Input parameters:

- `dpop_token` (string, required): Operator proof for this tool.
- `field` (string, required): The operator credential field to remove (templated or not).

### `goodearth_get_patron_credential_fields` (~235 tokens)

Goodearth Get Patron Credential Fields

List stored patron credential field names (not values).

Returns the names of fields stored for a patron, plus each
field's ``delivered_at`` ISO-8601 timestamp when known (null
for secrets vaulted before timestamps were recorded). Values
are never exposed — use this to verify which fields are
configured and how old each one is. Free. Proof of npub
ownership is required: the list of configured fields is itself
sensitive (reveals which integrations a patron has set up).

Input parameters:

- `dpop_token` (string, required): Raw JSON of a kind-27235 Nostr event signed by npub — not base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its `u` tag must hold THIS tool's exact name (from tools/list), not the endpoint URL…
- `npub` (string, required): The patron's Nostr public key (npub1...).

### `goodearth_request_npub_proof` (~489 tokens)

Goodearth Request Npub Proof

Request npub ownership proof from a patron via Nostr DM.

This is the npub-OWNERSHIP-PROOF flow — use it when a call returns
\``proof_required``. It proves the caller controls an npub; it does
NOT deliver any service secret. To hand an operator its API keys or
OAuth secrets, use ``request_credential_channel`` instead.

Sends a challenge DM that the patron must sign and reply to
using their Nostr client. **This is a human-in-the-loop flow.**

After calling this tool, STOP and tell the user to check their
Nostr client and reply to the challenge. Wait for the user to
confirm they have replied before calling ``receive_npub_proof``.
Do NOT poll or retry — each ``receive_npub_proof`` call
destructively drains the relay mailbox.

\**Returns** a ``dpop_token`` — the demonstrated-proof-of-possession
token that the calling application MUST remember and pass as the
\``dpop_token`` parameter on every subsequent paid tool call. The MCP
does not retain this value across restarts.

\**Lifecycle:** The cached proof expires after the patron's
chosen duration. When it expires, call ``request_npub_proof``
again for a fresh challenge, then wait for the user, then
call ``receive_npub_proof``.

Free.

Input parameters:

- `patron_npub` (string): Required. The patron's npub to request proof from.
- `reason` (string): Optional. A human-readable purpose for the request ("I'm working on your request XYZ and need the Operator to do ABC for you"). Signed into the provenance attestation and shown in the DM, so the reci…
- `verify_at` (string): Optional. A free-form statement of WHERE you (the initiating agent) already showed this proof's one-time code to the user — a URL, or "your Claude.ai conversation", "the Grok session". The OAuth 2.0…

### `goodearth_receive_npub_proof` (~311 tokens)

Goodearth Receive Npub Proof

Receive npub ownership confirmation from a patron.

Completes the npub-OWNERSHIP-PROOF flow (the credential-delivery
counterpart is ``receive_credentials``).

\**Call this only after the user confirms they have replied.**
Deterministic, one-shot retrieval: name the response with
\``(patron_npub, dpop_token)`` — the ``dpop_token`` being the value
returned by ``request_npub_proof``. The tool drains ONLY the pinned
rendezvous relay that challenge was published on, stopping at the DM
whose phrase matches. Mismatched DMs are deleted and NACK'd (without
revealing the expected phrase). If called before the user replies,
their message will never be found. Do NOT poll, loop, or retry.

The signed DM itself proves npub ownership (the patron's nsec
signed it). On success, returns the ``dpop_token`` — the same
token. The calling application MUST remember it and pass it as the
\``dpop_token`` parameter on every subsequent paid tool call. The
proof (a hash of the token) is stored in the vault keyed by that
hash — the MCP never stores the raw token itself. Free.

Input parameters:

- `dpop_token` (string): Required. The dpop_token returned by request_npub_proof.
- `patron_npub` (string): Required. The patron's npub to receive proof from.

### `goodearth_check_proof_status` (~139 tokens)

Goodearth Check Proof Status

Check whether a previously-cached dpop_token is still valid.

Mirrors ``check_oauth_status`` for the npub-proof flow: a calling
agent can ask "will my next paid call accept this dpop_token?"
before burning credits on a guaranteed failure.

Free, no side effects — does not evict the cache or touch relays.

Input parameters:

- `dpop_token` (string): Required. The dpop_token phrase returned by ``request_npub_proof`` / ``receive_npub_proof``.
- `patron_npub` (string): Required. The patron's npub (npub1...).

### `goodearth_oracle_how_to_join` (~26 tokens)

Goodearth Oracle How To Join

Get DPYC onboarding instructions from the Oracle. Free.

### `goodearth_oracle_get_tax_rate` (~25 tokens)

Goodearth Oracle Get Tax Rate

Get the current DPYC certification tax rate. Free.

### `goodearth_oracle_lookup_member` (~34 tokens)

Goodearth Oracle Lookup Member

Look up a DPYC community member by npub. Free.

Input parameters:

- `npub` (string, required)

### `goodearth_oracle_about` (~23 tokens)

Goodearth Oracle About

Describe the DPYC ecosystem via the Oracle. Free.

### `goodearth_oracle_network_advisory` (~26 tokens)

Goodearth Oracle Network Advisory

Get active network advisories from the Oracle. Free.

### `goodearth_check_authority_balance` (~74 tokens)

Goodearth Check Authority Balance

Check this operator's tax balance at the Authority.

Returns the sats available for certifying patron credit purchases.
When this balance reaches zero, patron top-ups cannot be certified
and the operator must call purchase_credits on the Authority.

This is the operator's own funding — not a patron balance. Free.

### `goodearth_get_pricing_model` (~52 tokens)

Goodearth Get Pricing Model

Get the active pricing model for this operator. Free.

If no model exists, self-initializes a scaffold with all
registered tools at 0 sats.  No economic data from code.

### `goodearth_set_pricing_model` (~69 tokens)

Goodearth Set Pricing Model

Set the active pricing model. RESTRICTED to operator.

Requires a valid proof (Schnorr-signed kind-27235 event)
proving the caller holds the operator's nsec.

Input parameters:

- `dpop_token` (string)
- `model_json` (string, required)

### `goodearth_reset_pricing_model` (~82 tokens)

Goodearth Reset Pricing Model

Erase all pricing models and restore a viable default.

Deletes every stored model, then self-initializes a fresh one
from the tool registry — all tools at 0 sats with proper UUIDs.
Returns the new model.

RESTRICTED to operator — requires proof (nsec-signed).

Input parameters:

- `dpop_token` (string)

### `goodearth_request_adoption` (~194 tokens)

Goodearth Request Adoption

Ask a chosen Authority to adopt this operator (deferred courtship).

RESTRICTED to the operator — requires proof the caller controls this
operator's npub. Resolves the Authority's MCP endpoint from the
community registry, mints an inline ownership proof with this
operator's nsec, and delivers the request MCP-to-MCP. The Authority
records it as pending; its owner approves on their own time. Poll
\``adoption_status`` for progress; the operator flips to ``ready``
once the Authority provisions it.

Input parameters:

- `authority_npub` (string, required): npub of the Authority to request adoption from.
- `dpop_token` (string): operator-npub ownership proof (inline kind-27235 or cached token).
- `note` (string): optional message for the Authority owner.
- `service_url` (string): this operator's MCP endpoint (advertised to the Authority).

### `goodearth_adoption_status` (~71 tokens)

Goodearth Adoption Status

Check this operator's adoption-request status at a chosen Authority.

Free. Polls the Authority MCP-to-MCP for the status of this operator's
request (pending / approved / rejected / provisioned).

Input parameters:

- `authority_npub` (string, required)
- `dpop_token` (string)

### `goodearth_restore_neon_schema` (~149 tokens)

Goodearth Restore Neon Schema

Re-run ``ensure_schema()`` on every NeonVault this operator uses.

Diagnostic / recovery tool for the case where the Neon HTTP SQL API
is returning persistent 4xx errors and the operator suspects the
schema isn't there or grants are wrong. Idempotent — uses
\``CREATE TABLE IF NOT EXISTS`` so a successful re-run is harmless.

Returns the per-step result. If any step raises, surfaces the Neon
error message inline (0.31.0 reads the SQL error body that earlier
wheels swallowed behind ``raise_for_status``).

RESTRICTED to operator — requires proof (nsec-signed).

Input parameters:

- `dpop_token` (string)

### `goodearth_list_canonical_identities` (~251 tokens)

Goodearth List Canonical Identities

Return canonical (tool_id, mcp_name, …) for every tool the wheel exposes.

The authoritative source for any client (Studio, agents, FE)
that needs to know how this MCP identifies its tools.
Reconcile uses this output to UUID-join against the stored
pricing model — no name-based UUID derivation, no guessing.

Includes both ToolIdentity-seeded tools and any UUID recorded by
\``@paid_tool`` that is missing from the registry. The latter appear
with ``registered: false`` (and in the top-level ``unregistered``
array) so Reconcile can flag deploy drift instead of silently
reporting clean when a live tool was never seeded (#174).

If the operator renames a function or rebrands a slug, the
mcp_name in this output changes but tool_id stays. That's the
whole point of the canonical-UUID design.

Also diffs the live FastMCP wire surface against the registry.
Tools exposed on the wire but absent from the registry appear in
\``unregistered`` so Reconcile can flag deploy drift instead of
silently under-reporting (issue #175).

Free, no side effects.

### `goodearth_get_nostr_profile` (~89 tokens)

Goodearth Get Nostr Profile

Read an npub's public Nostr profile (NIP-01 kind-0 metadata).

Free, no proof — the data is already public on relays. Returns the
latest metadata fields (name, display_name, about, picture, banner,
nip05, website, lud16) or an empty profile if none is published.

Input parameters:

- `npub` (string)

### `goodearth_publish_nostr_profile` (~151 tokens)

Goodearth Publish Nostr Profile

Publish a CLIENT-SIGNED kind-0 profile to relays for an npub.

The wheel never holds a patron nsec. The frontend signs the kind-0
metadata event with the patron's session key or a NIP-07 extension and
passes the signed event (JSON) here; the wheel verifies the signature
matches the npub, then relays it to public relays. The signature is the
authorization — no proof token, no key custody. Free.

Input parameters:

- `npub` (string): The patron's Nostr public key the event must be signed by.
- `signed_event` (string): A JSON-encoded, client-signed kind-0 event.

### `goodearth_check_price` (~181 tokens)

Goodearth Check Price

Preview the effective cost of a tool call.

Shows the base cost and any constraint effects (discounts, free
trials, surge pricing). Free — no credits required.

Input parameters:

- `dpop_token` (string)
- `npub` (string)
- `tool_id` (string, required): Either the tool's UUID (from the pricing model) or a bare capability string (e.g. ``"deal_scenario"``). FE callers usually have the capability name; this resolves both so the FE doesn't need to deriv…
- `tool_kwargs` (string): Optional JSON object with tool call parameters for ad valorem / categorical-multiplier pricing preview (e.g. '{"amount_sats": 5000}' or '{"difficulty": "sovereign", "mode": "live"}').

### `goodearth_list_constraint_types` (~52 tokens)

Goodearth List Constraint Types

List all available constraint types and their parameter schemas.

Returns the type, category, description, and parameter specs for
every constraint that can be used in a pricing pipeline.
Free — no credits required.

### `goodearth_mint_coupon` (~153 tokens)

Goodearth Mint Coupon

Create a new operator-owned discount coupon.

Input parameters:

- `discount_percent` (number, required): Percentage off the base price (0-100).
- `dpop_token` (string)
- `name` (string, required): The catchy code patrons type to redeem (operator-scoped uniqueness).
- `total_uses`: Aggregate cap across all patrons (default None = unlimited).
- `uses_per_patron`: How many tool calls one patron can claim the discount on (default 1; pass null/None for unlimited within the window).
- `valid_from` (string, required): ISO-8601 datetime when the coupon becomes active.
- `valid_until` (string, required): ISO-8601 datetime when the coupon expires.

### `goodearth_list_coupons` (~72 tokens)

Goodearth List Coupons

List every coupon this operator has minted (newest first).

Each row carries the current ``times_redeemed`` counter — the
Studio renders a progress bar from this against ``total_uses``.
RESTRICTED to operator — requires proof.

Input parameters:

- `dpop_token` (string)

### `goodearth_update_coupon` (~168 tokens)

Goodearth Update Coupon

Patch a coupon's editable fields.

Pass only the fields you want to change.  To set a cap to
unlimited (NULL in the schema), pass ``clear_uses_per_patron=true``
or ``clear_total_uses=true``.  Renaming the code is allowed —
existing patron redemption rows survive (they key on coupon id).

RESTRICTED to operator — requires proof.

Input parameters:

- `clear_total_uses` (boolean)
- `clear_uses_per_patron` (boolean)
- `coupon_id` (string, required)
- `discount_percent`
- `dpop_token` (string)
- `name`
- `total_uses`
- `uses_per_patron`
- `valid_from`
- `valid_until`

### `goodearth_delete_coupon` (~83 tokens)

Goodearth Delete Coupon

Delete a coupon.  Cascades to all patron redemptions.

Any chain step referencing the deleted coupon_id becomes a
no-op (the constraint returns neutral on unknown ids) — the
Studio surfaces orphan references as warnings.

RESTRICTED to operator — requires proof.

Input parameters:

- `coupon_id` (string, required)
- `dpop_token` (string)

### `goodearth_redeem_coupon` (~135 tokens)

Goodearth Redeem Coupon

Claim a coupon by its name (the code the operator shared).

Looks up the operator's coupon by ``code``, validates the window
and total cap, and records a per-patron redemption row.
Subsequent paid tool calls on this MCP auto-apply the discount
until ``uses_per_patron`` is exhausted.

Free — no credits required.  Requires proof of ``npub``.
Idempotent: redeeming the same code twice returns the existing
redemption.

Input parameters:

- `code` (string, required)
- `dpop_token` (string)
- `npub` (string, required)

### `goodearth_list_my_coupons` (~90 tokens)

Goodearth List My Coupons

List the coupons this patron has redeemed on this operator.

Returns both active and exhausted redemptions with a per-row
\``status`` (``active`` / ``window_closed`` / ``patron_limit`` /
\``total_limit``).  Free — requires proof of ``npub``.

Input parameters:

- `dpop_token` (string)
- `npub` (string, required)

### `goodearth_forget_coupon` (~89 tokens)

Goodearth Forget Coupon

Remove a coupon from this patron's redemption list.

Cosmetic only — the coupon itself still exists at the operator,
and the patron can re-redeem the same code later while the
window allows.  Free — requires proof of ``npub``.

Input parameters:

- `coupon_id` (string, required)
- `dpop_token` (string)
- `npub` (string, required)

### `goodearth_notarize_ledger` (~55 tokens)

Goodearth Notarize Ledger

Build a Merkle tree of all patron balances and submit the root
to Bitcoin via OpenTimestamps.

Operator-only background task. Bitcoin confirmation takes 1-6 hours.
Free — no credits required.

### `goodearth_get_notarization_proof` (~71 tokens)

Goodearth Get Notarization Proof

Generate a Merkle inclusion proof that a patron's balance was
included in a Bitcoin-notarized snapshot.

Input parameters:

- `notarization_id` (string, required): The notarization record ID.
- `npub` (string, required): The patron's Nostr public key (npub1...).

### `goodearth_list_notarizations` (~53 tokens)

Goodearth List Notarizations

List recent Bitcoin notarization records.

Input parameters:

- `limit` (integer): Maximum records to return (default 20).
- `status` (string): Optional filter (e.g., 'submitted', 'confirmed').

### `goodearth_gdd_season_curve` (~272 tokens)

Goodearth Gdd Season Curve

Growing degree day accumulation across a region, season to date.

Returns accumulation with its spread across your ground, the band of the
last ten seasons to read it against, a 7-day forecast extension, and a
projection at the recent rate.

The spread is the answer's point: it says how much the same field varies
from bench to hollow, which is what decides whether one planting date
serves the whole block.

Input parameters:

- `base_temp` (number): Crop base temperature in °F — the threshold below which the crop does not accumulate heat. 50 °F is the field-corn convention; cool-season crops use 32-40 °F.
- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.

### `goodearth_frost_window` (~247 tokens)

Goodearth Frost Window

When frost normally arrives on this ground, and whether it is coming this week.

Returns first-frost dates from the last ten seasons, how far the region's
own terrain spreads that, and a night-by-night assessment of the coming
forecast for the *coldest* ground rather than the average.

The spread is the answer's point. Frost forms on still, clear nights when
cold air drains off high ground and pools in low, so a single forecast low
is optimistic for a hollow and pessimistic for a bench on the same block.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.

### `goodearth_crop_gdd_status` (~318 tokens)

Goodearth Crop Gdd Status

Where every planting on a block stands, and whether it finishes before frost.

Returns, per planting: heat accumulated since set-out against its target,
the projected date it reaches that target at the season's recent rate, and
a verdict on whether that lands before the median first frost.

One call answers the whole block. The season curve and the frost record are
shared across plantings, so asking about eight beds costs one round trip
rather than eight.

Input parameters:

- `base_temp` (number): Default base temperature in °F for plantings that do not set their own.
- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `plantings` (array, required): The block's plantings. Each is {"crop": "Lisianthus", "gdd_target": 1050, "set_out": "2026-07-06"} with an optional "base_temp" in °F when the crop counts from something other than the block default.

### `goodearth_soil_temp_projection` (~320 tokens)

Goodearth Soil Temp Projection

When the soil on this ground crosses a planting threshold.

Returns the near-term forecast at planting depth, the date it crosses
within that horizon if it does, and when the crossing normally happens
here — so a grower knows both "plant this week?" and "how long have I got?".

Soil lags air by weeks and is the steadier signal. It is what decides
whether a clove or a seed should go in, not one warm afternoon.

Input parameters:

- `band` (string): 'planting' for 7-28 cm (~3-11 in, the default) or 'shallow' for 0-7 cm.
- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `direction` (string): 'cooling' for an autumn window, 'warming' for a spring one.
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `threshold` (number): The soil temperature in °F that opens or closes the window. Garlic goes in below about 60.

### `goodearth_pest_threshold` (~433 tokens)

Goodearth Pest Threshold

Where a pest model's degree-day stages stand on this ground.

Returns, per model: heat accumulated since its biofix, which stages have
been crossed, and the projected date of the next one — plus a short list of
which pests to go and look for this week.

Good Earth computes when your models arrive on your ground. It does not
publish entomology: the thresholds are yours, because the authoritative
numbers belong to your extension service and vary by region and biotype.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `pests` (array, required): The pests to evaluate, in any of three shapes. 1. Your own thresholds, from an extension bulletin: {"pest": "Aster leafhopper", "base_temp": 50, "biofix": "2026-05-01", "stages": [{"stage": "second f…

### `goodearth_calibration` (~467 tokens)

Goodearth Calibration

Turn a block's own field reports into a correction on the model.

Every other tool here answers from a 9 km grid refined by a physical
terrain model. What that cannot know is the part that makes a farm
particular — the hedgerow, the pond, the outlet the cold air drains
through. Your observations measure exactly that gap.

Returns two corrections, kept separate because they fix different things:
a bias in *heat* from crop stages (this ground accumulates more or less
than the grid credits) and a bias in *days* from observed frost (this
ground frosts earlier or later than the region).

Nothing is applied silently. A correction appears only once several
observations agree, implausible values are set aside rather than averaged
in, and the reports behind every figure come back with it.

Input parameters:

- `base_temp` (number): Base temperature in °F the stage targets are counted at.
- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `observations`: Optional. Omit and this reads the field reports already recorded for the block. Pass a list to calibrate against those instead, without recording them: a frost report is {"kind": "frost", "observed_o…
- `season`: Which season's reports to calibrate against. Defaults to this one.

### `goodearth_almanac` (~284 tokens)

Goodearth Almanac

The sky's own record for this ground — normal, actual, and what is coming.

Degree days say what the season is doing to the plants. This says what the
season is doing: temperature, dew point, rain, wind, sunshine and day
length, each against what is normal here, what has actually happened, and
the fortnight ahead. Plus the sun and moon, which are astronomy and so are
computed exactly rather than forecast.

Growers read these together with the heat. A week of high dew points is
disease weather whatever the degree-day total says, and a dry August is an
irrigation decision that heat accumulation cannot make for you.

One call covers every measure — three upstream requests regardless.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.

### `goodearth_plan_the_season` (~168 tokens)

Goodearth Plan The Season

The season-planning interview, as a workflow to follow.

The same text the `plan_the_season` MCP prompt carries. It exists twice
because prompt support is uneven: a client that surfaces prompts offers
this as a command, and one that does not can still reach it by calling a
tool. Both read one constant, so they cannot drift into two different
interviews.

Follow the returned steps in order, asking one question at a time. The
ordering is the point — it moves from the grower's decision to its
consequences rather than from the available data to a report.

Input parameters:

- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.

### `goodearth_review_roster` (~525 tokens)

Goodearth Review Roster

Audit a roster against what this ground's record actually knows.

Asked "are these the right pests to watch?", an agent will answer from its
own training data — unverifiable, different per model, and confidently
wrong exactly at the margins where a review matters. This answers from the
record instead: the degree-day models USA-NPN publishes for these
coordinates, and what iNaturalist has recorded nearby.

Three findings:

\- **out_of_range** — listed, and this ground's record does not know it.
\- **absent** — the record knows it well and the roster does not list it.
\- **implausible** — an observation that cannot be right, with what makes it
  wrong. This is the one that matters: observations feed
  \``goodearth_calibration``, which shifts the heat and frost bias for the
  whole block, so a junk entry degrades every later answer rather than
  merely showing a wrong row.

\**Every reason is about the RECORD, never about the animal.** "Not recorded
within 16 km" is a fact; "does not live here" is natural history, which
Good Earth does not publish. Nothing is removed — the grower who genuinely
saw the odd thing is precisely the case worth learning from, so findings are
proposed and the patron decides.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `observations`: Field reports to sanity-check: [{"kind": "frost", "observed_on": "2026-07-04"}, {"kind": "pest", "species": "Walrus", "observed_on": "2026-06-03"}].
- `pests`: The pests being watched: [{"pest": "Codling moth"}, ...].
- `season`: Which season's roster to audit. Defaults to this one.
- `wildlife`: The creatures being tracked: [{"species": "American robin"}, ...].

### `goodearth_task_save` (~208 tokens)

Goodearth Task Save

Create or update one task.

Single-day by design: one date and optional clock times on it. No
recurrence and no multi-day spans — a farm list is a list of days.

Input parameters:

- `done` (boolean)
- `dpop_token` (string)
- `due` (string): YYYY-MM-DD. The day it is for.
- `ends_at` (string): Optional HH:MM on the due date.
- `note` (string): Optional detail.
- `npub` (string): Required. Your Nostr public key (npub1...).
- `region_id` (string, required): The saved region this task belongs to.
- `reminder_only` (boolean): True publishes a reminder; false publishes an entry that takes the slot.
- `starts_at` (string): Optional HH:MM on the due date.
- `task_id` (string): Omit to create; pass an existing id to update.
- `title` (string, required): What needs doing.

### `goodearth_task_list` (~269 tokens)

Goodearth Task List

One page of a region's tasks, ordered and filtered by the database.

The sorting, the timeframe filter and the search all happen in SQL, so a
long list costs one page rather than the whole table.

\``sort_col`` names a column rather than supplying one: it indexes a fixed
map and falls back to the due date, so an unrecognised value gives the
default order rather than an error — and can never reach the query.

Input parameters:

- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...).
- `page` (integer): Zero-based page number.
- `page_size` (integer): Rows per page, capped at 200.
- `region_id` (string, required): The saved region whose tasks to list.
- `search` (string): Optional POSIX regular expression, matched against title and note.
- `season_start` (string): Optional YYYY-MM-DD, so 'season' means the grower's season.
- `sort_col` (string): due, title, done, starts, created or updated.
- `sort_dir` (string): asc or desc.
- `timeframe` (string): day, week, month, season or all. 'season' means this farm's season.

### `goodearth_task_delete` (~85 tokens)

Goodearth Task Delete

Remove one task.

Scoped to the caller's npub in the WHERE clause, so a known id is not on
its own enough to delete somebody else's task.

Input parameters:

- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...).
- `task_id` (string, required): The task's id.

### `goodearth_task_set_done` (~75 tokens)

Goodearth Task Set Done

Mark one task done, or put it back.

Input parameters:

- `done` (boolean): True to tick it off.
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...).
- `task_id` (string, required): The task's id.

### `goodearth_pest_catalog` (~289 tokens)

Goodearth Pest Catalog

Which pest stages are modelled for this ground this season.

Read from the USA-NPN degree-day forecasts rather than from a list in
this service, so a model they publish next season appears here without
anyone editing anything, and a Georgia orchard gets Georgia's dates.

Only layers measured to encode a day of year become dated events. Some
carry accumulated heat instead, and one of those reads 281 in Vermont —
a convincing 8 October that is really a heat sum. Those are counted and
named as unreadable rather than rendered as dates.

The insects recorded nearby come from iNaturalist and are a landscape
fact: one field holds almost no observations, so the search is widened
to the surrounding country and the answer says how far.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.

### `goodearth_nearby_species` (~514 tokens)

Goodearth Nearby Species

Search what is actually recorded near this ground, a page at a time.

This replaces asking for a whole catalogue. There are more than three
thousand insect and spider species recorded around one Vermont block; the
old answer showed forty of them and said nothing about the rest, and
fetching all of them costs eleven round trips to build a list nobody
reads. So: search, twenty to a page, and the true total on every page.

\**Species are a landscape fact, not a field one.** A nine-hectare hayfield
contains almost no observations, so the search widens to the surrounding
country and the answer says how wide it looked. Every other tool here
answers about the drawn ground and nothing outside it; this one cannot.

\**The count measures observers as much as organisms.** A roadside is
better recorded than a back hayfield, so a high count is evidence somebody
was standing there — not that a thing is common on your ground.

No judgement of any kind. iNaturalist does not say which of these is a
pest, a weed, or worth planting, and sorting them into those would be
adding a claim the feed never made.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `kingdom` (string, required): What to look for: 'plants', 'insects' (which includes spiders), 'wildlife' (birds, mammals, amphibians, reptiles) or 'fungi'.
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `page` (integer): Which page. 20 to a page.
- `q` (string): Narrow by name — 'bumble', 'maple', 'Bombus'. Empty returns the most-observed first.
- `with_lifecycle` (boolean): Only the ones USA-NPN publishes a life cycle for. The count then counts those, not everything recorded here — thirty-nine of 2,416 insects around one block have one.

### `goodearth_wildlife_catalog` (~666 tokens)

Goodearth Wildlife Catalog

Which animals are actually recorded around this ground.

Birds, mammals, amphibians and reptiles observed near here, ranked by how
often each has been seen — so the answer for a Vermont lakeshore is not
the answer for a Georgia orchard, and neither is a roster someone typed.

Species are a landscape fact. A nine-hectare field contains almost no
observations of anything, so the search widens to the surrounding country
and the response reports how wide it looked; treating that footprint as
the farm would be the dishonest version.

The ranking measures observers as much as animals — a roadside is better
recorded than a back field — so the counts travel with the answer.

Pass a scientific name as `species` and this answers with that animal's
life-cycle phenophases instead — nest building, nestlings, fledged young,
calls or song, emergence above ground. Those come from USA-NPN, which
publishes them; they are not written into this service. Roughly half the
species recorded around a farm have them, and one that does not returns an
empty list rather than a guess, because "not tracked" and "does nothing"
are different claims.

Set `with_events` to get those phenophases for EVERY species in the list at
once, as `habit_events`. Ask for it before writing a roster: an agent left
to name events from memory writes "rut onset" and "southbound flights",
words this service has never used, where NPN says "Nest building" and
"Fledged young". It costs one upstream call per species, which is why it
is off by default.

\**The event name is not load-bearing.** A wildlife row is dated by its
DRIVER — heat, daylight, an interval, a calendar date — and the label is
the grower's own words. `habit_events` is a courtesy to a caller looking
for the right word, never a list of the only acceptable ones: "Big Night
crossing" is a real thing a salamander does and no catalogue holds it.

Good Earth times an event you set. It does not publish natural history.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `species` (string): Optional. A scientific name from a previous catalogue answer, e.g. 'Strix varia'. Given one, this returns that animal's life-cycle phenophases instead of the regional list.
- `with_events` (boolean): Include each species' known phenophases as `habit_events`, so a roster can be written from the published vocabulary rather than from memory. Costs one upstream call per species.

### `goodearth_wildlife_calendar` (~428 tokens)

Goodearth Wildlife Calendar

When the other creatures working your season arrive.

A farm is not only its crops. Robins arrive, woodchucks wake, squirrels
start caching. The same drivers that time a crop time the animals — heat
accumulation, day length, and the calendar the sun keeps — so they can be
computed for your ground rather than read off a regional average.

Three clocks, because animals do not all run on one: a degree-day
threshold, a photoperiod threshold (migration runs on this, which is why it
barely moves between a warm year and a cold one), or a date from your own
record.

The thresholds are yours. Good Earth works out when they arrive here; it
does not publish natural history.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `events` (array, required): The events to time, with your own thresholds. Heat-driven: {"species": "Woodchuck", "event": "emergence", "driver": "heat", "gdd": 120, "base_temp": 43}. Daylight-driven: {"species": "Robin", "event"…
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.

### `goodearth_crop_suitability` (~357 tokens)

Goodearth Crop Suitability

Which crops finish on this ground, and with how much room to spare.

"What can I grow?" is not a lookup. Two farms in the same county, one on a
bench and one in a hollow, have different answers — so this measures the
block's own frost-free window and the heat it accumulates inside it, then
judges each crop's requirement against that.

The answer that matters is not yes or no but MARGIN: how much season is
left after the crop is done, in the days a grower plans in. A crop that
finishes on the last warm day of an average year fails in half of them.

Requirements are yours. Published degree-day figures vary by cultivar and
maturity group; Good Earth computes against your ground rather than
publishing agronomy.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `crops` (array, required): The crops to judge, with your own requirements. Each is {"crop": "Field corn", "gdd_target": 2600, "base_temp": 50} with optional "frost_hardy", "category" and "emoji".
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.

### `goodearth_tree_suitability` (~495 tokens)

Goodearth Tree Suitability

Whether a tree survives and gets its chill on this ground.

A tree is not asked "does it finish before frost" — that is a question only
something that must finish in one season can be asked. It is asked two
others, both settled before it goes in the ground:

\* **Will it survive?** Every winter on record has a coldest night; a
  cultivar has a limit. The answer is how often the first went below the
  second.
\* **Will it fruit?** A deciduous fruit tree needs chill hours to break
  dormancy cleanly. The answer is how many winters on record delivered them.

Both come back as a FREQUENCY across the record rather than a yes. A tree
that survives nine winters in ten is a different proposition from one that
survives five, and any single word hides the difference.

Chill is counted as hours in the 32-45 °F band between 1 November and
15 February — the window the published chill-hour figures were derived
against. A wider window would bank more hours against a requirement
calibrated to a narrower one and report a tree comfortable where it is not.

The requirements are yours. Hardiness limits and chill hours are cultivar
figures that vary widely within a species; Good Earth computes what this
ground delivered against them and does not publish agronomy.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `trees` (array, required): The trees to judge, with the figures from their nursery tags. Each is {"tree": "Honeycrisp apple", "chill_hours": 800, "hardy_to_f": -30} with optional "category" and "emoji". Both figures are option…

### `goodearth_tree_year` (~362 tokens)

Goodearth Tree Year

When spring reached this ground, and what the sap did.

\**First leaf and first bloom**, from USA-NPN's Spring Index, dated for this
block and set against its own thirty-year normal. "Spring is early this
year" is a headline; "leaf-out reached this block seven days before its
normal" is something to act on.

First bloom is also when the pollen starts. That is a restatement of what
bloom is, not a pollen forecast — Good Earth has no pollen feed, models
none, and says nothing about what anyone should do about it.

\**The sap run**, for a block with maple, birch or walnut on it. Sap moves
on freeze and thaw rather than on warmth: a night below freezing followed
by a day above it. Counted off this ground's own season record, so it
costs no extra call. A block with nothing tappable gets no sap section —
the count would be just as true there and would answer a question nobody
on that ground asked.

The trees are read from the block's own record; nothing needs passing.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.

### `goodearth_calendar_dataset` (~427 tokens)

Goodearth Calendar Dataset

Compute this block's dated season as a dataset, and store it for publishing.

Every dated thing this block knows about: crop targets, pest stages,
wildlife and husbandry dates, the frost record, and your tasks. Returned as
structured rows — a calendar is one rendering of them, and a caller wanting
a table or a notification wants the same data.

An iCalendar rendering is stored alongside under a feed token, which the
Good Earth site serves at a subscribable URL. Point any iCal or Google
Calendar client at it and the season appears next to the school run and the
market stall, which is where a grower will actually see it.

This is the computed act: it reads the weather feeds and rebuilds
everything. Pass the same token again to recompute in place — subscribers
keep their subscription and the events update rather than duplicating.

Nothing is passed in but the block: what it grows, what it watches for and
what is due are read from the record. That is what makes a refresh safe —
while those collections travelled as arguments, nobody could recompute an
existing feed without knowing what had been handed to it the first time,
so a refresh silently published a smaller season than the one it replaced.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `season`: Which season to publish. Defaults to this one.
- `token` (string): Pass an existing feed's token to REFRESH it in place; omit to create one.

### `goodearth_calendar_fetch` (~136 tokens)

Goodearth Calendar Fetch

Read a stored calendar dataset by its feed token.

This exists for the Good Earth site, which serves the subscribable URL: a
calendar client speaks HTTP and knows nothing about MCP, JSON-RPC or npub
proofs, so the site fetches through here and renders the response as
text/calendar.

The unguessable token is the credential — there is nowhere in an iCalendar
subscription to put a proof. Serving is a separate act from computing, and
every read is counted so the operator can see how hard a feed is worked.

Input parameters:

- `token` (string, required): The feed token from calendar_dataset.

### `goodearth_calendar_list` (~50 tokens)

Goodearth Calendar List

The calendar feeds you have published, and how often each is polled.

Input parameters:

- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key.

### `goodearth_calendar_revoke` (~61 tokens)

Goodearth Calendar Revoke

Stop publishing a feed. Subscribers stop receiving updates. Free.

Input parameters:

- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key.
- `token` (string, required): The feed token to stop publishing.

### `goodearth_planting_window` (~467 tokens)

Goodearth Planting Window

When to start seed, when to put it out, and the last day it still finishes.

Heat requirement answers whether a crop CAN finish here. It says nothing
about when to start, which is the decision actually made with a seed packet
in hand in February. This answers three separate questions:

Start seed indoors — counted back from the day it can go out, for a
transplanted crop. Out — the earliest the frost record and the soil allow,
whichever is later; a tender crop waits for the last spring frost, a hardy
one uses the shoulder before it, a direct sowing waits for the soil, which
lags the air by weeks. Latest — the last day a sowing still has enough heat
left to beat the first fall frost, which is what decides whether an August
succession is worth the seed.

All from this block's own record rather than a zone map. The requirements
are yours.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `crops` (array, required): The crops to date, with your own requirements. Each is {"crop": "Tomato", "gdd_target": 1300, "base_temp": 50} plus any of "frost_hardy", "direct_sow", "min_soil_f" (germination soil temperature) and…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.

### `goodearth_forget_my_ground` (~286 tokens)

Goodearth Forget My Ground

Delete every block you have here, and everything recorded on them.

Blocks, crops, plantings, pest models, wildlife watches, field reports,
tasks, published calendar feeds and the cached weather read for your
ground. A real delete, not a retirement: every other removal in this
service keeps the row as history, and this one does not, because a grower
who asks to be forgotten and is quietly kept has been told something
untrue. Any calendar feed you published stops resolving at once.

\**You remain a patron.** Your balance and your purchase history are not
touched — those are the network's ledger rather than this operator's record
of your farm, and there is no name, email or KYC in this system to forget.
Sign in again with the same npub and you can start over on new ground.

Requires proof of the npub, like any call that reads your record. Free:
charging someone to leave is a toll on the door out.

Input parameters:

- `confirm` (string): Must be exactly "FORGET MY GROUND". A phrase rather than a boolean, because this cannot be undone and confirm=true is what gets sent by reflex.
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) — whose ground to forget.

### `goodearth_block_save` (~328 tokens)

Goodearth Block Save

Save a plot of land, so every other tool can work it by name.

Its area and sample count are measured here from the bounds you give, and
returned — they are facts about the geometry, so there is nothing for you to
keep in step.

Blocks may overlap or nest. A grower who saves the whole farm and then the
meadow inside it has asked two questions about two pieces of ground, and
both are right; the overlap is not a drawing error to correct.

Input parameters:

- `aliases`: Other names you call it. Only needed for a name that shares no words with the saved one — any unambiguous part of the name already works. Omit to keep the aliases it has; pass [] to clear them.
- `base_temp` (number): The base temperature this ground's growing degree days count from.
- `block` (string): Omit to create. Pass an existing block's id to update it.
- `dpop_token` (string)
- `geometry` (object, required): Its bounds: a GeoJSON Polygon, or {lat, lon, radius_m}. It may overlap or sit inside another block — a meadow within the farm around it is two blocks, each answered for its own ground.
- `name` (string, required): What you call this ground, e.g. 'North Field'. Unique among your blocks.
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `retired` (boolean): True to retire it. Nothing is deleted — its record stays readable.

### `goodearth_block_list` (~175 tokens)

Goodearth Block List

The ground you have saved, with its bounds.

The blocks themselves and nothing else — what grows on them, what you watch
for, and what you have seen are their own listing, so this answer stays the
same size whether you farm one plot or forty.

A grower who has saved nothing gets the worked example, marked as such, so
there is always somewhere to stand.

Blocks can overlap — a meadow drawn inside the farm that contains it is two
blocks, each answered for its own ground. Read an overlap as intent, not as
one outline being wrong.

Input parameters:

- `dpop_token` (string)
- `include_retired` (boolean): Include ground you have retired.
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.

### `goodearth_block_item_save` (~293 tokens)

Goodearth Block Item Save

Record what you grow, watch for, saw, or hold seed for on a plot.

A whole batch in one call, because an afternoon in the field produces
several notes at once and each one should not be its own fare.

Input parameters:

- `block` (string, required): The ground this belongs to — its id, its name, or an alias.
- `dpop_token` (string)
- `items`: What to record, as a list. A planting is {crop, gdd_target, set_out}; a pest is a model as pest_threshold takes it; wildlife is an event as wildlife_calendar takes it; an observation is {observed_on,…
- `kind` (string, required): One of: planting, pest, wildlife, observation, seed.
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `retire_ids`: Ids to retire. They stay readable as history; nothing is deleted.
- `season`: The season year these belong to. Defaults to the year of each one's own date. Observations and seed lots belong to no season.

### `goodearth_block_item_list` (~386 tokens)

Goodearth Block Item List

What you grow, watch for, or saw on a plot — a page at a time.

\`as_of` is how a past season answers: the record as it stood that day,
rather than as it stands now.

Sorting and searching happen in the database, over as many rows as the
block holds rather than the page you are looking at.

Input parameters:

- `as_of` (string): Read the record as it STOOD on this date (YYYY-MM-DD) — what was live then, including anything you have retired since.
- `block` (string, required): The ground to read — its id, its name, or an alias.
- `dpop_token` (string)
- `include_retired` (boolean): Include what you have retired.
- `kind` (string, required): One of: planting, pest, wildlife, observation, seed.
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `page` (integer): Zero-based page number.
- `page_size` (integer): Rows per page, up to 200.
- `search` (string): Case-insensitive regex over the name and the event, e.g. 'migration' finds both of a bird's. Empty matches everything.
- `season`: Limit to one season year. Ignored for observations and seed lots.
- `since` (string): Only observations on or after this date (YYYY-MM-DD).
- `sort_col` (string): Order by one of: name, event, driver, starts_on, target_gdd, observed_on, season, created, updated. Omit for the default order — sightings newest first, everything else by when it was added.
- `sort_dir` (string): 'asc' or 'desc'.
- `until` (string): Only observations on or before this date (YYYY-MM-DD).

### `goodearth_disease_risk` (~561 tokens)

Goodearth Disease Risk

Hours of leaf wetness on this ground, and what the disease models make of them.

Returns the estimated wet hours since the season began, every qualifying
infection period each model found, which of its criteria were met and which
were not, and the wet stretch the forecast implies next.

Degree days are the wrong clock for a fungus. What decides an infection is
how long the leaf stayed wet and how warm it was while it did, which is why
a dry August that accumulated heat all month grows no botrytis. A season
with nothing qualifying is reported as exactly that — risk that is absent is
as useful to a grower as risk that is present.

WETNESS IS ESTIMATED, NEVER MEASURED. No feed publishes a leaf wetness
sensor for arbitrary ground, so it is inferred from modelled humidity and
rain, and every answer names the estimator and the feed that fed it. That
matters more here than elsewhere: humidity crosses the 90% line in a step,
and two feeds a couple of degrees apart on dew point can differ threefold on
the hours they count.

Good Earth runs published models against your ground. It does not publish
plant pathology and it never recommends a treatment — registration is
jurisdiction-specific and a label rate is law. Take the decision to your
extension service, whose word counts where this service's does not.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `models`: Which published models to run, as a list. Omit for all of them. Each row names one: {"model": "hutton"} for potato and tomato late blight, {"model": "botrytis"} for grey mould on cut flowers, and lik…
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.
- `season`: A past season year to count instead of this one. Omit for the season to date.

### `goodearth_drying_window` (~373 tokens)

Goodearth Drying Window

When the dew burns off this ground, the dry days ahead, and the next rain.

Answers "is it dry enough yet?" for a grower planning to cut flowers, pick,
mow or make hay. Returns this morning's and tomorrow morning's dew-off hour
(the first hour the leaves are estimated to stay dry for two hours running),
the first run of forecast days with no rain, the next hour of rain, and per
day the rain, wet hours, reference evapotranspiration (FAO-56 ET0) and peak
vapour-pressure deficit — how hard the air is pulling water out of anything
wet. Ten days ahead, from one forecast call.

Not wet is not drying: a still, overcast, humid day wets nothing and dries
little, which is why ET0 travels with every day. Wetness is ESTIMATED from
modelled humidity and rain, never measured, as in `disease_risk`.

Conditions only. Good Earth never says a crop is ready to cut or that hay
will cure — that depends on the crop, the swath and the field — and it
publishes no agronomy.

Input parameters:

- `block` (string, required): The ground to answer for: a block you have saved — its id, its name, one of its aliases, or any part of its name that only one block has (e.g. "Meadow" for "Lower Meadow"). If several match, the erro…
- `dpop_token` (string)
- `npub` (string): Required. Your Nostr public key (npub1...) for credit billing.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lonniev-goodearth-mcp/goodearth-mcp#diagnostics

## Score history

- 2026-09-26: 68
- 2026-09-25: 67
- 2026-09-24: 67
- 2026-09-23: 66
- 2026-09-22: 66
- 2026-09-21: 65
- 2026-09-20: 65
- 2026-09-19: 64
- 2026-09-18: 64
- 2026-09-17: 63
- 2026-09-16: 63
- 2026-09-15: 62

## Common questions

### What is the Good Earth MCP server?

Good Earth is an MCP server listed in the public MCP registry as io.github.lonniev/goodearth-mcp. Climate timing for gardens and small farms: frost, heat, soil and planting dates for your plot. This page covers its hosted endpoint (https://goodearth-mcp.fastmcp.app/mcp).

### Is the Good Earth MCP server safe to use?

Good Earth scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Good Earth MCP server expose?

Good Earth exposes 81 tools: goodearth_check_balance, goodearth_purchase_credits, goodearth_check_payment, goodearth_restore_credits, goodearth_account_statement, and 76 more. Their descriptions and schemas cost roughly 17,750 tokens of context every time the server is loaded.

### Does the Good Earth MCP server require authentication?

No. We connected to Good Earth without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Good Earth MCP server still maintained?

Good Earth is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://goodearth-mcp.fastmcp.app/mcp
- Repository: https://github.com/lonniev/goodearth-mcp
- Website: https://goodearth.tollbooth-dpyc.com/
- Changelog RSS feed: https://verifymcp.io/servers/lonniev-goodearth-mcp/goodearth-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/lonniev-goodearth-mcp/goodearth-mcp.json
- HTML version of this page: https://verifymcp.io/servers/lonniev-goodearth-mcp/goodearth-mcp
