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.

Channel3 Shopping

REMOTE · MCP.TRYCHANNEL3.COM · SCANNED SEP 21

Shopping search across 100M+ products, with every retailer's offer and live price in one place.

0 this week 86 Trust /100
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 Security77
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 908 tokens (~129/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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
  • 57% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the Channel3 Shopping MCP server?

Channel3 Shopping is a hosted endpoint at https://mcp.trychannel3.com/, 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.trychannel3.com

# add to Claude Code
claude mcp add --transport http com-trychannel3-shopping 'https://mcp.trychannel3.com/'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-trychannel3-shopping": {
      "url": "https://mcp.trychannel3.com/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-trychannel3-shopping": {
      "type": "http",
      "url": "https://mcp.trychannel3.com/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-trychannel3-shopping]
url = "https://mcp.trychannel3.com/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-trychannel3-shopping": {
      "type": "remote",
      "url": "https://mcp.trychannel3.com/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-trychannel3-shopping --url 'https://mcp.trychannel3.com/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-trychannel3-shopping:
    url: "https://mcp.trychannel3.com/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-trychannel3-shopping": {
      "Transport": "http",
      "Url": "https://mcp.trychannel3.com/"
    }
  }
}
# add to Vellum
assistant mcp add com-trychannel3-shopping -t streamable-http -u 'https://mcp.trychannel3.com/'
// mcp.json
{
  "mcpServers": {
    "com-trychannel3-shopping": {
      "type": "http",
      "url": "https://mcp.trychannel3.com/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 4 Sept 26 0
    • Stability: 0.97 → pass security
  • 3 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 +1
    • 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 +1
    • Tool coverage: 68% → 57% functional
    • “browse_products” added an optional parameter “device_id” cosmetic
    • “get_details” added an optional parameter “device_id” cosmetic
    • “get_price_history” added an optional parameter “device_id” cosmetic
    • “get_similar” added an optional parameter “device_id” cosmetic
  • 18 Aug 26 0
    • “get_details” added an optional parameter “selected_options” cosmetic
    • “get_price_history” added an optional parameter “selected_options” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

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 Sept 2026 · Probed https://mcp.trychannel3.com/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=trychannel3.com CN=WE1,O=Google Trust Services,C=US 3 Aug 2026 1 Nov 2026 ECDSA 256 ECDSA-SHA256 44125acf7f93c01138c5c25137f608d
SANs: trychannel3.com, mcp.trychannel3.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 secure

Validation of mcp.trychannel3.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
trychannel3.com. present 2371 13 Verified
mcp.trychannel3.com. Verified address RRset verified with the apex keys
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.trychannel3.com/ Verified 200
http (plaintext) http://mcp.trychannel3.com/ HTTPS enforced 301 https://mcp.trychannel3.com/
MCP tools · 6 exposed · ~786 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
browse_products ~149

Search and page through products for the storefront UI.

NameTypeReqDescription
device_idstring
image_urlstringPublic image URL for visual search. Combine with `query` for text + image.
limitinteger
page_tokenstringToken from a previous response's next_page_token.
querystringOne product type and its constraints in natural language (brand, color, material, size, price, gender). Good: "red leather jacket under $200"; "leather golf glove under $40". Bad: "gift ideas for dad…
thread_idstring
NameTypeReqDescription
next_page_tokenstring|nullyes
productsarrayyes

No examples provided.

get_details ~72

Fetch a product with live offers, for the storefront UI.

NameTypeReqDescription
device_idstring
product_idstringyesCanonical product ID.
selected_optionsobjectVariant configuration as `{ optionName: label }` for re-resolving offers.
thread_idstring
NameTypeReqDescription
productobjectyes

No examples provided.

get_price_history ~76

Fetch 30-day price history for a product, for the storefront UI.

NameTypeReqDescription
device_idstring
product_idstringyesCanonical product ID.
selected_optionsobjectVariant configuration as `{ optionName: label }` for re-resolving offers.
thread_idstring
NameTypeReqDescription
canonical_product_idstringyes
historyarrayyes
statisticsyes

No examples provided.

get_products ~175

Get full product data (offers, description, attributes, images) by product ID from a search result, or by retailer URL. Pass several IDs in one call to compare. Use search_products to find products. Returns details in the storefront UI. The result includes a `thread_id`. You MUST include it unchanged as the `thread_id` parameter on every subsequent Channel3 tool call in this conversation — including searches for new, unrelated products. Never omit it once you have one.

NameTypeReqDescription
product_idsarrayyesProducts to fetch in parallel.
thread_idstringConversation thread ID. Omit ONLY on the very first Channel3 call of a conversation. From then on, always pass the `thread_id` from the most recent Channel3 result, unchanged — even when the new call…
NameTypeReqDescription
as_ofstringyesISO timestamp of when this result was produced; prices are live as of this moment.
productsarrayyes
server_originstringOrigin of this MCP server; the storefront UI posts analytics events here.
session_idstringPostHog MCP session ID for analytics correlation.
thread_idstringyesConversation thread ID. Pass it back unchanged as `thread_id` on every follow-up call in this conversation.
unresolvedarray

No examples provided.

get_similar ~62

Find products similar to a given product, for the storefront UI.

NameTypeReqDescription
device_idstring
limitinteger
product_idstringyesCanonical product ID to find similar products for.
thread_idstring
NameTypeReqDescription
next_page_tokenstring|nullyes
productsarrayyes

No examples provided.

search_products ~252

Search 100M+ products across thousands of retailers for one product type. Call once for each distinct product type, and send independent calls together. Put relevant constraints in `query`. Returns up to 8 product cards plus structured product data. The result includes a `thread_id`. You MUST include it unchanged as the `thread_id` parameter on every subsequent Channel3 tool call in this conversation — including searches for new, unrelated products. Never omit it once you have one.

NameTypeReqDescription
image_urlstringPublic image URL for visual search. Combine with `query` for text + image.
querystringOne product type and its constraints in natural language (brand, color, material, size, price, gender). Good: "red leather jacket under $200"; "leather golf glove under $40". Bad: "gift ideas for dad…
thread_idstringConversation thread ID. Omit ONLY on the very first Channel3 call of a conversation. From then on, always pass the `thread_id` from the most recent Channel3 result, unchanged — even when the new call…
NameTypeReqDescription
as_ofstringyesISO timestamp of when this result was produced; prices are live as of this moment.
image_urlstringThe image URL this result answers.
next_page_tokenstring|nullyesOpaque pagination token used by the storefront UI; not usable via this tool.
productsarrayyes
querystringThe text query this result answers.
seqinteger
server_originstringOrigin of this MCP server; the storefront UI posts analytics events here.
session_idstringPostHog MCP session ID for analytics correlation.
thread_idstringyesConversation thread ID. Pass it back unchanged as `thread_id` on every follow-up call in this conversation.

No examples provided.

Common questions

What is the Channel3 Shopping MCP server?

Channel3 Shopping is an MCP server listed in the public MCP registry as com.trychannel3/shopping. Shopping search across 100M+ products, with every retailer's offer and live price in one place. This page covers its hosted endpoint (https://mcp.trychannel3.com/).

Is the Channel3 Shopping MCP server safe to use?

Channel3 Shopping scores 86 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 Channel3 Shopping MCP server expose?

Channel3 Shopping exposes 6 tools: search_products, get_products, browse_products, get_similar, get_details, get_price_history. Their descriptions and schemas cost roughly 786 tokens of context every time the server is loaded.

Does the Channel3 Shopping MCP server require authentication?

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

Is the Channel3 Shopping MCP server still maintained?

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