Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/price-drop-alert-tracker

REMOTE · MCP.ZOVO.ONE

Track product prices and get drop alerts - history, watches and pending alerts.

Available components

−13 this week 82 Trust /100

Last scanned (14 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Recent critical change

Authorization (17 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability86
  • 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 1041 tokens (~86/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 Management94
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 12 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 17 Nov 26 −13
    • Authorization: pass → fail ▼ critical
    • Stability: pass → fail ▼ security
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 75 → 84 ▼ functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 2026 · Probed https://mcp.zovo.one/mcp/price-drop-alert-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 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 39e1adfa4eb6500e0e3d48868766e3e9
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. DS published 64939 8 Verified
zovo.one. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

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-drop-alert-tracker Verified 200
http (plaintext) http://mcp.zovo.one/mcp/price-drop-alert-tracker HTTPS enforced 301 https://mcp.zovo.one/mcp/price-drop-alert-tracker
MCP tools · 10 exposed · ~839 tokens

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 →

Tool Tokens
alerts_pending ~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 ~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.

NameTypeReqDescription
keystringyesLicense key from checkout, MCPL1.<payload>.<signature>

No output schema declared.

No examples provided.

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 ~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.

NameTypeReqDescription
currencystring–ISO code such as USD or EUR
labelstring–Short name for this item
pricestring|numberyesPrice as shown, for example 1299.00 or 1.299,00
urlstringyesProduct page URL

No output schema declared.

No examples provided.

price_check ~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.

NameTypeReqDescription
urlstringyesProduct page URL, including https://

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
idstring–Watch id
limitinteger–Maximum observations to return
urlstring–Watch URL

No output schema declared.

No examples provided.

watch_add ~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.

NameTypeReqDescription
currencystring–ISO code such as USD or EUR, if the page does not say
labelstring–Short name for this item
target_pricestring|number–Report this watch in alerts_pending when the price is at or below this (positive number)
urlstringyesProduct page URL

No output schema declared.

No examples provided.

watch_list ~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 ~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.

NameTypeReqDescription
allboolean–Refresh every watch in one call (Pro; on free, refresh one id at a time)
idstring–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 ~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.

NameTypeReqDescription
idstring–Watch id from watch_list
urlstring–URL of the watch, if you do not have the id

No output schema declared.

No examples provided.

Install

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

io.github.theluckystrike/price-drop-alert-tracker is a hosted endpoint at https://mcp.zovo.one/mcp/price-drop-alert-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

# add to Claude Code
claude mcp add --transport http theluckystrike-price-drop-alert-tracker 'https://mcp.zovo.one/mcp/price-drop-alert-tracker'
Common questions

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

io.github.theluckystrike/price-drop-alert-tracker is an MCP server listed in the public MCP registry as io.github.theluckystrike/price-drop-alert-tracker. Track product prices and get drop alerts - history, watches and pending alerts. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/price-drop-alert-tracker).

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

io.github.theluckystrike/price-drop-alert-tracker scores 82 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-drop-alert-tracker MCP server expose?

io.github.theluckystrike/price-drop-alert-tracker 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-drop-alert-tracker MCP server require authentication?

No. We connected to io.github.theluckystrike/price-drop-alert-tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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

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

What did VerifyMCP test on the io.github.theluckystrike/price-drop-alert-tracker MCP server?

VerifyMCP ran 13 checks on io.github.theluckystrike/price-drop-alert-tracker, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.