price-watch

@ the log, two real entries

  surfshark / Starter          vpn            2026-05-30
- $2.49
+ $15.45

  bluehost / Basic             cloud-hosting  2026-07-06
- $1.99
+ $3.99

That first row is a 520 percent jump on an intro rate that quietly expired. Nobody mails you about these. This MCP server hands an assistant the reviewed log of every move like it, so "did this get more expensive" stops being a guess.

The log sits behind the pricing database, 494 tools deep. Dated rows, old and new values where a price moved, a human sign-off on each. The 30 days to July 10, 2026 carried 636 entries, 120 of them outright price moves.

What it watches

> The week of July 6, verbatim from the feed. Bluehost raised Basic from $1.99 to $3.99. Screaming Frog cut its paid tier from $279 to $199. Namecheap dropped Stellar to $2.28. Chargebee re-read Starter as free where it used to say $250 a month. Binance refreshed its spot maker and taker schedule, and Coinbase touched both Advanced Trade fees and the Coinbase One tiers.

What the raw rows behind that digest look like

bluehost / Basic             cloud-hosting  2026-07-06
- $1.99
+ $3.99

  screaming-frog / Paid        seo-tools      2026-07-06
- $279
+ $199

  namecheap / Stellar          cloud-hosting  2026-07-06
- $4.66
+ $2.28

  chargebee / Starter          payments       2026-07-08
- $250/mo
+ free

Hosting swings hardest week to week; intro rates expire, renewal ladders kick in, and the log catches each step with a date.

Ask it

Did Notion change anything this quarter?

`product_changes` returns dated rows for one slug. Notion right now: quiet quarter, last verified July 4. The human-readable trail is its price history page.

What went up the most this month?

`biggest_increases` ranks the sharpest hikes in a window. Surfshark's intro-rate expiry tops the current one.

Is anything moving in cloud hosting?

`category_changes` sweeps one category. Hosting logged three moves in the first week of July alone.

What does Framer charge today, and is that new?

`check_price` returns the current verified price plus the last change touching it. `recent_changes` is the same idea for the whole catalog, newest first.

How a call flows

sequenceDiagram
    participant A as Assistant
    participant S as price-watch
    participant F as changelog feed
    A->>S: biggest_increases, last 30 days
    S->>F: fetch once, cache 6h
    F-->>S: 636 dated entries
    S-->>A: ranked hikes, old and new prices, dates
    Note over A: answer cites dates,not vibes

The feed itself is public, `llms-changelog.json`, and the server filters it locally. Five tools, three prompts on top: `recent_price_moves` for a window digest, `track_product` for one tool's status and direction, `category_price_watch` for a category sweep with its sharpest hikes.

Hook it up

{
  "mcpServers": {
    "price-watch": {
      "command": "npx",
      "args": ["-y", "@comparedge/price-watch-mcp@latest"]
    }
  }
}

Claude Desktop reads `~/Library/Application Support/Claude/claude_desktop_config.json`, Cursor takes it under Settings then MCP, VS Code with Copilot uses `.vscode/mcp.json`. Restart the client and five tools show up. No key, no signup, zero dependencies. Client walkthroughs sit in the setup docs.

Why trust a log

Every row passed the same verification process before it landed; the feed carries each sign-off date. Month-by-month roundups of the same data become the pricing reports, and the raw rows ship as open pricing data under CC BY 4.0.

The server fetches two public feeds from comparedge.com, caches them for six hours, filters everything on your machine, and serves the last good copy if a refresh fails. The catalog sibling and the token-cost sibling live under the same MCP family roof.

MIT. JSON-RPC 2.0 over stdio.