Organic Web Checker

io.github.healersfind-altPublished by GitHub account healersfind-altv1.0.0Updated Oct 24, 2026

USDA NOP organic compliance checks — operation websites vs live OID certificate data.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that compares a certified organic operation's website against live USDA OID certificate data and reports verified, flagged and caution items.

What you can do
  • Run a full website-versus-OID compliance check for a named operation and website, returning a structured report of verified, flagged, caution and marketing items with cert metadata and item-level URLs.
  • Fetch an operation's current USDA OID certificate (certified products, certifier, status, location, scopes) without running a website check.
  • Optionally bypass the 24-hour OID cache to pull fresh data from USDA.
When to use it
Useful for organic certifying agents, compliance consultants and certified operations doing self-review who want a quick cross-check of organic product claims on a public website against the operation's certificate. It is decision-support only, so flagged items still need manual review.
Requirements
A remote MCP endpoint; no local runtime or package. An API key created through an account on the provider's site, sent in the X-API-Key header. Credits purchased for website checks, and network access to the provider and USDA data.
Before you install
The X-API-Key header is a secret and should be kept out of shared configs. Each successful compliance check costs 1 credit, so usage spends purchased credits; certificate lookups are free. The server sends the operation name and website URL to the provider and pulls public USDA data. Results are not a compliance determination and require manual review.

Installation

In SourceWeft

  1. Open Organic Web Checker in the dashboard and add it to a workspace.
  2. Connect X-API-Key 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.github.healersfind-alt%2Forganic-web-checker/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.

{
  "mcpServers": {
    "organic-web-checker": {
      "type": "http",
      "url": "https://www.organicwebchecker.com/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

Organic Web Checker — MCP Server

Cross-reference certified organic operation websites against live USDA Organic Integrity Database (OID) certificate data. Identifies organic product representations that may not be on the certificate of organic operation.

Status: Live · Remote HTTP MCP server · JSON-RPC 2.0 · API key required

  • Endpoint: https://www.organicwebchecker.com/mcp
  • Website: organicwebchecker.com
  • Protocol: MCP 2024-11-05

What it does

Organic Web Checker (OWC) compares products marketed as organic on a certified operation's public website against the operation's live USDA OID certificate. It surfaces:

  • ✅ Verified — product representation found on the cert
  • 🔴 Flagged — organic representation with no matching cert item
  • 🟡 Caution — close name variation, processing-form question, or grouped-scope match requiring review by the certifying agent

Built for organic certifying agents, compliance consultants, and certified operations doing self-review. Decision-support tool — not a compliance determination. Manual review of flagged items is required.

Tools

check_organic_compliance

Runs a full website-vs-OID compliance check and returns a structured report.

ParameterTypeRequiredDescription
operation_namestringyesOperation name exactly as listed in USDA OID
website_urlstringyesFull URL of the operation's website
force_freshbooleannoBypass 24-hour OID cache and pull live from USDA (default false)

Returns: structured JSON report with verified, flagged, caution, marketing lists, cert metadata, and item-level URLs.

Cost: 1 credit per successful run.

get_oid_certificate

Fetches an operation's current USDA OID certificate without running a website check.

ParameterTypeRequiredDescription
operation_namestringyesOperation name as listed in USDA OID

Returns: certified products, certifier, status, location, scopes.

Connect

Claude Desktop / Cursor / other MCP clients

json
{  "mcpServers": {    "organic-web-checker": {      "url": "https://www.organicwebchecker.com/mcp",      "headers": {        "X-API-Key": "owc_live_..."      }    }  }}

Raw JSON-RPC

bash
curl -X POST https://www.organicwebchecker.com/mcp \  -H "Content-Type: application/json" \  -H "X-API-Key: owc_live_..." \  -d '{    "jsonrpc": "2.0",    "id": 1,    "method": "tools/call",    "params": {      "name": "check_organic_compliance",      "arguments": {        "operation_name": "Example Organic Farm LLC",        "website_url": "https://example.com"      }    }  }'

The server implements initialize, tools/list, and tools/call. Tools are discovered automatically by MCP-compatible clients on connect.

Get an API key

  1. Create an account at organicwebchecker.com
  2. Visit organicwebchecker.com/api to generate a key (prefix owc_live_)
  3. Buy credits at organicwebchecker.com/pricing (or use a promo code if you have one)

Each successful check_organic_compliance call deducts 1 credit. get_oid_certificate is free of credit cost. Rate limit: 60 checks/hour per key.

Regulatory context

OWC checks public-facing organic representations against publicly available OID certificate information. It acknowledges:

  • Retail exemption — 7 CFR §205.101(a)(2)
  • Handler/OSP scope — 7 CFR §205.201; detailed product coverage held by the certifying agent
  • SOE rule (March 19, 2024) — brokers, traders, importers, exporters now require handler certification

Results are decision-support only. Final compliance determinations are made by certifying agents.

License

This repository (server metadata and documentation) is licensed under the MIT License — see LICENSE.

The Organic Web Checker service itself is proprietary software. Method protected by U.S. provisional patent application No. 64053105.

Operator

Organic Web Checker LLC (Florida) Inventor / Founder: Christian Strickland Contact: [email protected]

Source: README.md at commit 9449ee5

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.