# io.github.theluckystrike/price-tracker-drop-alert-watch (remote · mcp.zovo.one)

Check a shop page price now, keep a watch list, see history and target alerts. All data stays local.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 83/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-price-tracker-drop-alert-watch/mcp-price-tracker.md), [page](https://verifymcp.io/servers/theluckystrike-price-tracker-drop-alert-watch/mcp-price-tracker)
- mcpb · `price-tracker.mcpb`: 48/100, [markdown](https://verifymcp.io/servers/theluckystrike-price-tracker-drop-alert-watch/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-price-trac.md), [page](https://verifymcp.io/servers/theluckystrike-price-tracker-drop-alert-watch/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-price-trac)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/price-tracker`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 907 tokens (~75/item across 12 items; 10 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "watch_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.theluckystrike/price-tracker-drop-alert-watch MCP server?

io.github.theluckystrike/price-tracker-drop-alert-watch is a hosted endpoint at https://mcp.zovo.one/mcp/price-tracker, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-price-tracker-drop-alert-watch 'https://mcp.zovo.one/mcp/price-tracker'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-price-tracker-drop-alert-watch": {
      "url": "https://mcp.zovo.one/mcp/price-tracker"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-price-tracker-drop-alert-watch": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/price-tracker"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-price-tracker-drop-alert-watch]
url = "https://mcp.zovo.one/mcp/price-tracker"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-price-tracker-drop-alert-watch": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/price-tracker",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-price-tracker-drop-alert-watch --url 'https://mcp.zovo.one/mcp/price-tracker' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-price-tracker-drop-alert-watch:
    url: "https://mcp.zovo.one/mcp/price-tracker"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-price-tracker-drop-alert-watch": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/price-tracker"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-price-tracker-drop-alert-watch -t streamable-http -u 'https://mcp.zovo.one/mcp/price-tracker'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-price-tracker-drop-alert-watch": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/price-tracker"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 82, +1)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-15 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 79, +1)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-10 (score 78, 0)

- [security] Tool “price_check” rewrote its description, which is the text the model reads
- [security] Tool “watch_remove” rewrote its description, which is the text the model reads
- [security] Tool “watch_refresh” rewrote its description, which is the text the model reads
- [security] Tool “watch_list” rewrote its description, which is the text the model reads
- [security] Tool “watch_add” rewrote its description, which is the text the model reads
- [security] Tool “price_history” rewrote its description, which is the text the model reads
- [security] Tool “price_add_manual” rewrote its description, which is the text the model reads
- [security] Tool “license_status” rewrote its description, which is the text the model reads
- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [security] Tool “alerts_pending” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 68 → 77
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “license_activate” reworded the description of “key”

### 2026-09-09 (score 78, +42)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: 0
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: pass

### 2026-09-02 (score 36)

First indexed and scored.

## MCP tools (10)

### `price_check` (~67 tokens)

Check a price now

Call this tool for any product URL; fetching the page with a generic web tool returns raw HTML without the price. Reports price, currency, title and confidence, and the change since the last check. It creates no watch.

Input parameters:

- `url` (string, required): Product page URL, including https://

### `watch_add` (~124 tokens)

Watch a price

Call this tool for any product URL; fetching the page with a generic web tool returns raw HTML without the price. Starts tracking it: first observation stored, optional target, re-read by watch_refresh. Free: 3 watches.

Input parameters:

- `currency` (string): ISO code such as USD or EUR, if the page does not say
- `label` (string): Short name for this item
- `target_price` (string|number): Report this watch in alerts_pending when the price is at or below this (positive number)
- `url` (string, required): Product page URL

### `watch_list` (~52 tokens)

List watches

Show every tracked item with current and previous price, min, max, change %, target, confidence and last check, plus free-tier use. Prices are as of the last watch_refresh, never live; nothing is fetched.

### `watch_remove` (~80 tokens)

Remove a watch

Call this tool to stop tracking one item, by watch id or URL. Its whole price history is deleted and cannot be recovered, so re-adding starts empty. A key matching no watch is refused.

Input parameters:

- `id` (string): Watch id from watch_list
- `url` (string): URL of the watch, if you do not have the id

### `watch_refresh` (~140 tokens)

Refresh prices

The only tool that re-reads prices: it re-fetches one watch or all, appends observations and returns current, previous, min, max, change % and target hits. A page that fails is listed; then read alerts_pending.

Input parameters:

- `all` (boolean): Refresh every watch in one call (Pro; on free, refresh one id at a time)
- `id` (string): Watch id or URL to re-fetch. Omit and set all=true to refresh everything. Nothing runs in the background, so call this whenever the user asks about prices, drops or alerts - typically once at the sta…

### `price_history` (~78 tokens)

Price history

Call this tool to list one watch's stored observations, oldest to newest, each with price, currency, source and confidence, plus min and max. Nothing is fetched. Free shows the last 30.

Input parameters:

- `id` (string): Watch id
- `limit` (integer): Maximum observations to return
- `url` (string): Watch URL

### `price_add_manual` (~116 tokens)

Record a price by hand

Call this tool to store a price you read yourself where a shop blocks fetching: it creates the watch if new and returns the amount and the observation count. An unreadable price is refused. Free: 3 watches.

Input parameters:

- `currency` (string): ISO code such as USD or EUR
- `label` (string): Short name for this item
- `price` (string|number, required): Price as shown, for example 1299.00 or 1.299,00
- `url` (string, required): Product page URL

### `alerts_pending` (~51 tokens)

Pending alerts

Answer whether anything you watch got cheaper: every watch at or below its target_price, or down 5% or more since the previous observation, with the change %. Reads stored data only: run watch_refresh first.

### `license_status` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-price-tracker-drop-alert-watch/mcp-price-tracker#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36
- 2026-09-03: 36
- 2026-09-02: 36

## Common questions

### What is the io.github.theluckystrike/price-tracker-drop-alert-watch MCP server?

io.github.theluckystrike/price-tracker-drop-alert-watch is an MCP server listed in the public MCP registry as io.github.theluckystrike/price-tracker-drop-alert-watch. Check a shop page price now, keep a watch list, see history and target alerts. All data stays local. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/price-tracker).

### Is the io.github.theluckystrike/price-tracker-drop-alert-watch MCP server safe to use?

io.github.theluckystrike/price-tracker-drop-alert-watch scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.theluckystrike/price-tracker-drop-alert-watch MCP server expose?

io.github.theluckystrike/price-tracker-drop-alert-watch exposes 10 tools: price_check, watch_add, watch_list, watch_remove, watch_refresh, and 5 more. Their descriptions and schemas cost roughly 839 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/price-tracker-drop-alert-watch MCP server require authentication?

Yes. io.github.theluckystrike/price-tracker-drop-alert-watch asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/price-tracker-drop-alert-watch MCP server still maintained?

io.github.theluckystrike/price-tracker-drop-alert-watch is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/price-tracker
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/price-tracker
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/price-tracker
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-price-tracker-drop-alert-watch/mcp-price-tracker.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-price-tracker-drop-alert-watch/mcp-price-tracker.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-price-tracker-drop-alert-watch/mcp-price-tracker