Home / MCP registry index / io.gardenarena/gardenscript
GardenArena GardenScript
io.gardenarena/gardenscript in the official MCP registry.
Endpoint https://gardenarena.io/mcp.
The registry describes it as: Simulate farms, validate GardenScript and compare policies with Rust. No outbound LLM calls.
We read its 30 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.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http gardenscript https://gardenarena.io/mcp{
"mcpServers": {
"gardenscript": {
"url": "https://gardenarena.io/mcp"
}
}
}code --add-mcp '{"name":"gardenscript","type":"http","url":"https://gardenarena.io/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.
Tools it advertises
validate_gardenscript get_bamboo_scene bamboo_challenge_get coop_workshop_get coop_workshop_run farm_workshop_get farm_workshop_run farm_next_event farm_autopilot_run farm_campaign_get farm_campaign_run farm_policy_get farm_policy_validate farm_policy_run farm_compare_get farm_compare_run farm_weather_search farm_weather_get bamboo_training_run bamboo_training_explain bamboo_training_artifact list_garden_arenas get_garden_arena submit_garden_strategy get_garden_results entry_create strategy_validate strategy_prepare_seal strategy_seal artifact_verify
Run this server? Show the check in your README
The badge reflects the latest weekly read:
[](https://lazaretto.dev/mcp-registry/io-gardenarena-gardenscript)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.
Related
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| Huggingface io.github.pipeworx-io/huggingface | 54 tools, nothing matched 2026-10-27 |
| io.github.DarthSander/agentdata-nl io.github.DarthSander/agentdata-nl | 53 tools, nothing matched 2026-10-22 |
| Gemini Crypto io.github.pipeworx-io/gemini-crypto | 52 tools, nothing matched 2026-10-27 |
| Rankwise com.tryrankwise/rankwise | 49 tools, nothing matched 2026-10-26 |
| Tensorust com.tensorust/mcp | 46 tools, nothing matched 2026-10-27 |