Should my agent depend on the MCP server com.webotee/amazon-product-research-mcp?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

amazon product research mcp

com.webotee/amazon-product-research-mcp

Amazon brand, seller, niche & buy-box intelligence inside your own Claude or ChatGPT.

— the operator's own registry description reported

Publisher com.webotee · first seen 2026-08-12 · endpoint https://app.webotee.com/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.485 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency351 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools79

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_3d9c59efd90b32035a43b747 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

alibaba_supplier_search asin_buybox_history asin_comparables asin_profit_calc authorized_seller_list authorized_seller_set brand_buybox_trajectory brand_new_asins brand_similar brand_under_attack brand_xmarket brands_gaining_sellers brands_in_operator_network buybox_loss_alert categories_amazon_retreating category_metrics category_new_entrants category_top_growers category_undercompeted_brands collect_asin_now competitive_landscape evaluate_asin_sourcing evaluate_brand evaluate_category_for_private_label filter_brands_by_fba_share filter_operators_by_fba_share find_brands_with_high_seller_churn find_deconcentrating_brands find_new_operators find_product_across_web find_single_seller_brands find_sourcing_opportunities find_undercompeted_brands find_underserved_niches gating_repricing_advice keyword_cross_marketplace keyword_demand map_violations_today my_competitors my_opportunities my_products my_store operator_brands_by_competition operator_buybox_losses operator_category_dominance operator_classifier operator_compare operator_concentration operator_lost_brands operator_new_brands operator_new_on_brand operator_resells_what operator_top_asins operator_top_brands operator_xmarket_presence playbook_create playbook_list playbook_run_now playbook_schedule product_page_content risk_assessment search_products set_cost_floor shopping_search top_expanding_operators top_sourcing_picks top_velocity_brands unauthorized_sellers watchlist_add watchlist_add_rule watchlist_delta watchlist_diff watchlist_list watchlist_remove watchlist_stats watchlist_webwide web_search webotee_job_status xmkt_pricing_compare

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	79/79	✓
has a description	79/79	✓
description is substantive	79/79	✓
parameters are typed	79/79	✓
parameters are described	27/79	27/79

79 of 79 tools graded · 79 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.0.0

server version Webotee AI Connect

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:38Z	ok_tools	200	351	2025-06-18
2026-08-12T05:33:52Z	ok_tools	200	420	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.webotee/amazon-product-research-mcp.svg)](https://robinsaige.com/s/com.webotee/amazon-product-research-mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview