io.github.healersfind-alt/organic-web-checker
USDA NOP organic compliance checks — operation websites vs live OID certificate data.
What can you do with io.github.healersfind-alt/organic-web-checker?
- ✅ 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
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http organic-web-checker 'https://www.organicwebchecker.com/mcp' --header 'X-API-Key: <API key — issue one at https://www.organicwebchecker.com/api>'{
"mcpServers": {
"organic-web-checker": {
"type": "http",
"url": "https://www.organicwebchecker.com/mcp",
"headers": {
"X-API-Key": "<API key — issue one at https://www.organicwebchecker.com/api>"
}
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
operation_name | string | yes | Operation name exactly as listed in USDA OID |
website_url | string | yes | Full URL of the operation's website |
force_fresh | boolean | no | Bypass 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
operation_name | string | yes | Operation name as listed in USDA OID |
Returns: certified products, certifier, status, location, scopes.
Connect
Claude Desktop / Cursor / other MCP clients
{
"mcpServers": {
"organic-web-checker": {
"url": "https://www.organicwebchecker.com/mcp",
"headers": {
"X-API-Key": "owc_live_..."
}
}
}
}Raw JSON-RPC
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
- Create an account at organicwebchecker.com
- Visit organicwebchecker.com/api to generate a key (prefix
owc_live_) - 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: hello@organicwebchecker.com
Frequently asked questions
What is io.github.healersfind-alt/organic-web-checker?
USDA NOP organic compliance checks — operation websites vs live OID certificate data.
How do I install io.github.healersfind-alt/organic-web-checker?
It runs as a remote server. In Claude Code: claude mcp add --transport http organic-web-checker 'https://www.organicwebchecker.com/mcp' --header 'X-API-Key: <API key — issue one at https://www.organicwebchecker.com/api>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.healersfind-alt/organic-web-checker need an API key?
Yes. It expects X-API-Key, which you set in its configuration.
Is io.github.healersfind-alt/organic-web-checker open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.healersfind-alt/organic-web-checker?
It is published by healersfind-alt. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.