Organic Web Checker

Name: Organic Web Checker
Author: healersfind-alt

by healersfind-altcommunityv1.0.0

This MCP server compares an operation’s public website claims of organic products against the live USDA Organic Integrity Database certificate for that operation. It returns a compliance-oriented report marking items as verified, flagged, or caution for manual review.

From the registry: USDA NOP organic compliance checks — operation websites vs live OID certificate data.

GitHub Repository Website

Install & configure

Prerequisites

required
Create an Organic Web Checker account
Sign up for an account to access the API and generate credentials.
https://www.organicwebchecker.com/
required
Generate an API key
Create an API key from the Organic Web Checker API page. The README indicates keys use the prefix `owc_live_`.
https://www.organicwebchecker.com/api
optional
Buy credits
Purchase credits or use a promo code. Each successful `check_organic_compliance` call costs 1 credit; `get_oid_certificate` does not consume credits.
https://www.organicwebchecker.com/pricing

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `organic-web-checker` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Create an Organic Web Checker account** — Sign up for an account to access the API and generate credentials. (https://www.organicwebchecker.com/)
- **Generate an API key** — Create an API key from the Organic Web Checker API page. The README indicates keys use the prefix `owc_live_`. (https://www.organicwebchecker.com/api)

Optional prerequisites:
- Buy credits — Purchase credits or use a promo code. Each successful `check_organic_compliance` call costs 1 credit; `get_oid_certificate` does not consume credits. (https://www.organicwebchecker.com/pricing)

Canonical MCP server config (HTTP transport):
- url: `https://www.organicwebchecker.com/mcp`
- headers:
  - `X-API-Key`: `<your-api-key>`

Note: Remote HTTP MCP server using JSON-RPC 2.0. The server supports `initialize`, `tools/list`, and `tools/call`. API key is required. Rate limit is 60 checks/hour per key.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: Remote HTTP MCP server using JSON-RPC 2.0. The server supports `initialize`, `tools/list`, and `tools/call`. API key is required. Rate limit is 60 checks/hour per key.