io.github.rootsbymenda/cannabis-regulatory
REMOTE · CANNABIS-MCP-SERVER.ROOTSBYBENDA.WORKERS.DEV · 2 COMPONENTS
Cannabis compliance: US state testing, INCB, Health Canada, EU precursors. Free.
Last scanned (18 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 4 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared sse, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- HTTPS: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Stability: 0.27 → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 4 Nov 2026 · Probed https://cannabis-mcp-server.rootsbybenda.workers.dev/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rootsbybenda.workers.dev | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 15355523f9dba24913c1d5d4dc380a04 |
| SANs: rootsbybenda.workers.dev, *.rootsbybenda.workers.dev | ||||||
| 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 cannabis-mcp-server.rootsbybenda.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://cannabis-mcp-server.rootsbybenda.workers.dev/sse | HTTP error | 404 | |
| http (plaintext) | http://cannabis-mcp-server.rootsbybenda.workers.dev/sse | Inconclusive | 404 |
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 →
check_cannabis_compliance ~276
Retrieve cannabis product compliance requirements by jurisdiction including all required testing categories, analyte limits, and regulatory sections. Input: US state name or 'Canada' for Health Canada, optional product class (flower, concentrate, edible, topical, extract, oil, dried_cannabis). Returns for US states: all testing categories (pesticide, heavy metal, microbial, solvent, mycotoxin, potency, moisture) with per-analyte action levels, units, and product-type applicability. Returns for Canada: Health Canada cannabis regulation parameters, limit values, units, product class, and regulation section references. Database: 1,942 US state testing requirements + 383 Health Canada cannabis regulations. For cannabis product compliance planning and regulatory gap analysis. Do not use for controlled-substance scheduling (use check_controlled_substance) or broad keyword discovery (use search_cannabis_regulations).
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | yes | Cannabis compliance jurisdiction: a US state name (e.g. 'California') or 'Canada' for Health Canada cannabis regulations. Choose the market where the product will be tested, sold, or assessed. |
| product_class | string | – | Optional cannabis product class for compliance filtering. Use flower, concentrate, edible, topical, extract, oil, or dried_cannabis when requirements differ by product format. |
No output schema declared.
No examples provided.
check_cannabis_testing ~344
Retrieve US state-level cannabis testing limits and action levels for regulatory compliance. Input: US state name (e.g. 'California', 'Colorado'), optional test category (pesticide, heavy_metal, microbial, solvent, mycotoxin, potency, moisture), and optional specific analyte name (e.g. 'lead', 'arsenic', 'Salmonella', 'butane'). Returns: testing categories with analyte names, action levels (pass/fail thresholds), units (ppm, ppb, CFU/g), product class applicability (flower, concentrate, edible), and regulation references. Database: 1,942 state-level testing requirements across all legalized US states. For cannabis laboratory compliance and product testing requirements. Do not use for controlled-substance scheduling (use check_controlled_substance), Health Canada regulations (use check_cannabis_compliance with jurisdiction 'Canada'), or non-cannabis food pesticide MRLs.
| Name | Type | Req | Description |
|---|---|---|---|
| analyte | string | – | Optional specific cannabis testing analyte or contaminant name (e.g. 'lead', 'arsenic', 'Salmonella', 'butane'). Use analyte names to narrow a state/category lookup to one action level. |
| state | string | yes | US state name for cannabis testing-limit lookup (e.g. 'California', 'Colorado', 'Oregon'). Use the state where the cannabis product is tested or sold because action levels vary by jurisdiction. |
| test_category | string | – | Optional cannabis laboratory testing category filter. Use pesticide, heavy_metal, microbial, solvent, mycotoxin, potency, or moisture when the user asks about a specific contaminant or assay class. |
No output schema declared.
No examples provided.
check_controlled_substance ~302
Check international controlled-substance scheduling status across UN, EU, and novel psychoactive substance databases. Input: substance name, cannabinoid, narcotic drug, precursor, NPS name, synonym, or CAS number (e.g. 'cannabis', 'THC', 'morphine', 'pseudoephedrine', '64-17-5'). Returns: UN INCB Yellow List scheduling (narcotic drugs under 1961 Single Convention — schedule, synonyms, formula, conversion ratio, CAS), EU Drug Precursor category (CN code, threshold quantities, license/registration requirements), and EMCDDA/EUDA Novel Psychoactive Substance risk assessment (chemical class, control status, risk assessment year, scheduling decision). Sources: INCB Yellow List (154 narcotic drugs), EU Drug Precursors regulation (46 chemicals), EMCDDA/EUDA NPS risk assessments (41 substances). For controlled substance regulatory compliance and scheduling verification. Do not use for cannabis testing limits (use check_cannabis_testing) or product compliance summaries (use check_cannabis_compliance).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Controlled substance common name, cannabinoid, narcotic drug, precursor chemical, NPS name, synonym, or CAS number (e.g. 'morphine', 'cannabis', '64-17-5'). Use CAS when available for exact matching… |
No output schema declared.
No examples provided.
search_cannabis_regulations ~283
Search across all cannabis and controlled-substance regulatory datasets by keyword for regulatory intelligence discovery. Input: keyword covering jurisdiction, product class, analyte, substance, precursor, or NPS term (e.g. 'THC', 'pesticide', 'heavy metal', 'Salmonella', 'morphine', 'pseudoephedrine'). Returns: cross-dataset matches from US state cannabis testing limits (grouped by state), UN INCB scheduling (narcotic drugs), Health Canada cannabis regulations, and EU Drug Precursors — each with dataset labels, jurisdictions, substance/analyte names, limits, and regulatory references. Database: 1,942 testing limits + 154 INCB substances + 383 Health Canada records + 46 EU precursors + 41 EMCDDA NPS. For cannabis regulatory research and cross-jurisdictional analysis. Do not use when exact state, jurisdiction, or substance is known (use the specific compliance or scheduling tools).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Cannabis regulatory keyword, jurisdiction, product class, analyte, controlled substance, precursor, or NPS term (e.g. 'THC', 'pesticide', 'heavy metal', 'Salmonella', 'morphine', 'pseudoephedrine').… |
No output schema declared.
No examples provided.
How do I install the io.github.rootsbymenda/cannabis-regulatory MCP server?
io.github.rootsbymenda/cannabis-regulatory is a hosted endpoint at https://cannabis-mcp-server.rootsbybenda.workers.dev/sse, 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 · cannabis-mcp-server.rootsbybenda.workers.dev
claude mcp add --transport http rootsbymenda-cannabis-regulatory 'https://cannabis-mcp-server.rootsbybenda.workers.dev/sse'
What is the io.github.rootsbymenda/cannabis-regulatory MCP server?
io.github.rootsbymenda/cannabis-regulatory is an MCP server listed in the public MCP registry as io.github.rootsbymenda/cannabis-regulatory. Cannabis compliance: US state testing, INCB, Health Canada, EU precursors. Free. This page covers its hosted endpoint (https://cannabis-mcp-server.rootsbybenda.workers.dev/sse).
Is the io.github.rootsbymenda/cannabis-regulatory MCP server safe to use?
io.github.rootsbymenda/cannabis-regulatory scores 18 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 io.github.rootsbymenda/cannabis-regulatory MCP server expose?
io.github.rootsbymenda/cannabis-regulatory exposes 4 tools: check_cannabis_testing, check_controlled_substance, check_cannabis_compliance, search_cannabis_regulations. Their descriptions and schemas cost roughly 1,205 tokens of context every time the server is loaded.
Does the io.github.rootsbymenda/cannabis-regulatory MCP server require authentication?
Its publisher declares no required credentials for io.github.rootsbymenda/cannabis-regulatory. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.rootsbymenda/cannabis-regulatory MCP server still maintained?
io.github.rootsbymenda/cannabis-regulatory is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.