Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

mechoulam.de Cannabis Evidence Register

REMOTE · MECHOULAM.DE · SCANNED SEP 24

GRADE-rated clinical evidence on cannabis as medicine (DE/EN). Search and cite studies.

Available components

+3 this week 79 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 399 tokens (~79/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 Management93
  • Stability observed for 28 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
  • Structured output schemas are declared (40% of tools); any adoption earns full credit.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
Install

How do I install the mechoulam.de Cannabis Evidence Register MCP server?

mechoulam.de Cannabis Evidence Register is a hosted endpoint at https://mechoulam.de/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 · mechoulam.de

# add to Claude Code
claude mcp add --transport http de-mechoulam-cannabis-evidence 'https://mechoulam.de/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "de-mechoulam-cannabis-evidence": {
      "url": "https://mechoulam.de/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "de-mechoulam-cannabis-evidence": {
      "type": "http",
      "url": "https://mechoulam.de/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.de-mechoulam-cannabis-evidence]
url = "https://mechoulam.de/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-mechoulam-cannabis-evidence": {
      "type": "remote",
      "url": "https://mechoulam.de/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add de-mechoulam-cannabis-evidence --url 'https://mechoulam.de/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  de-mechoulam-cannabis-evidence:
    url: "https://mechoulam.de/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "de-mechoulam-cannabis-evidence": {
      "Transport": "http",
      "Url": "https://mechoulam.de/mcp"
    }
  }
}
# add to Vellum
assistant mcp add de-mechoulam-cannabis-evidence -t streamable-http -u 'https://mechoulam.de/mcp'
// mcp.json
{
  "mcpServers": {
    "de-mechoulam-cannabis-evidence": {
      "type": "http",
      "url": "https://mechoulam.de/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +2
    • Schema quality: good → excellent functional
Diagnostics

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 24 Sept 2026 · Probed https://mechoulam.de/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mechoulam.de CN=WE1,O=Google Trust Services,C=US 8 Aug 2026 6 Nov 2026 ECDSA 256 ECDSA-SHA256 dacf54cd08a97e2c0ec4274887fb6ec1
SANs: mechoulam.de, *.mechoulam.de
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 mechoulam.de. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
de. present 26755 8 Verified
mechoulam.de. 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 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data:; connect-src 'self'; form-action 'self'; frame-ancestors 'self'; base-uri 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=(), fullscreen=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mechoulam.de/mcp Verified 200
http (plaintext) http://mechoulam.de/mcp HTTPS enforced 301 https://mechoulam.de/mcp
MCP tools · 5 exposed · ~356 tokens

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 →

Tool Tokens
fetch ~58

Fetch one full record by the id returned from search: the GRADE-rated evidence summary of an indication, or one study with its per-indication verdicts. Includes the source URL to cite.

NameTypeReqDescription
idstringyesId from a search result
NameTypeReqDescription
idstringyes
metadataobject
textstringyes
titlestringyes
urlstringyes

No examples provided.

get_indication ~84

Get the GRADE-rated evidence summary for one indication (reviewed studies only). Use a slug from list_indications.

NameTypeReqDescription
langstringLanguage of the answer and of the cited source URL. 'de' (default) cites mechoulam.de/..., 'en' cites mechoulam.de/en/...
slugstringyesIndication slug

No output schema declared.

No examples provided.

get_study ~76

Get one study by DOI with its per-indication verdicts (reviewed-only).

NameTypeReqDescription
doistringyesStudy DOI
langstringLanguage of the answer and of the cited source URL. 'de' (default) cites mechoulam.de/..., 'en' cites mechoulam.de/en/...

No output schema declared.

No examples provided.

list_indications ~76

List all indications on mechoulam.de with slug, name, category, count of reviewed studies and the citable page URL.

NameTypeReqDescription
langstringLanguage of the answer and of the cited source URL. 'de' (default) cites mechoulam.de/..., 'en' cites mechoulam.de/en/...

No output schema declared.

No examples provided.

search ~62

Search the mechoulam.de cannabis-medicine evidence register by free text (indication, condition, drug, study title, author). Returns indications and reviewed studies with citable URLs. Answer language follows the language of the query.

NameTypeReqDescription
querystringyesSearch query
NameTypeReqDescription
resultsarrayyes

No examples provided.

Common questions

What is the mechoulam.de Cannabis Evidence Register MCP server?

mechoulam.de Cannabis Evidence Register is an MCP server listed in the public MCP registry as de.mechoulam/cannabis-evidence. GRADE-rated clinical evidence on cannabis as medicine (DE/EN). Search and cite studies. This page covers its hosted endpoint (https://mechoulam.de/mcp).

Is the mechoulam.de Cannabis Evidence Register MCP server safe to use?

mechoulam.de Cannabis Evidence Register scores 79 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 mechoulam.de Cannabis Evidence Register MCP server expose?

mechoulam.de Cannabis Evidence Register exposes 5 tools: search, fetch, list_indications, get_indication, get_study. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.

Does the mechoulam.de Cannabis Evidence Register MCP server require authentication?

No. We connected to mechoulam.de Cannabis Evidence Register without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the mechoulam.de Cannabis Evidence Register MCP server still maintained?

mechoulam.de Cannabis Evidence Register is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.