HempData

io.hempdataPublished by hempdata.ioOfficial publisherv0.2.0Updated Oct 24, 2026

Verified hemp & cannabinoid regulatory data for all 50 US states + DC. Free key at hempdata.io.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server giving an assistant access to verified hemp and cannabinoid regulatory data for all 50 US states plus DC.

What you can do
  • Look up hemp and cannabinoid regulatory information by US state, including Washington DC.
  • Retrieve verified compliance data covering all 50 states.
  • Answer regulatory questions for the states a product or business operates in.
  • No individual tools are documented, so the exact queries available are not specified.
When to use it
Useful when an assistant needs to answer questions about US state-level hemp or cannabinoid rules, such as checking compliance requirements across states or comparing regulations before a product launch.
Requirements
A remote endpoint at mcp.hempdata.io over streamable HTTP; no local install. OAuth authentication is required, with an Authorization header carrying a Bearer HempData API key; a free tier key is available from the provider's pricing page.
Before you install
The server requires an API key sent in the Authorization header, so treat it as a secret. Paid tiers may apply beyond the free tier. The data is regulatory reference material, not legal advice, and should be verified before relying on it for compliance decisions.

Installation

In SourceWeft

  1. Open HempData in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.hempdata%2Fhempdata/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "hempdata": {
      "type": "http",
      "url": "https://mcp.hempdata.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.2.0LatestSep 17, 2026
  2. v0.1.0Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.