Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lowtoxgear Scanner

REMOTE · MCP-SCAN.LOWTOXGEAR.COM

Australian ingredient scanner MCP — 21k+ AU products, 237 chemical rules, 17 condition tags.

0 this week 71 Trust /100

Last scanned (23 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 531 tokens (~106/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 63% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp-scan.lowtoxgear.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lowtoxgear.com CN=WE1,O=Google Trust Services,C=US 12 Nov 2026 10 Feb 2027 ECDSA 256 ECDSA-SHA256 63601a787aaefbee1331ab85573d4a8d
SANs: lowtoxgear.com, mcp-scan.lowtoxgear.com, *.mcp-scan.lowtoxgear.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp-scan.lowtoxgear.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
lowtoxgear.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp-scan.lowtoxgear.com/mcp Verified 200
http (plaintext) http://mcp-scan.lowtoxgear.com/mcp Inconclusive 404
MCP tools · 5 exposed · ~436 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_catalog_stats ~38

Return the size of the indexed Australian product catalogue — total, food, beauty, and total scans performed. Useful to set user expectations on coverage.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_magnet_samples ~60

List the six condition-specific magnet guides with sample product images. Each guide is a strict-clean shortlist (eczema-safe personal care, clean shampoos AU, mineral-only sunscreens AU, pregnancy-safe beauty, fragrance-free essentials, snacks without artificial dyes).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_resources ~53

URL templates for chained queries — product page, per-product alternatives, category alternatives, magnet guides, OG images, and full LLM-ready documentation. Use to give the user/agent canonical links they can fetch or render directly.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scan_barcode ~178

Look up an Australian product by barcode (EAN/UPC/JAN, 6–14 digits) and get full chemical-safety analysis. Returns the product info (if found) plus an array of flagged ingredients with severity (red/amber), the matching chemical rule, source citation, and condition-specific notes. Optional `conditions` array escalates flags for users with chronic conditions: mcas, eczema, pcos, fertility, pregnancy, fibromyalgia, pots, ibs, hashimotos, fragrance, autism, adhd, asthma, autoimmune, endometriosis, lyme, chronic-fatigue.

NameTypeReqDescription
barcodestringyes6–14 digit barcode (EAN/UPC/JAN). Common: 13-digit EAN.
conditionsarray–Optional list of personal condition tags to escalate flags for. Multiple supported.

No output schema declared.

No examples provided.

submit_missing_product ~107

Request that a product be added to the Low Tox Scanner index. Useful when scan_barcode returns product_found: false. Submission goes to a moderation queue.

NameTypeReqDescription
barcodestringyes6–14 digit barcode
brandstring––
categorystring––
ingredients_textstring–Comma-separated ingredient list copied from the product packaging
notesstring–Freeform context for the moderator
product_namestring––

No output schema declared.

No examples provided.

Install

How do I install the Lowtoxgear Scanner MCP server?

Lowtoxgear Scanner is a hosted endpoint at https://mcp-scan.lowtoxgear.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp-scan.lowtoxgear.com

# add to Claude Code
claude mcp add --transport http com-lowtoxgear-scanner 'https://mcp-scan.lowtoxgear.com/mcp'
Common questions

What is the Lowtoxgear Scanner MCP server?

Lowtoxgear Scanner is an MCP server listed in the public MCP registry as com.lowtoxgear/scanner. Australian ingredient scanner MCP, 21k+ AU products, 237 chemical rules, 17 condition tags. This page covers its hosted endpoint (https://mcp-scan.lowtoxgear.com/mcp).

Is the Lowtoxgear Scanner MCP server safe to use?

Lowtoxgear Scanner scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Lowtoxgear Scanner MCP server expose?

Lowtoxgear Scanner exposes 5 tools: scan_barcode, get_catalog_stats, get_magnet_samples, submit_missing_product, get_resources. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.

Does the Lowtoxgear Scanner MCP server require authentication?

No. We connected to Lowtoxgear Scanner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Lowtoxgear Scanner MCP server still maintained?

Lowtoxgear Scanner is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Lowtoxgear Scanner MCP server?

VerifyMCP ran 11 checks on Lowtoxgear Scanner, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Lowtoxgear Scanner: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.