Good Earth

Goodearth Request Npub Proof

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 one-time challenge nonce shown in the DM. Pass it to receive_npub_proof to collect the reply. It is a matching token, not a credential: on its own it authorizes nothing.

Lifecycle: receive_npub_proof returns the proof grant, which expires after the duration the patron named in their reply. When it expires, call request_npub_proof again for a fresh challenge, then wait for the user, then call receive_npub_proof.

Free.

Input Schema

TableJSON Schema

Name	Required	Description
`reason`	No	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 recipient sees why they are being asked — especially useful when the signer is unknown to them.
`verify_at`	No	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 Device Grant ``verification_uri``, generalized: the user approves only if the code in the DM matches the one you displayed there, so an unsolicited request they've never seen is refused. Signed into the attestation.
`patron_npub`	No	Required. The patron's npub to request proof from.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and discloses rich behavior: it sends a challenge DM, requires a human reply, returns a one-time dpop_token nonce that authorizes nothing, and warns that receive_npub_proof destructively drains the relay mailbox. It also explains expiration and the need to re-request a fresh challenge.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action, then clearly separates the flow type, human-in-the-loop requirement, return value, and lifecycle. Every sentence contributes necessary routing or behavioral context for a complex multi-step tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a human-in-the-loop proof-request tool with an output schema, the description supplies the missing behavioral context: when to use it, what it returns, what not to do, and how the lifecycle continues. The agent has enough information to invoke it correctly and sequence the sibling receive_npub_proof call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents reason, verify_at, and patron_npub thoroughly. The main description adds no additional parameter-level syntax, format, or edge-case guidance beyond what the schema provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: request npub ownership proof from a patron via Nostr DM. It explicitly distinguishes this flow from the sibling tool request_credential_channel, so an agent can tell them apart without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit triggers: use when a call returns proof_required, and use request_credential_channel when delivering API keys or OAuth secrets. It also prescribes the human-in-the-loop protocol: stop, tell the user, wait for confirmation, do not poll or retry.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Good Earth tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.