Shroom Labs
REMOTE · API.SHROOMLABS.IO
Mushroom grow profiles, timelines and troubleshooting guides for home growers and smart chambers.
Available components
Last scanned (8 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 523 tokens (~104/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 68
First indexed and scored.
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 5 Nov 2026 · Probed https://api.shroomlabs.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shroomlabs.io | CN=WE1,O=Google Trust Services,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a53d11519a2cb2d50e68417178a0daba |
| SANs: shroomlabs.io, api.shroomlabs.io, *.api.shroomlabs.io | ||||||
| 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 api.shroomlabs.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| shroomlabs.io. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.shroomlabs.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.shroomlabs.io/mcp | Inconclusive | 405 |
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 →
get_chamber_guide Get a grow chamber guide ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Which guide. Omit to list all topics. |
No output schema declared.
No examples provided.
get_profile Get a mushroom grow profile ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Profile slug from list_profiles, e.g. 'lions-mane'. A plain name like 'Lion's Mane' also works. |
No output schema declared.
No examples provided.
grow_timeline Mushroom grow timeline ~70
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Profile slug or name, e.g. 'pearl-oyster'. |
No output schema declared.
No examples provided.
list_profiles List mushroom grow profiles ~117
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).
| Name | Type | Req | Description |
|---|---|---|---|
| include_off_menu | boolean | – | Also include educational Off-menu profiles. Default false. |
| query | string | – | Optional filter on name, species or tag, e.g. 'oyster' or 'beginner'. |
No output schema declared.
No examples provided.
search_grow_content Search mushroom growing guides ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results. Default 8. |
| query | string | yes | Words to search for, e.g. 'mushrooms not pinning' or 'oyster kit'. |
No output schema declared.
No examples provided.
How do I install the Shroom Labs MCP server?
Shroom Labs is a hosted endpoint at https://api.shroomlabs.io/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 · api.shroomlabs.io
claude mcp add --transport http io-shroomlabs-shroom-labs 'https://api.shroomlabs.io/mcp'
What is the Shroom Labs MCP server?
Shroom Labs is an MCP server listed in the public MCP registry as io.shroomlabs/shroom-labs. Mushroom grow profiles, timelines and troubleshooting guides for home growers and smart chambers. This page covers its hosted endpoint (https://api.shroomlabs.io/mcp).
Is the Shroom Labs MCP server safe to use?
Shroom Labs scores 70 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 Shroom Labs MCP server expose?
Shroom Labs exposes 5 tools: list_profiles, get_profile, search_grow_content, get_chamber_guide, grow_timeline. Their descriptions and schemas cost roughly 480 tokens of context every time the server is loaded.
Does the Shroom Labs MCP server require authentication?
No. We connected to Shroom Labs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Shroom Labs MCP server still maintained?
Shroom Labs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.