io.github.theluckystrike/price-tracker-drop-alert-watch
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Check a shop page price now, keep a watch list, see history and target alerts. All data stays local.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 907 tokens (~75/item across 12 items; 10 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-price-tracker-drop-alert-watch 'https://mcp.zovo.one/mcp/price-tracker'
{
"mcpServers": {
"theluckystrike-price-tracker-drop-alert-watch": {
"url": "https://mcp.zovo.one/mcp/price-tracker"
}
}
} {
"servers": {
"theluckystrike-price-tracker-drop-alert-watch": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/price-tracker"
}
}
} [mcp_servers.theluckystrike-price-tracker-drop-alert-watch] url = "https://mcp.zovo.one/mcp/price-tracker"
{
"$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 mcp add theluckystrike-price-tracker-drop-alert-watch --url 'https://mcp.zovo.one/mcp/price-tracker' --transport streamable-http
mcp_servers:
theluckystrike-price-tracker-drop-alert-watch:
url: "https://mcp.zovo.one/mcp/price-tracker" {
"McpServers": {
"theluckystrike-price-tracker-drop-alert-watch": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/price-tracker"
}
}
} assistant mcp add theluckystrike-price-tracker-drop-alert-watch -t streamable-http -u 'https://mcp.zovo.one/mcp/price-tracker'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 17 Sept 26 +1
- Server version: 0.21.0 → 0.22.0 functional
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +1
- Tool “license_activate” rewrote its description, which is the text the model reads security
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 0
- 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 security
- Schema quality: 68 → 77 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +42
- Transport: unverified → pass ▲ security
- 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. security
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 2 Sept 26 36
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/price-tracker
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/price-tracker | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/price-tracker | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/price-tracker |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
alerts_pending Pending alerts ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
license_activate Activate license ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
price_add_manual Record a price by hand ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO code such as USD or EUR |
| label | string | – | Short name for this item |
| price | string|number | yes | Price as shown, for example 1299.00 or 1.299,00 |
| url | string | yes | Product page URL |
No output schema declared.
No examples provided.
price_check Check a price now ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Product page URL, including https:// |
No output schema declared.
No examples provided.
price_history Price history ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Watch id |
| limit | integer | – | Maximum observations to return |
| url | string | – | Watch URL |
No output schema declared.
No examples provided.
watch_add Watch a price ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Product page URL |
No output schema declared.
No examples provided.
watch_list List watches ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
watch_refresh Refresh prices ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
watch_remove Remove a watch ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Watch id from watch_list |
| url | string | – | URL of the watch, if you do not have the id |
No output schema declared.
No examples provided.
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.