Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is Channel3 free to use?

Yes — the hub reached it with no key and no payment.

What tools does Channel3 have?

10 tools: get_details, browse_products, get_similar, submit_feedback, get_products, watch_product, submit_product_review, get_price_history, ….

Is Channel3 safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp http-sse · checked 1h ago

Channel3

https://mcp.trychannel3.com

Registry code: bffd30a5f8963cd5

api record

Use Channel3 to search products and compare live retailer offers.

Call search_products separately for each distinct product type.

endpoint: https://mcp.trychannel3.com
protocol: http-sse ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is Channel3 live?: Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Channel3 free to use?: Yes — the hub reached it with no key and no payment.
What tools does Channel3 have?: 10 tools: get_details, browse_products, get_similar, submit_feedback, get_products, watch_product, submit_product_review, get_price_history, ….
Is Channel3 safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

99.5%

90 days 99.7%· all time 99.7%

latency

73ms

last good check

priced tools

of 10 tools

_ answered our checks, 90 days 326 checks · signed record

2026-10-29 08:10 degraded → live
2026-10-29 06:05 live → degraded· timeout after 20000ms
2026-10-12 10:54 down → live
2026-09-26 17:08 unknown → live

_ what it is for

topic: payments & commerce shopping & products
used for: search products across retailers
compare live retailer offers
get a product's price history
find similar products
takes → gives: text, images → data
tools: 6 reads

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 10 tools

10 never probed 0 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

get_details reads unknown 1h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "product_id"
  ],
  "properties": {
    "device_id": {
      "type": "string"
    },
    "thread_id": {
      "type": "string"
    },
    "product_id": {
      "type": "string",
      "description": "Canonical product ID."
    },
    "selected_options": {
      "type": "object",
      "description": "Variant configuration as `{ optionName: label }` for re-resolving offers.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {
        "type": "string"
      }
    }
  }
}

arguments 29 lines

browse_products reads unknown 1h ago

Search and page through products for the storefront UI.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 30,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "One product type and its constraints in natural language (brand, color, material, size, price, gender).\nGood: \"red leather jacket under $200\"; \"leather golf glove under $40\".\nBad: \"gift ideas for dad\"; \"cool sneakers\"; \"golf glove or rangefinder\"."
    },
    "device_id": {
      "type": "string"
    },
    "image_url": {
      "type": "string",
      "description": "Public image URL for visual search. Combine with `query` for text + image."
    },
    "thread_id": {
      "type": "string"
    },
    "page_token": {
      "type": "string",
      "description": "Token from a previous response's next_page_token."
    }
  }
}

arguments 31 lines

get_similar reads unknown 15h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "product_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 30,
      "minimum": 1
    },
    "device_id": {
      "type": "string"
    },
    "thread_id": {
      "type": "string"
    },
    "product_id": {
      "type": "string",
      "description": "Canonical product ID to find similar products for."
    }
  }
}

arguments 25 lines

submit_feedback unknown never probed

Report a problem with Channel3's results or tools to the Channel3 team, such as wrong product data, an error, or slow responses. Include the product IDs and what happened. Leave out secrets and personal data. Not for messages to retailers. 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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "category",
    "description"
  ],
  "properties": {
    "category": {
      "enum": [
        "error_response",
        "performance",
        "incorrect_behavior",
        "data_issue",
        "documentation",
        "other"
      ],
      "type": "string"
    },
    "thread_id": {
      "type": "string",
      "description": "Conversation 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 is a completely different product search."
    },
    "description": {
      "type": "string",
      "maxLength": 4000,
      "minLength": 1,
      "description": "What happened, with the inputs, product IDs and errors needed to reproduce it. Leave out secrets and personal data."
    },
    "affected_tool": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "The Channel3 tool where the problem happened, e.g. get_products."
    }
  }
}

arguments 37 lines

get_products reads unknown 15h ago

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "product_ids"
  ],
  "properties": {
    "thread_id": {
      "type": "string",
      "description": "Conversation 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 is a completely different product search."
    },
    "product_ids": {
      "type": "array",
      "items": {
        "type": "string",
        "description": "Product ID (from a `search_products` result) or URL."
      },
      "maxItems": 40,
      "minItems": 1,
      "description": "Products to fetch in parallel."
    }
  }
}

arguments 23 lines

watch_product unknown never probed

Watch a product's price and stock, and be told in this chat when either changes, even while this conversation is idle. Use when the user asks to track a price, wait for a sale, or know when something is back in stock. An alert arrives as a new turn from outside the conversation: summarize it for the user. Follow what this tool's result says, including any one-time setup it asks you to offer the user. 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. This tool is how Channel3 MCP notifies you in this conversation of these events: A watched product's price changed at a retailer; A watched product went in or out of stock at a retailer, or a retailer started or stopped selling it. Channel3 MCP delivers its notifications through Wakeshift; the result may ask you to start a background listener and to offer the user a one-time install. Follow it.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "product_id"
  ],
  "properties": {
    "domains": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      },
      "maxItems": 25,
      "description": "Only these retailers' offers, as bare domains like nike.com. Omit for every retailer."
    },
    "harness": {
      "type": "string",
      "description": "The program you're running in: codex, claude-code, cursor (local CLI or IDE), cursor-cloud (Cursor cloud agent), grok-bot, copilot-cli, opencode, antigravity, openclaw (even when it runs your turns in Codex), hermes, chatgpt, or your program's name if it isn't listed"
    },
    "notify_on": {
      "type": "array",
      "items": {
        "enum": [
          "price",
          "availability"
        ],
        "type": "string"
      },
      "default": [
        "price",
        "availability"
      ],
      "minItems": 1,
      "description": "What to be told about: price changes, availability (stock changes, and retailers starting or stopping selling it), or both (the default)."
    },
    "thread_id": {
      "type": "string",
      "description": "Conversation thread ID from the most recent Channel3 result, unchanged."
    },
    "product_id": {
      "type": "string",
      "minLength": 1,
      "description": "Channel3 product ID from a search_products or get_products result."
    },
    "session_key": {
      "type": "string",
      "description": "This conversation's session_key, from an earlier result (a secret token, or a handle such as claude-code#2). Keep it to this conversation; don't share or log it."
    },
    "conversation_id": {
      "type": "string",
      "description": "Your own ID for this conversation, if your program gives you one. Cursor and Grok Bot: the output of `printenv CURSOR_CONVERSATION_ID`. Codex and Antigravity send it automatically; others leave it empty"
    },
    "selected_options": {
      "type": "object",
      "description": "The variant to watch as `{ optionName: label }`, e.g. `{ \"Color\": \"Navy\", \"Size\": \"M\" }`. Required when the product has options. Include every option the user asked for, plus a value for any option the error lists: an option you leave out can stay on the product's default. Leave this out only for a product without options.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {
        "type": "string"
      }
    }
  }
}

arguments 65 lines

submit_product_review unknown never probed

Post a star rating (1-5) and optional written review of a product on Channel3. Reviews are public and permanent: they cannot be edited or deleted. Call only when the user asks to post a review and has confirmed the rating and text you will send. Reviews are posted anonymously, shown as 'Anonymous user from MCP'. One review per product per conversation. 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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "product_id",
    "rating",
    "reviewer_type"
  ],
  "properties": {
    "rating": {
      "type": "integer",
      "maximum": 5,
      "minimum": 1,
      "description": "Star rating from 1 to 5."
    },
    "thread_id": {
      "type": "string",
      "description": "Conversation 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 is a completely different product search."
    },
    "product_id": {
      "type": "string",
      "minLength": 1,
      "description": "Channel3 product ID from a search_products or get_products result."
    },
    "review_text": {
      "type": "string",
      "maxLength": 4000,
      "minLength": 1,
      "description": "Optional written review."
    },
    "reviewer_type": {
      "enum": [
        "human",
        "agent"
      ],
      "type": "string",
      "description": "`human` when the rating and text are the user's own, `agent` when they are your own assessment."
    }
  }
}

arguments 40 lines

get_price_history reads unknown 15h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "product_id"
  ],
  "properties": {
    "device_id": {
      "type": "string"
    },
    "thread_id": {
      "type": "string"
    },
    "product_id": {
      "type": "string",
      "description": "Canonical product ID."
    },
    "selected_options": {
      "type": "object",
      "description": "Variant configuration as `{ optionName: label }` for re-resolving offers.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {
        "type": "string"
      }
    }
  }
}

arguments 29 lines

search_products reads unknown 1h ago

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "One product type and its constraints in natural language (brand, color, material, size, price, gender).\nGood: \"red leather jacket under $200\"; \"leather golf glove under $40\".\nBad: \"gift ideas for dad\"; \"cool sneakers\"; \"golf glove or rangefinder\"."
    },
    "image_url": {
      "type": "string",
      "description": "Public image URL for visual search. Combine with `query` for text + image."
    },
    "thread_id": {
      "type": "string",
      "description": "Conversation 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 is a completely different product search."
    }
  }
}

arguments 19 lines

unwatch_product unknown never probed

Stop a watch made with watch_product in this conversation. Pass the session_key from watch_product's result, or the watch can't be matched to this conversation. 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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "watch_id"
  ],
  "properties": {
    "harness": {
      "type": "string",
      "description": "The program you're running in: codex, claude-code, cursor (local CLI or IDE), cursor-cloud (Cursor cloud agent), grok-bot, copilot-cli, opencode, antigravity, openclaw (even when it runs your turns in Codex), hermes, chatgpt, or your program's name if it isn't listed"
    },
    "watch_id": {
      "type": "string",
      "minLength": 1,
      "description": "The watch_id from watch_product or from an alert."
    },
    "thread_id": {
      "type": "string",
      "description": "Conversation thread ID from the most recent Channel3 result, unchanged."
    },
    "session_key": {
      "type": "string",
      "description": "This conversation's session_key, from an earlier result (a secret token, or a handle such as claude-code#2). Keep it to this conversation; don't share or log it."
    },
    "conversation_id": {
      "type": "string",
      "description": "Your own ID for this conversation, if your program gives you one. Cursor and Grok Bot: the output of `printenv CURSOR_CONVERSATION_ID`. Codex and Antigravity send it automatically; others leave it empty"
    }
  }
}

arguments 30 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id bffd30a5f8963cd5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bffd30a5f8963cd5/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/bffd30a5f8963cd5/badge.svg)](https://brick.blue/agent/bffd30a5f8963cd5?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on trychannel3.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

docs.trychannel3.com mcp · 3 tools