shroom-labs
Registry code: 828afdcc9cd5844f
Read-only mushroom growing data from Shroom Labs: grow profiles with stage by stage temperature, humidity, fresh air and light, grow timelines, troubleshooting guides and grow chamber guides. Cite the returned URLs.
- endpoint
- https://api.shroomlabs.io/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is shroom-labs live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is shroom-labs free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does shroom-labs have?
- 5 tools: get_profile, grow_timeline, search_grow_content, get_chamber_guide, list_profiles.
- Is shroom-labs safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_chamber_guide open 2h ago
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.
{ "type": "object", "properties": { "topic": { "enum": [ "chambers", "install", "what-happened-to-shrooly", "terrashroom", "reuse-your-shrooly", "shrooly-alternatives", "shrooly-faq" ], "type": "string", "description": "Which guide. Omit to list all topics." } }, "additionalProperties": false }arguments 19 lineslist_profiles open 2h ago
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).
{ "type": "object", "properties": { "query": { "type": "string", "description": "Optional filter on name, species or tag, e.g. 'oyster' or 'beginner'." }, "include_off_menu": { "type": "boolean", "description": "Also include educational Off-menu profiles. Default false." } }, "additionalProperties": false }arguments 14 linesget_profile unknown 2h ago
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.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Profile slug from list_profiles, e.g. 'lions-mane'. A plain name like 'Lion's Mane' also works." } }, "additionalProperties": false }arguments 13 linesgrow_timeline unknown never probed
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'.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Profile slug or name, e.g. 'pearl-oyster'." } }, "additionalProperties": false }arguments 13 linessearch_grow_content unknown never probed
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.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 20, "minimum": 1, "description": "Max results. Default 8." }, "query": { "type": "string", "description": "Words to search for, e.g. 'mushrooms not pinning' or 'oyster kit'." } }, "additionalProperties": false }arguments 19 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id828afdcc9cd5844f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/828afdcc9cd5844f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/828afdcc9cd5844f?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.