USDA NOP organic compliance checks — operation websites vs live OID certificate data.
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 Website: organicwebchecker.com Organic Web Checker (OWC) compares products marketed as organic on a…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
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 Website: organicwebchecker.com 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: ✅…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.