Shroom Labs MCP server
io.shroomlabs/shroom-labsshroomlabs.iostreamable-httpv1.0.0Scanned
Mushroom grow profiles, timelines and troubleshooting guides for home growers and smart chambers.
5 tools: 1 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Shroom Labs MCP server can do
The Shroom Labs MCP server is published by shroomlabs.io, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: grow_timeline), but cannot delete data. 4 tools only read.
1 tool brings in text other people can write (search_grow_content).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 1Claude Code: ask
grow_timelineDay by day timeline for growing one mushroom: each stage with its start day, end day and conditions, and the total days from start to harvest.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Day by day timeline for growing one mushroom: each stage with its start day, end day and conditions, and the total days from start to harvest. Use for 'how long does X take to grow'.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_chamber_guideGet Shroom Labs guides for automated mushroom grow chambers: which chambers work ('chambers'), installing free OpenShrooly firmware on a Shrooly chamber ('install'), what happened …No findings
Why it is in this group
- The name "get_chamber_guide" says "get": a word for reading.
Description, as the server wrote it Get Shroom Labs guides for automated mushroom grow chambers: which chambers work ('chambers'), installing free OpenShrooly firmware on a Shrooly chamber ('install'), what happened to the Shrooly app ('what-happened-to-shrooly'), keeping a Terrashroom running ('terrashroom'), and more. Omit topic to list all.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_profileGet the full grow recipe for one mushroom by slug (e.g.No findings
Why it is in this group
- The name "get_profile" says "get": a word for reading.
Description, as the server wrote it Get the full grow recipe for one mushroom by slug (e.g. 'lions-mane', 'pearl-oyster', 'shiitake'): every stage with days, temperature (C and F), humidity, fresh air exchange (fan) and light hours, plus chamber tips and sources.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_profilesList Shroom Labs mushroom grow profiles (species and strains such as lion's mane, pearl oyster, shiitake).No findings
Why it is in this group
- The name "list_profiles" says "list": a word for reading.
Description, as the server wrote it List Shroom Labs mushroom grow profiles (species and strains such as lion's mane, pearl oyster, shiitake). Each has a slug for get_profile, total grow days and a canonical URL. Culinary only by default; set include_off_menu to also list educational Off-menu profiles (always returned with a legal notice).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
search_grow_contentSearch Shroom Labs grow profiles, troubleshooting guides (not pinning, contamination, leggy stems, humidity and fresh air) and blog posts.Reads text others writeNo findings
Why it is in this group
- The name "search_grow_content" says "search": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "search" and "post": it reads posts, which other people can write.
Description, as the server wrote it Search Shroom Labs grow profiles, troubleshooting guides (not pinning, contamination, leggy stems, humidity and fresh air) and blog posts. Returns titles, short descriptions and canonical URLs to cite.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:22 UTC, unchanged since Nov 2, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.shroomlabs.io/mcp: tools/list returned 5 tools to an anonymous client, including grow_timeline (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http shroom-labs https://api.shroomlabs.io/mcpclaude mcp add --transport http shroom-labs https://api.shroomlabs.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__shroom-labs__list_profiles",
"mcp__shroom-labs__get_profile",
"mcp__shroom-labs__search_grow_content",
"mcp__shroom-labs__get_chamber_guide"
],
"ask": [
"mcp__shroom-labs__grow_timeline"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as shroom-labs. Review it before you use it.
Capability tags behind 1 rule
- mcp__shroom-labs__search_grow_content untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.shroomlabs/shroom-labs/verify?hash=11dd83e3e7a3f96cf6a0e9d7238c7878966f39ac4855ccc085841c8ea7f271c6" | jq -e '.changed == false'Pinned hash 11dd83e3e7a3, from Nov 13, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.shroomlabs/shroom-labs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.shroomlabs/shroom-labs)Source: MCP Registry · repository. Synced Nov 1, 2026, 00:17 UTC.
Shroom Labs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Shroom Labs MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Shroom Labs MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Shroom Labs MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Shroom Labs MCP server have?
- 5 tools: 1 write, 4 read. grow_timeline, list_profiles, get_profile, search_grow_content and get_chamber_guide.
Does the Shroom Labs MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Shroom Labs MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Shroom Labs MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.