BuyWhere MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor identity continuity, MCP tool inventory, permissions and adoption.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Product search and retailer price comparisons via MCP

What we know

Product search and retailer price comparisons via MCP. Published by the owner of npm package buywhere-mcp. BuyWhere MCP server for product search, price comparison, and affiliate-ready shopping workflows.

Maintenance / activity evidence

155 npm downloads, 2026-09-09 to 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high_for_identity_and_metrics_medium_for_verified_package_description.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation. Complete write authority is not verified.
Provider account/access per published package; check upstream
Sensitive access: Service account information and data accessible by supplied credentials

Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 155 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package buywhere-mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T04:43:53Z.

All limitations / Review context

Has buywhere-mcp changed publishing identity, permissions, install requirements, or risk exposure?

Published package documentation reviewed; public listing with prominently disclosed risks: Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation.

Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.
Provider account/access per published package; check upstream
Sensitive access: Service account information and data accessible by supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Respect upstream entitlements, version constraints and least-privilege setup.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Original activity observations

155 npm downloads, 2026-09-09 to 2026-10-08

Technical identity

npm/buywhere-mcp

Exact implementation source: https://www.npmjs.com/package/buywhere-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:buywhere-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Registry source ↗
registry.modelcontextprotocol.io/v0/servers
Source material retained for this review.
Package registry ↗
buywhere-mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Documentation entry — installation instructions still need review.

Warning

npm/buywhere-mcp is NOT proven binary-identical to npm/@buywhere/mcp-server.
Current vendor docs treat @buywhere/mcp-server as canonical; retain both identities for editorial resolution.
API key required; external API calls and possible billing not tested.
Identity mismatch: npm/buywhere-mcp README prescribes npx -y @buywhere/mcp-server; do not replace package identity or claim validated relationship; require publisher identity resolution
Vendor-owned buywhere-mcp repository and legacy npm/buywhere-mcp README both explicitly instruct launching a DISTINCT canonical npm package @buywhere/mcp-server; document as publisher-recommended dependency, not an identity match.
Independent vendor npm @buywhere/mcp-server exists; exact equivalence of two npm tarballs unverified. No silent identity substitution.
Recommended by vendor README, but runs a different npm identity than this Radar record.
Publisher README config reproduced as MCP100 structured data; requires real credentials and may require separately installed or built server. Not runtime tested.
For client use, configure npx -y @buywhere/mcp-server with BUYWHERE_API_KEY; retain Radar identity npm/buywhere-mcp and flag alternative npm identity; do not silently merge catalog records.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Identity mismatch persists. npm/buywhere-mcp README points to @buywhere/mcp-server. Do not copy other package command to the frozen identity; hold until provenance/identity is separately resolved.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect · exact package unresolved
Vendor-owned buywhere-mcp repository and legacy npm/buywhere-mcp README both explicitly instruct launching a DISTINCT canonical npm package @buywhere/mcp-server; document as publisher-recommended dependency, not an identity match. | Publisher npm README revisited on 2026-10-14; exact identity retained. WARNING: @buywhere/mcp-server belongs to a different exact npm identity; do not copy this other package as this record.
Configure / authenticate
MCP100 setup guide
Exact roster identity is npm/buywhere-mcp; fetched publisher README references `@buywhere/mcp-server` (a different package). Do not silently replace identity; verify package provenance and startup in the exact package before exposing it.
Required environment variables: BUYWHERE_API_KEY
Check connection
Suggested check
Do not claim authenticated tool success for `buywhere-mcp` based only on another package README.
Remove / uninstall / revoke
MCP100 setup guide
If your Claude Code MCP registration is named `buywhere-mcp`, run the client removal command. For Claude Desktop/Cursor/Codex or another registered name, remove the matching entry in that host’s MCP settings. Hosted OAuth disconnect and stopping a self-hosted process are separate; npx has no permanent global package install.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove buywhere-mcp

Official Documentation & Sources

What it does

Product search and retailer price comparisons via MCP. Published by the owner of npm package buywhere-mcp. BuyWhere MCP server for product search, price comparison, and affiliate-ready shopping workflows.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Retail & E-commerce
Best fit: Product search and retailer price comparisons via MCP

Representative uses

Product search and retailer price comparisons via MCP

Limitations

Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Provider account/access per published package; check upstream
Permissions: Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation.
Data handling: Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation.
Cost: Credit/subscription costs may apply; inspect provider docs
Risk and cautions: Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation.

Access scope and cautions

Write actions: Not verified
Sensitive access: Service account information and data accessible by supplied credentials
Risk level: medium
Security notes: Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation. Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T04:43:53Z. Watchlist tracking is not a recommendation or a security certification.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Do not infer shell entrypoint or automated credential setup if a command is not explicitly verified. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Provider account/access per published package; check upstream

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation.

What data-handling boundary should I consider?

Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation. Recorded sensitive-access context: Service account information and data accessible by supplied credentials.

What limitations and risks should I check before use?

Commerce/product comparisons may use affiliate tracking; price and merchant information need independent confirmation. Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes. Public exact-package npm downloads observed for recent 30-day window. Public listing suitability does not imply safe installation or entitlement to access third-party accounts. Respect upstream entitlements, version constraints and least-privilege setup.

What cost model is recorded?

The reviewed cost model is Credit/subscription costs may apply; inspect provider docs. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.