https://api.trychannel3.com/mcp ↗
Find any product online.
channel3 is a remote MCP server published at api.trychannel3.com. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 673 ms, a delay an agent will notice. It offers a narrow, focused set of 3 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
search_catalog — Parameters like 'query' and 'filters' are listed but not clearly defined as optional or required.lookup_catalog — Overlap with 'search_catalog' creates ambiguity in use cases for 'ids' vs 'query'.get_product — Lacks explicit documentation on handling errors (e.g., invalid 'id').Risk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/alex-9y47-channel3)<a href="https://mcpmetrics.io/servers/alex-9y47-channel3"><img src="https://mcpmetrics.io/badge/alex-9y47/channel3/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 11:20:19 | Legacy | 400 | 981 | 200 | 981 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 900 | 200 | 903 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 400 | 581 | 200 | 579 | 2025-11-25 |
| 2026-09-11 05:44:28 | Legacy | 400 | 685 | 200 | 696 | 2025-11-25 |
| 2026-09-11 03:50:39 | Legacy | 400 | 622 | 200 | 639 | 2025-11-25 |
| 2026-09-11 01:59:45 | Legacy | 400 | 638 | 200 | 667 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 364 | 401 | 673 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.