Siltwell
REMOTE · APP.SILTWELL.COM
Your garden notebook: ask about your beds, plantings, harvests and frost dates, and log your work.
Available components
Last scanned (21 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category IoT and Hardware
Recent critical change
Authorization (14 Oct 2026). See the changelog before you install this server.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (add_planting). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 13 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +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.
- 9 Nov 26 +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.
- 7 Nov 26 +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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
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 21 Nov 2026 · Probed https://app.siltwell.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=siltwell.com | CN=WE1,O=Google Trust Services,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f2a59130da66a53f0ed5eb82035902a7 |
| SANs: siltwell.com, app.siltwell.com, *.app.siltwell.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.siltwell.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| siltwell.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.siltwell.com/mcp | Verified | 200 | |
| http (plaintext) | http://app.siltwell.com/mcp | HTTPS enforced | 301 | https://app.siltwell.com/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 →
add_planned_planting Plan a planting ~171
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".
| Name | Type | Req | Description |
|---|---|---|---|
| bed | string | yes | The bed's name. |
| cropSlug | string | – | Optional catalog crop slug. |
| displayName | string | yes | 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 | yes | Planned planting date, YYYY-MM-DD. |
No output schema declared.
No examples provided.
add_planting Add a planting ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bed | string | yes | – |
| garden | string | – | Garden name; defaults to the user's first garden. |
| method | string | – | Default direct_seed. |
| notes | string | – | – |
| plant | string | yes | – |
| 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. |
No output schema declared.
No examples provided.
create_bed Create a bed ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| type | string | yes | – |
| widthCm | number | – | Width in centimeters (optional). |
No output schema declared.
No examples provided.
delete_bed Archive a bed ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bed | string | yes | The bed's name. |
| garden | string | – | Garden name; defaults to the user's first garden. |
No output schema declared.
No examples provided.
delete_planned_planting Delete a planned planting ~106
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).
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
| id | string | yes | The planned planting's id (from list_planned_plantings). |
No output schema declared.
No examples provided.
delete_planting Archive a planting ~129
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
delete_schedule Delete a care schedule ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_bed_layout Get a bed's layout ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bed | string | yes | Bed name. |
| garden | string | – | Garden name; defaults to the user's first garden. |
No output schema declared.
No examples provided.
get_current_conditions Get current conditions ~60
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".
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
No output schema declared.
No examples provided.
get_forecast Get the forecast ~49
7-day forecast for the garden with overnight-low frost alerts. Use for planting timing, frost protection, watering plans.
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
No output schema declared.
No examples provided.
get_harvests Get harvests ~65
List harvests with per-plant totals. Use when the user asks what/how much they harvested.
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
| plant | string | – | – |
| since | string | – | ISO date lower bound. |
No output schema declared.
No examples provided.
get_history Get weather history ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
| since | string | – | ISO date, default 90 days ago. |
No output schema declared.
No examples provided.
get_plan Get sowing windows and care tasks ~87
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".
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
No output schema declared.
No examples provided.
get_season_plan Get the season plan ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_soil_readings Get soil readings ~48
Latest soil moisture % and soil temperature per bed, with bed names. Use for watering/sowing decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
No output schema declared.
No examples provided.
list_beds List beds ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
No output schema declared.
No examples provided.
list_planned_plantings List planned plantings ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
No output schema declared.
No examples provided.
log_curing Log curing ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
| kind | string | yes | – |
| plantingId | string | yes | Exact planting id (from query_plantings or get_bed_layout). |
No output schema declared.
No examples provided.
log_event Log a garden event ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
lookup_frost_dates Look up frost dates for a place ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
lookup_frost_risk Look up frost risk this week for a place ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
lookup_growing_season Look up growing season length for a place ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
lookup_planting_windows Look up planting windows for a place ~218
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
place_planting Place a planting in a bed ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
| hCm | number | yes | Footprint height in cm (> 0). |
| plant | string | – | Plant name of the planting to place. |
| plantingId | string | – | Or the planting id directly. |
| wCm | number | yes | Footprint width in cm (> 0). |
| xCm | number | yes | X offset from the bed's top-left, in cm (≥ 0). |
| yCm | number | yes | Y offset from the bed's top-left, in cm (≥ 0). |
No output schema declared.
No examples provided.
query_plantings Find plantings ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
record_harvest Record a harvest ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| unit | string | yes | – |
No output schema declared.
No examples provided.
search_events Search the garden log ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
set_care_schedule Set a care schedule ~317
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
update_bed Update a bed ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bed | string | yes | 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 | – | – |
No output schema declared.
No examples provided.
update_harvest Update a harvest ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
update_planned_planting Update a planned planting ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| garden | string | – | Garden name; defaults to the user's first garden. |
| id | string | yes | The planned planting's id (from list_planned_plantings). |
| notes | string | – | – |
| quantity | number | – | – |
| status | string | – | – |
| targetDate | string | – | New planned date, YYYY-MM-DD. |
No output schema declared.
No examples provided.
update_planting Update a planting ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · app.siltwell.com
claude mcp add --transport http com-siltwell-garden 'https://app.siltwell.com/mcp'
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.