These three answer different questions. keepa-mcp answers "what has this Amazon ASIN cost over the last year", using the Keepa API. pricetrack-mcp answers "what does this SaaS product charge today and when did it last change", from a catalogue of published vendor pricing. Ours answers "watch this exact URL and tell me when it drops", for any ordinary shop page, with the history kept on your disk.
| Fact | Ours | keepa-mcp | pricetrack-mcp |
|---|---|---|---|
| Tools | 8 plus license_status and license_activate | 6 | 4 public catalogue tools |
| Transport | stdio, plus a hosted streamable HTTP endpoint | stdio (npx) | Hosted streamable HTTP, plus stdio via npx |
| Account or API key needed | No | Yes, KEEPA_API_KEY | No for the four public tools; OAuth sign-in for account tools |
| What it can see | Any public product page you give a URL for | Amazon catalogue data through Keepa | Published pricing for the SaaS products in the PriceTrack catalogue |
| Where the history lives | Local JSON in ~/.local/share/mcp-servers/price-tracker/ | Keepa, queried per call | PriceTrack servers |
| Licence | MIT | MIT | MIT |
| Latest release read | 0.2.3 on the MCP registry | npm keepa-mcp 0.1.2, 2026-08-09 | npm @pricetrack/mcp 0.1.0, 2026-08-18 |
| Target alerts you set yourself | Yes, per watch | No, deals are Keepa-wide filters | No, alerts are an account feature |
Pick it for Amazon research. Nothing we do comes close to a year of decoded price series, sales rank history with a demand trend, keyword ASIN search, category best sellers or a deals feed filtered by drop percentage and rating. Those are the six tools it exposes. It needs a Keepa API key, and its README states plainly that it is an unofficial client not affiliated with Keepa.
Pick it when the question is about software vendors rather than products in a basket. It searches a
catalogue the project describes as 33,000 or more SaaS products, returns current plans with billing
periods, lists verified price changes and the biggest 30 day movers, and compares two to five products
side by side. It also has the lowest friction of the three: a hosted URL with no authentication, so
claude mcp add --transport http pricetrack https://pricetrack.dev/api/mcp is the whole
install.
Pick ours when the page you care about is not in anyone's catalogue: a European shop, a niche
retailer, a supplier quote page, a competitor's own pricing page. You pass a URL,
price_check fetches it and reports price, currency, title and the change since the last
stored observation, and watch_add keeps it on a list with an optional target price.
History and alerts stay in local JSON, so nobody learns what you are watching. Extraction reads
JSON-LD, microdata and Open Graph before falling back to text, and returns a confidence level rather
than pretending. Free covers unlimited checks, 3 watches and 30 observations each.
The price-tracker package carries 39 automated tests, all passing, covering price extraction across page shapes, redirect handling, the stdio protocol and two concurrent writers. The 121 check validate.mjs probe suite is at 121 of 121. In user value round 5, the price watch and refresh scenario was driven through the real Claude CLI and scored 3 of 3. The five suites together are 144 tests.
Ours, Claude Code:
claude mcp add price-tracker -- npx -y @theluckystrike/mcp-price-trackerkeepa-mcp:
claude mcp add keepa -e KEEPA_API_KEY=your_key -- npx -y keepa-mcppricetrack-mcp:
claude mcp add --transport http pricetrack https://pricetrack.dev/api/mcpConfig file paths per client are on the setup pages. The product page for ours is MCP Price Tracker, and the guides cover the watch and alert workflow.
It fetches the URL you give it like any other page, and extraction is best effort with a confidence level. For Amazon specifically, keepa-mcp is built for it and has real history behind it; ours is built for the long tail of shop pages that no catalogue covers.
Only when you ask. It is a local server with no background process, so watch_refresh runs when the model calls it. If you want a schedule, run watch_refresh from a cron job that talks to the server.
Only the shop, when a fetch happens. The watch list and the observation history are JSON files under your home directory and are never uploaded. keepa-mcp and pricetrack-mcp both send your query to their service by design.
Yes, and it is a reasonable setup: keepa-mcp for Amazon history, pricetrack-mcp for SaaS pricing, ours for the specific pages you care about. Tool names do not collide.
Unlimited price_check calls, 3 watches, and 30 stored observations per watch, with target alerts included. Pro at $19 once removes the watch and history limits and adds refresh all.