Home / MCP registry index / com.siltwell/garden
Siltwell
com.siltwell/garden in the official MCP registry.
Endpoint https://app.siltwell.com/mcp.
The registry describes it as: Your garden notebook: ask about your beds, plantings, harvests and frost dates, and log your work.
We read its 32 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
query_plantings search_events get_harvests list_beds get_bed_layout get_current_conditions get_soil_readings get_forecast get_history get_plan log_event record_harvest add_planting log_curing create_bed update_bed set_care_schedule update_planting delete_planting delete_bed delete_schedule update_harvest place_planting list_planned_plantings add_planned_planting update_planned_planting delete_planned_planting get_season_plan lookup_frost_dates lookup_planting_windows lookup_growing_season lookup_frost_risk
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-siltwell-garden)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.