Lowtoxgear Scanner

Lowtoxgear — MCP server suite

Two MCP servers for the Lowtoxgear ecosystem. Both live, no-auth, no API key needed — paste a URL into Claude.ai → Settings → Connectors, or call directly via JSON-RPC 2.0 POST.

Both registered under the com.lowtoxgear/* namespace (DNS-verified via lowtoxgear.com) in the Anthropic MCP Registry.

What they do

Lowtoxgear Storefront — shop the catalogue

The Lowtoxgear brand is an Australian low-tox lifestyle e-commerce store spanning four collections:

• Certified Activewear — clothing built without PFAS, fluorocarbons, or synthetic finishes
• Clean Supplements — Australian-sourced supplement products with third-party testing
• GOTS Certified — Global Organic Textile Standard apparel
• Low-Tox Home Products — household items audited for clean ingredients

The storefront MCP exposes the Shopify public catalogue with one brand-specific extension: filter_by_certification lets agents query by tags like GOTS, OEKO-TEX, PFAS-free, etc.

Lowtoxgear Scanner — analyse anything by barcode

The Scanner is an independent Australian ingredient scanner for any consumer product. Live at scan.lowtoxgear.com:

• 21,000+ Australian product pages indexed by barcode (EAN/UPC/JAN)
• 237 source-cited chemical rules — fragrance allergens, EU-banned additives, EDCs, phthalates, PFAS, formaldehyde releasers, parabens, preservatives, and more
• 17 condition-specific flag escalations — MCAS, eczema, PCOS, fertility, pregnancy, fibromyalgia, POTS, IBS, Hashimoto's, fragrance sensitivity, autism, ADHD, asthma, autoimmune, endometriosis, lyme, chronic fatigue
• Six magnet guides of strict-clean shortlists by condition (eczema-safe personal care, mineral-only sunscreens, pregnancy-safe beauty, clean shampoos, etc.)
• No sponsored placement — independent, source-cited

The Scanner MCP is a thin wrapper around the existing scanner backend — it exposes the same data via the MCP JSON-RPC protocol so agents can query it programmatically.

Install (both)

Claude Desktop / Claude Code / Cursor

{
  "mcpServers": {
    "lowtoxgear-storefront": { "url": "https://mcp.lowtoxgear.com/mcp" },
    "lowtoxgear-scanner":    { "url": "https://mcp-scan.lowtoxgear.com/mcp" }
  }
}

ChatGPT / Claude.ai Custom Connectors

Settings → Connectors → Add custom connector → paste either URL.

Test from a terminal

# Scan a barcode
curl -sS https://mcp-scan.lowtoxgear.com/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"scan_barcode","arguments":{"barcode":"9300605000018"}}}'

# Search the storefront
curl -sS https://mcp.lowtoxgear.com/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"search_products","arguments":{"query":"GOTS organic"}}}'

Cross-discovery

Both servers reference each other in their initialize and get_* responses:

• The Storefront's get_policies returns a pointer to the Scanner (for chemical-safety analysis of items found in the catalogue).
• The Scanner's get_resources returns a pointer to the Storefront (for shopping the cleanest-in-class).

This lets agents chain queries naturally: scan a barcode → if flagged, query the storefront for a cleaner alternative.

Architecture

                       ┌──────────────────────────┐
                       │  AI agent (Claude / etc) │
                       └────┬───────────────┬─────┘
                            │ JSON-RPC 2.0  │ JSON-RPC 2.0
                            ▼               ▼
              mcp.lowtoxgear.com/mcp   mcp-scan.lowtoxgear.com/mcp
              (storefront MCP Worker)  (scanner MCP Worker)
                            │               │
                            │ Shopify       │ scan.lowtoxgear.com/api/*
                            │ public JSON   │ (existing scanner web app)
                            ▼               ▼
                      lowtoxgear.com   scan.lowtoxgear.com
                      (Shopify store)  (D1: 21k AU products,
                                        237 chemical rules)

Both MCP Workers run on Cloudflare Workers with their own custom domains. The Scanner backend (D1 database, chemical-rule engine, OCR ingestion) lives in a separate Worker we don't modify.

Publishing to the MCP Registry

See PUBLISHING.md — one DNS verification on lowtoxgear.com unlocks both manifests under com.lowtoxgear/*.

License

MIT — see LICENSE.

Built by Lowtoxgear · Source for scanner data is independent + source-cited · Contact: [email protected]