# Siltwell (remote · app.siltwell.com)

Your garden notebook: ask about your beds, plantings, harvests and frost dates, and log your work.

- Trust score: 76/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

> **Recent critical change**: Authorization (2026-10-14). See the changelog below before you install this server.

## Components

- remote · `app.siltwell.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-siltwell-garden/app.md), [page](https://verifymcp.io/servers/com-siltwell-garden/app)

## Channel facts

- Endpoint: `https://app.siltwell.com/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-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (add_planting).
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4360 tokens (~136/item across 32 items; 32 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% 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.
  - All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Siltwell MCP server?

Siltwell is a hosted endpoint at https://app.siltwell.com/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 com-siltwell-garden 'https://app.siltwell.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-siltwell-garden": {
      "url": "https://app.siltwell.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-siltwell-garden": {
      "type": "http",
      "url": "https://app.siltwell.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-siltwell-garden]
url = "https://app.siltwell.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-siltwell-garden": {
      "type": "remote",
      "url": "https://app.siltwell.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-siltwell-garden --url 'https://app.siltwell.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-siltwell-garden:
    url: "https://app.siltwell.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-siltwell-garden": {
      "Transport": "http",
      "Url": "https://app.siltwell.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-siltwell-garden -t streamable-http -u 'https://app.siltwell.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-siltwell-garden": {
      "type": "http",
      "url": "https://app.siltwell.com/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-13 (score 76, 0)

- [security] Stability: 0.97 → pass

### 2026-11-11 (score 76, +1)

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

### 2026-11-09 (score 75, +1)

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

### 2026-11-07 (score 74, +1)

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

### 2026-11-06 (score 73, 0)

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

### 2026-11-05 (score 73, +1)

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

### 2026-11-03 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (32)

### `query_plantings` (~98 tokens)

Find plantings

List the user's plantings (what is planted, where, when, how, current status). Use when the user asks what they planted, when something was sown/transplanted, or what's growing in a bed.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `plant` (string): Filter by plant common name (contains, case-insensitive).
- `status` (string): Default: active.

### `search_events` (~116 tokens)

Search the garden log

Search the garden log: watering, fertilizing, transplanting, pruning, pest sightings, treatments, frost damage, notes. Use when the user asks when they last did something or what happened in the garden.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `limit` (number): Max rows, default 50.
- `plant` (string): Filter to events on plantings of this plant name.
- `since` (string): ISO date lower bound (inclusive).
- `type` (string)

### `get_harvests` (~65 tokens)

Get harvests

List harvests with per-plant totals. Use when the user asks what/how much they harvested.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `plant` (string)
- `since` (string): ISO date lower bound.

### `list_beds` (~82 tokens)

List beds

List the garden's beds: name, type (outdoor_bed/raised_bed/greenhouse/grow_light_shelf/pot), dimensions in cm, notes, and how many active plantings each holds. Use to see what beds exist and where there may be room.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.

### `get_bed_layout` (~116 tokens)

Get a bed's layout

Read a bed's layout grid: the bed's dimensions (cm) plus each placed planting's footprint (xCm, yCm from the bed's top-left; wCm × hCm), and any active plantings not yet placed. Use to reason about space — e.g. "is there 60 cm free at the front of Bed 2?". Positions are written by place_planting.

Input parameters:

- `bed` (string, required): Bed name.
- `garden` (string): Garden name; defaults to the user's first garden.

### `get_current_conditions` (~60 tokens)

Get current conditions

Current weather at the garden (station if connected, else forecast) plus per-bed soil moisture/temperature. Use for "how is the garden right now / should I water".

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.

### `get_soil_readings` (~48 tokens)

Get soil readings

Latest soil moisture % and soil temperature per bed, with bed names. Use for watering/sowing decisions.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.

### `get_forecast` (~49 tokens)

Get the forecast

7-day forecast for the garden with overnight-low frost alerts. Use for planting timing, frost protection, watering plans.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.

### `get_history` (~83 tokens)

Get weather history

Daily weather history for the garden: min/max temp, rain, growing degree days (base 10 °C) with a cumulative total. Use for "how warm/wet has it been" and growth-progress questions.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `since` (string): ISO date, default 90 days ago.

### `get_plan` (~87 tokens)

Get sowing windows and care tasks

Upcoming sowing/transplant windows computed from the user's plant catalog and the garden's frost dates, plus zone, frost dates, and any due care tasks (watering/fertilizing, with a rain-skip hint). Use for "what should I plant/start/transplant and when" and "what care is due".

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.

### `log_event` (~223 tokens)

Log a garden event

Record something the user did or observed: watered, fertilized, transplanted, pruned, pest sighting, treatment, frost damage, or a note. Attach it to a plant's active planting via `plant`, to a bed via `bed`, or garden-wide with neither. If both plant and bed are given, the event attaches to the plant's planting.

Input parameters:

- `amount` (string): For fertilized/treated.
- `bed` (string): Bed name — for bed-level events.
- `garden` (string): Garden name; defaults to the user's first garden.
- `note` (string)
- `occurredAt` (string): ISO datetime; default now.
- `pestName` (string): For type=pest.
- `plant` (string): Plant name — targets its most recent active planting.
- `plantingId` (string): Exact planting id (from query_plantings) — overrides plant.
- `product` (string): For fertilized/treated.
- `severity` (string): For type=pest.
- `type` (string, required)

### `record_harvest` (~116 tokens)

Record a harvest

Record a harvest, e.g. "I picked 2 kg of cucumbers" or "2 lb of tomatoes". Resolves the plant's active planting automatically. Pounds and ounces are stored as grams.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `harvestedAt` (string): ISO datetime; default now.
- `notes` (string)
- `plant` (string)
- `plantingId` (string)
- `quantity` (number, required)
- `unit` (string, required)

### `add_planting` (~179 tokens)

Add a planting

Record that the user planted/sowed something: creates the plant in their catalog if new and the planting in the named bed. Passing variety replaces the variety stored on an existing plant with the same name.

Input parameters:

- `bed` (string, required)
- `garden` (string): Garden name; defaults to the user's first garden.
- `method` (string): Default direct_seed.
- `notes` (string)
- `plant` (string, required)
- `quantity` (number)
- `sownAt` (string): ISO date; default today.
- `transplantedAt` (string): ISO date the seedling went into the bed (indoor starts).
- `variety` (string): Variety/cultivar, e.g. "Sremski F1". Stored on the plant; replaces the variety of an existing plant with the same name.

### `log_curing` (~90 tokens)

Log curing

Record that a harvested crop has finished curing (or dismiss the reminder). Use when the gardener says they've cured, dried, trimmed or stored a crop like garlic, onions or herbs.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `kind` (string, required)
- `plantingId` (string, required): Exact planting id (from query_plantings or get_bed_layout).

### `create_bed` (~137 tokens)

Create a bed

Add a garden bed. `type` is one of outdoor_bed (in-ground), raised_bed, greenhouse, grow_light_shelf, pot. Dimensions (lengthCm/widthCm/heightCm) are optional. Use when the user wants a new bed or planting area.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `heightCm` (number): Height/depth in centimeters (optional).
- `lengthCm` (number): Length in centimeters (optional).
- `name` (string, required)
- `type` (string, required)
- `widthCm` (number): Width in centimeters (optional).

### `update_bed` (~124 tokens)

Update a bed

Change an existing bed's name, type, or dimensions. Identify the bed by its current name. Use when the user wants to rename a bed, change its type, or set/adjust its dimensions.

Input parameters:

- `bed` (string, required): The bed's current name.
- `garden` (string): Garden name; defaults to the user's first garden.
- `heightCm` (number)
- `lengthCm` (number)
- `name` (string): New name (optional).
- `type` (string): New type (optional).
- `widthCm` (number)

### `set_care_schedule` (~317 tokens)

Set a care schedule

Create a recurring care schedule (water/fertilize/custom). Scope it to a plant (its active planting), a bed, or the whole garden. Recurrence is EITHER everyDays (e.g. 3) OR weekdays (e.g. ['monday','thursday']). Use when the user wants a repeating watering/feeding reminder. Optionally end it on a date (endsOn) or after N completions (endsAfter); use at most one.

Input parameters:

- `amount` (string): Optional, e.g. '2 L'.
- `bed` (string): Scope to this bed (optional; ignored if plant is given).
- `endsAfter` (number): Optional: stop after this many completions. Use at most one of endsOn / endsAfter.
- `endsOn` (string): Optional last date YYYY-MM-DD (inclusive); no task after it. Use at most one of endsOn / endsAfter.
- `everyDays` (number): Repeat every N days (1–365). Use this OR weekdays.
- `garden` (string): Garden name; defaults to the user's first garden.
- `label` (string): Optional label (mainly for custom).
- `plant` (string): Scope to this plant's active planting (optional).
- `startDate` (string): First due date YYYY-MM-DD; default today.
- `type` (string): Default water.
- `weekdays` (array): Repeat on these weekdays, e.g. ['monday','thursday']. Use this OR everyDays.

### `update_planting` (~189 tokens)

Update a planting

Change a planting's status (active/finished/failed), notes, quantity, transplant date, variety, or MOVE it to another bed (pass bed with the target bed's name — history stays attached; any layout position is cleared, re-place with place_planting). Identify the planting by plant name or plantingId.

Input parameters:

- `bed` (string): Move the planting to this bed (by name).
- `garden` (string): Garden name; defaults to the user's first garden.
- `notes` (string)
- `plant` (string): Plant name of the planting to update.
- `plantingId` (string): Or the planting id directly.
- `quantity` (number)
- `status` (string)
- `transplantedAt` (string): ISO date the seedling went into the bed.
- `variety` (string): Variety/cultivar; stored on the plant.

### `delete_planting` (~129 tokens)

Archive a planting

Remove a planting from the garden. Siltwell archives it: it disappears from the app and from these tools, and its care schedules stop. Its harvests, events and photos stay stored, but the app has no way to restore it. Identify by plant name or plantingId. Use when the user says to delete/remove a planting (e.g. one added by mistake).

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `plant` (string): Plant name of the planting to remove.
- `plantingId` (string): Or the planting id directly.

### `delete_bed` (~115 tokens)

Archive a bed

Remove a bed from the garden. Siltwell archives it: it leaves the bed lists in the app and in these tools, its care schedules stop, and planned plantings queued for it are skipped. Past weather history still shows its name. The app has no way to restore it. Blocked while the bed has active plantings; remove or finish those first. Identify by bed name.

Input parameters:

- `bed` (string, required): The bed's name.
- `garden` (string): Garden name; defaults to the user's first garden.

### `delete_schedule` (~135 tokens)

Delete a care schedule

Turn off a recurring care schedule (stops its reminders). Identify it by scheduleId, or by scope — plant (its active planting), bed, or garden-wide (neither) — optionally narrowed by type (water/fertilize/custom). Use when the user says to stop a watering/feeding reminder.

Input parameters:

- `bed` (string): Scope: this bed.
- `garden` (string): Garden name; defaults to the user's first garden.
- `plant` (string): Scope: this plant's active planting.
- `scheduleId` (string): The schedule's id.
- `type` (string): Narrow to this care type.

### `update_harvest` (~152 tokens)

Update a harvest

Correct a logged harvest — the most-recent harvest of a plant (by name) or a specific harvestId. Edit quantity, unit, notes, or the date. Use when the user says a harvest they recorded was wrong.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `harvestId` (string): Or a specific harvest id.
- `harvestedAt` (string): Corrected ISO datetime.
- `notes` (string)
- `plant` (string): Edit the most-recent harvest of this plant.
- `quantity` (number): Corrected amount (> 0).
- `unit` (string): lb and oz are stored as grams and need a quantity alongside.

### `place_planting` (~219 tokens)

Place a planting in a bed

Place or move a planting on its bed's layout grid — set its position (xCm, yCm measured from the bed's top-left corner) and footprint (wCm × hCm) in centimeters. Identify the planting by plant name or plantingId. Use when the user wants to arrange, position, or move a plant within its bed. For a planting that already spans several grid squares, use the app's layout editor instead.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `hCm` (number, required): Footprint height in cm (> 0).
- `plant` (string): Plant name of the planting to place.
- `plantingId` (string): Or the planting id directly.
- `wCm` (number, required): Footprint width in cm (> 0).
- `xCm` (number, required): X offset from the bed's top-left, in cm (≥ 0).
- `yCm` (number, required): Y offset from the bed's top-left, in cm (≥ 0).

### `list_planned_plantings` (~100 tokens)

List planned plantings

List the garden's succession plan — future plantings queued for a bed that haven't been sown yet (only status='planned'; done/skipped entries are omitted). Use when the user asks what's coming up next, what they've planned to plant, or wants to review their succession plan. For plantings already in the ground, use query_plantings instead.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.

### `add_planned_planting` (~171 tokens)

Plan a planting

Queue a future planting for a bed as part of a succession plan — it is NOT yet sown (use add_planting for something the user already planted). Use when the user wants to plan ahead, e.g. "plan to plant more carrots in Bed 2 on August 15".

Input parameters:

- `bed` (string, required): The bed's name.
- `cropSlug` (string): Optional catalog crop slug.
- `displayName` (string, required): What to call this planting, e.g. 'Fall Carrots'.
- `garden` (string): Garden name; defaults to the user's first garden.
- `method` (string): Default direct_seed.
- `notes` (string)
- `quantity` (number)
- `targetDate` (string, required): Planned planting date, YYYY-MM-DD.

### `update_planned_planting` (~154 tokens)

Update a planned planting

Update a queued succession-plan entry: change its status (planned/done/skipped), reschedule its targetDate, or adjust quantity/notes. Identify it by id (from list_planned_plantings). Use when the user sows a planned planting (mark status done), decides to skip it, or wants to reschedule/adjust it.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `id` (string, required): The planned planting's id (from list_planned_plantings).
- `notes` (string)
- `quantity` (number)
- `status` (string)
- `targetDate` (string): New planned date, YYYY-MM-DD.

### `delete_planned_planting` (~106 tokens)

Delete a planned planting

Remove an entry from the succession plan outright (a queued future planting that hasn't been sown). This is a hard delete, not recoverable — for a planting already sown/growing, use delete_planting instead. Identify it by id (from list_planned_plantings).

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `id` (string, required): The planned planting's id (from list_planned_plantings).

### `get_season_plan` (~140 tokens)

Get the season plan

Compute the garden's rest-of-season planting schedule: every bed's next crops, chained forward to the effective first frost, deconflicted across beds with crop rotation and curated sow windows. Returns a PROPOSAL only — nothing is written; use add_planned_planting to accept a row into the succession plan. Returns every bed's chain, or one bed's full chain plus remainingCount for the rest when the garden's plan covers one bed.

Input parameters:

- `garden` (string): Garden name; defaults to the user's first garden.
- `today` (string): Optional YYYY-MM-DD to plan from; defaults to today in the garden's timezone.

### `lookup_frost_dates` (~147 tokens)

Look up frost dates for a place

Average last spring frost, average first fall frost and hardiness zone for any place, from 10 years of weather records. Works without a Siltwell account. Dates are MM-DD. For the signed-in user's own garden, get_plan returns the garden's zone and frost dates, with the frost dates adjusted for its microclimate.

Input parameters:

- `latitude` (number): Latitude in decimal degrees. Give it with longitude instead of place.
- `longitude` (number): Longitude in decimal degrees. Give it with latitude instead of place.
- `place` (string): Town plus region or country, for example "Portland, Oregon". Omit it to use the signed-in user's garden.

### `lookup_planting_windows` (~218 tokens)

Look up planting windows for a place

When to start seeds indoors, plant out, and sow for a fall harvest at any place, crop by crop, with the days left to sow today. Works without a Siltwell account. Dates are YYYY-MM-DD. Without crops, it returns the 30 crops with the soonest next step; pass crops to see others. For the signed-in user's own garden, get_plan returns sowing and transplant windows for the garden's own plants, counted from its microclimate-adjusted last frost date.

Input parameters:

- `crops` (array): Crop names to include, for example ["tomato", "garlic"]. Omit to get the 30 crops with the soonest next step.
- `latitude` (number): Latitude in decimal degrees. Give it with longitude instead of place.
- `longitude` (number): Longitude in decimal degrees. Give it with latitude instead of place.
- `place` (string): Town plus region or country, for example "Portland, Oregon". Omit it to use the signed-in user's garden.

### `lookup_growing_season` (~147 tokens)

Look up growing season length for a place

Frost-free season length and seasonal growing degree days at any place, and whether heat-loving crops get enough heat to ripen. Works without a Siltwell account. For the signed-in user's own garden, get_plan returns the microclimate-adjusted frost dates that bound its season, and get_history returns its daily growing degree days.

Input parameters:

- `latitude` (number): Latitude in decimal degrees. Give it with longitude instead of place.
- `longitude` (number): Longitude in decimal degrees. Give it with latitude instead of place.
- `place` (string): Town plus region or country, for example "Portland, Oregon". Omit it to use the signed-in user's garden.

### `lookup_frost_risk` (~153 tokens)

Look up frost risk this week for a place

Forecast lows for the next 7 days at any place and the nights at risk of frost. Each frost night is dated by the morning its low falls on, so protect plants the evening before that date. Works without a Siltwell account. For the signed-in user's own garden, get_forecast returns this forecast with the garden's microclimate adjustment applied.

Input parameters:

- `latitude` (number): Latitude in decimal degrees. Give it with longitude instead of place.
- `longitude` (number): Longitude in decimal degrees. Give it with latitude instead of place.
- `place` (string): Town plus region or country, for example "Portland, Oregon". Omit it to use the signed-in user's garden.

## Diagnostics

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

## Score history

- 2026-11-21: 76
- 2026-11-20: 76
- 2026-11-19: 76
- 2026-11-18: 76
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 76
- 2026-11-10: 75
- 2026-11-09: 75
- 2026-11-08: 74
- 2026-11-07: 74
- 2026-11-06: 73
- 2026-11-05: 73
- 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: 69
- 2026-10-26: 68
- 2026-10-25: 68
- 2026-10-24: 67
- 2026-10-23: 67

## Common questions

### What is the Siltwell MCP server?

Siltwell is an MCP server listed in the public MCP registry as com.siltwell/garden. Your garden notebook: ask about your beds, plantings, harvests and frost dates, and log your work. This page covers its hosted endpoint (https://app.siltwell.com/mcp).

### Is the Siltwell MCP server safe to use?

Siltwell scores 76 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 Siltwell MCP server expose?

Siltwell exposes 32 tools: query_plantings, search_events, get_harvests, list_beds, get_bed_layout, and 27 more. Their descriptions and schemas cost roughly 4,265 tokens of context every time the server is loaded.

### Does the Siltwell MCP server require authentication?

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

### Is the Siltwell MCP server still maintained?

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

### What did VerifyMCP test on the Siltwell MCP server?

VerifyMCP ran 13 checks on Siltwell, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://app.siltwell.com/mcp
- Website: https://siltwell.com/ai-assistants
- Changelog RSS feed: https://verifymcp.io/servers/com-siltwell-garden/app.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-siltwell-garden/app/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-siltwell-garden/app.json
- HTML version of this page: https://verifymcp.io/servers/com-siltwell-garden/app
