xyz.gardenpatch/gardenpatch
REMOTE · GARDENPATCH.XYZ
Paid per call over x402: growth coaches, small utilities and real-world actions. USDC on Base.
Available components
Last scanned (17 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 854 tokens (~94/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +1
- 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 security
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://gardenpatch.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gardenpatch.xyz | CN=YR1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | RSA 2048 | SHA256-RSA | 629cc28b3b867e33547cff087700441ad13 |
| SANs: gardenpatch.xyz | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gardenpatch.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| gardenpatch.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' blob:; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data: blob:; media-src 'self' https://ua4wyv6qmriusp9q.public.blob.vercel-storage.com; connect-src 'self' blob: https://gardenpatch.xyz https://api.openai.com https://vitals.vercel-insights.com https://raw.githack.com; worker-src 'self' blob:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gardenpatch.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://gardenpatch.xyz/mcp | HTTPS enforced | 308 | https://gardenpatch.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_action Perform an action (paid) ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | 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 | yes | Which action. Use the published slug. |
No output schema declared.
No examples provided.
call_coach Call a coach (paid) ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | 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 | yes | The conversation so far. At least one entry. |
| mode | string | yes | The job to buy. Sending a mode a coach does not sell is a 400, not a fallback. |
No output schema declared.
No examples provided.
call_tool Run a tool (paid) ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | The tool's request. Call list_tools for its schema and an example. |
| slug | string | yes | Which tool. Use the published slug. |
No output schema declared.
No examples provided.
get_receipt Re-read a paid call ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payer_address | string | – | The wallet that paid, if you are not presenting a payment proof. |
| receipt_id | string | yes | The rcpt_… id from a paid 200. |
No output schema declared.
No examples provided.
get_schema Get a JSON Schema ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Which side of the contract to return. |
| id | string | yes | A mode id, an action slug, or a tool slug. |
| kind | string | yes | Which catalog the id belongs to. |
No output schema declared.
No examples provided.
list_actions List actions ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_coaches List coaches ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tools List tools ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sandbox_call Try a coach for free ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Which coach. |
| mode | string | yes | Which job to sample. |
No output schema declared.
No examples provided.
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.
remote · gardenpatch.xyz
claude mcp add --transport http xyz-gardenpatch-gardenpatch 'https://gardenpatch.xyz/mcp'
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.