# xyz.gardenpatch/gardenpatch (remote · gardenpatch.xyz)

Paid per call over x402: growth coaches, small utilities and real-world actions. USDC on Base.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `gardenpatch.xyz`: 72/100 (this document), [markdown](https://verifymcp.io/servers/xyz-gardenpatch-gardenpatch/gardenpatch.md), [page](https://verifymcp.io/servers/xyz-gardenpatch-gardenpatch/gardenpatch)

## Channel facts

- Endpoint: `https://gardenpatch.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-04.

- **Endpoint Security**: 63/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 9 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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 854 tokens (~94/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 xyz.gardenpatch/gardenpatch MCP server?

xyz.gardenpatch/gardenpatch is a hosted endpoint at https://gardenpatch.xyz/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 xyz-gardenpatch-gardenpatch 'https://gardenpatch.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-gardenpatch-gardenpatch": {
      "url": "https://gardenpatch.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-gardenpatch-gardenpatch": {
      "type": "http",
      "url": "https://gardenpatch.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-gardenpatch-gardenpatch]
url = "https://gardenpatch.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-gardenpatch-gardenpatch": {
      "type": "remote",
      "url": "https://gardenpatch.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-gardenpatch-gardenpatch --url 'https://gardenpatch.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-gardenpatch-gardenpatch:
    url: "https://gardenpatch.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-gardenpatch-gardenpatch": {
      "Transport": "http",
      "Url": "https://gardenpatch.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-gardenpatch-gardenpatch -t streamable-http -u 'https://gardenpatch.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xyz-gardenpatch-gardenpatch": {
      "type": "http",
      "url": "https://gardenpatch.xyz/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-11-03 (score 72, +1)

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

### 2026-11-01 (score 71, +1)

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

### 2026-10-30 (score 70, +1)

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

### 2026-10-28 (score 69, +1)

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

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

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

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

- [security] Tool “call_tool” rewrote its description, which is the text the model reads
- [security] Tool “list_tools” rewrote its description, which is the text the model reads

### 2026-10-23 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 66)

First indexed and scored.

## MCP tools (9)

### `list_coaches` (~56 tokens)

List coaches

Free. The catalog of 7 growth coaches, the 16 modes they sell, and the current price of each. Call this first — it is generated from the same registry the paid endpoint validates against, so it is never stale.

### `list_actions` (~46 tokens)

List actions

Free. The catalog of paid real-world side effects, such as sending a review request. An action does something rather than returning advice, so it carries consent rules a coach call does not.

### `list_tools` (~63 tokens)

List tools

Free. The catalog of 6 small paid utilities (QR codes, time zone conversion, Markdown to HTML, calendar .ics files, website growth signals, image resize) with each one's price, request schema and a worked example. One endpoint, one job, one payment.

### `get_schema` (~86 tokens)

Get a JSON Schema

Free. The published request or response JSON Schema for one mode or one action. Use it to build a request you know will validate before you pay for it.

Input parameters:

- `direction` (string): Which side of the contract to return.
- `id` (string, required): A mode id, an action slug, or a tool slug.
- `kind` (string, required): Which catalog the id belongs to.

### `sandbox_call` (~91 tokens)

Try a coach for free

Free, and no wallet needed. Returns a schema-valid sample response for a mode: same envelope, same field names, same deliverable shape as a paid call. It is a fixed sample for the mode, not an answer to your input — that is what makes it free. Build your integration against this first.

Input parameters:

- `agent` (string, required): Which coach.
- `mode` (string, required): Which job to sample.

### `call_coach` (~178 tokens)

Call a coach (paid)

Paid, from $0.18 per call, settled in USDC on Base over x402. Returns a growth diagnosis, the arithmetic behind it, concrete actions, and a typed deliverable. Without payment this returns the payment requirements as a structured error you can settle and retry. Try sandbox_call first if you only need to see the shape.

Input parameters:

- `agent` (string, required): Which coach to call.
- `context` (object): Company, metrics, offer and audience. Numbers here buy arithmetic instead of adjectives.
- `idempotency_key` (string): Reuse on a retry of the same job to avoid paying twice.
- `messages` (array, required): The conversation so far. At least one entry.
- `mode` (string, required): The job to buy. Sending a mode a coach does not sell is a 400, not a fallback.

### `call_action` (~142 tokens)

Perform an action (paid)

Paid. HAS A REAL-WORLD SIDE EFFECT: it puts a message in front of an actual person. Requires a consent block stating how and when that person agreed to be contacted. There is no sandbox for this — a simulated send cannot be told apart from a real one. Retries are safe with the same idempotency key; a new key means a genuine second send.

Input parameters:

- `body` (object, required): The action request, including its consent block. Call get_schema first.
- `idempotency_key` (string): Reuse to retry safely; a new key means a genuine second send.
- `slug` (string, required): Which action. Use the published slug.

### `call_tool` (~103 tokens)

Run a tool (paid)

Paid, from $0.01 per call, settled in USDC on Base over x402. Runs one utility and returns its result. Tools contact no one and store nothing; website signals and image resize read only the one public URL you name. A request refused for its input is never charged.

Input parameters:

- `body` (object, required): The tool's request. Call list_tools for its schema and an example.
- `slug` (string, required): Which tool. Use the published slug.

### `get_receipt` (~89 tokens)

Re-read a paid call

Free. Returns a call you already paid for: amount, mode, usage, and the deliverable again. Only the wallet that paid can read it, and only while the receipt has not expired.

Input parameters:

- `payer_address` (string): The wallet that paid, if you are not presenting a payment proof.
- `receipt_id` (string, required): The rcpt_… id from a paid 200.

## Diagnostics

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

## Score history

- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 67
- 2026-10-24: 67
- 2026-10-23: 66
- 2026-10-22: 66

## Common questions

### What is the xyz.gardenpatch/gardenpatch MCP server?

xyz.gardenpatch/gardenpatch is an MCP server listed in the public MCP registry as xyz.gardenpatch/gardenpatch. Paid per call over x402: growth coaches, small utilities and real-world actions. USDC on Base. This page covers its hosted endpoint (https://gardenpatch.xyz/mcp).

### Is the xyz.gardenpatch/gardenpatch MCP server safe to use?

xyz.gardenpatch/gardenpatch scores 72 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 xyz.gardenpatch/gardenpatch MCP server expose?

xyz.gardenpatch/gardenpatch exposes 9 tools: list_coaches, list_actions, list_tools, get_schema, sandbox_call, and 4 more. Their descriptions and schemas cost roughly 854 tokens of context every time the server is loaded.

### Does the xyz.gardenpatch/gardenpatch MCP server require authentication?

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

### Is the xyz.gardenpatch/gardenpatch MCP server still maintained?

xyz.gardenpatch/gardenpatch is still listed as active in the MCP registry. We last reached this channel on 4 November 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://gardenpatch.xyz/mcp
- Website: https://gardenpatch.xyz/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/xyz-gardenpatch-gardenpatch/gardenpatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-gardenpatch-gardenpatch/gardenpatch.json
- HTML version of this page: https://verifymcp.io/servers/xyz-gardenpatch-gardenpatch/gardenpatch