io.github.rootsbymenda/cannabis-regulatory
REMOTE · CANNABIS-MCP-SERVER.ROOTSBYBENDA.WORKERS.DEV · 2 COMPONENTS · SCANNED AUG 3
Cannabis compliance: US state testing, INCB, Health Canada, EU precursors. Free.
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 →
Endpoint Security63
- 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1205 tokens (~301/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · cannabis-mcp-server.rootsbybenda.workers.dev
claude mcp add --transport http rootsbymenda-cannabis-regulatory https://cannabis-mcp-server.rootsbybenda.workers.dev/sse
[mcp_servers.rootsbymenda-cannabis-regulatory] url = "https://cannabis-mcp-server.rootsbybenda.workers.dev/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rootsbymenda-cannabis-regulatory": {
"type": "remote",
"url": "https://cannabis-mcp-server.rootsbybenda.workers.dev/sse",
"enabled": true
}
}
} openclaw mcp add rootsbymenda-cannabis-regulatory --url https://cannabis-mcp-server.rootsbybenda.workers.dev/sse --transport streamable-http
mcp_servers:
rootsbymenda-cannabis-regulatory:
url: "https://cannabis-mcp-server.rootsbybenda.workers.dev/sse" {
"mcpServers": {
"rootsbymenda-cannabis-regulatory": {
"type": "http",
"url": "https://cannabis-mcp-server.rootsbybenda.workers.dev/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- 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 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 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.
- 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
- 26 Jul 26 57
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 3 Aug 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 | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | a19ebb28df33c3640efc0c208730db7e |
| 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 |
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 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 | 404 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://cannabis-mcp-server.rootsbybenda.workers.dev/sse | Verified | 200 | |
| http (plaintext) | http://cannabis-mcp-server.rootsbybenda.workers.dev/sse | Served over HTTP | 200 |
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.
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.