World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Track product prices and get drop alerts - history, watches and pending alerts.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Price Drop Alert Tracker。按照 https://mcp.popnx.com/i/theluckystrike-price-drop-alert-tracker.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.zovo.one) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 Price Drop Alert Tracker 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Price Drop Alert Trackerhttps://mcp.zovo.one/mcp/price-drop-alert-tracker在 Request headers 下添加这个名称和值
AuthorizationBearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsPrice Drop Alert Tracker
用 Price Drop Alert Tracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Price Drop Alert Tracker,或回答中出现 Price Drop Alert Tracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Price Drop Alert Tracker
Price Drop Alert Tracker 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 Price Drop Alert Tracker 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code · 约 5 分钟
需要 Price Drop Alert Tracker 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user price-drop-alert-tracker https://mcp.zovo.one/mcp/price-drop-alert-tracker --header 'Authorization: Bearer your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Price Drop Alert Tracker 在列表中并显示已连接
用 Price Drop Alert Tracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Price Drop Alert Tracker,或回答中出现 Price Drop Alert Tracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 Price Drop Alert Tracker 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
在 Price Drop Alert Tracker 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Price Drop Alert Tracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Price Drop Alert Tracker,或回答中出现 Price Drop Alert Tracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 Price Drop Alert Tracker 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
在 Price Drop Alert Tracker 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Price Drop Alert Tracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Price Drop Alert Tracker,或回答中出现 Price Drop Alert Tracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --transport http --scope user price-drop-alert-tracker https://mcp.zovo.one/mcp/price-drop-alert-tracker --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"price-drop-alert-tracker": {
"url": "https://mcp.zovo.one/mcp/price-drop-alert-tracker",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"price-drop-alert-tracker": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/price-drop-alert-tracker",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}说明仍为英文原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
工具名称和描述与服务器在 2026年11月14日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
price_checkCall 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.
watch_addCall 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.
watch_listShow 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_removeCall 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.
watch_refreshThe 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.
price_historyCall 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.
price_add_manualCall 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.
alerts_pendingAnswer 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_statusReport 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_activateTurn Pro on for this connection with key, an MCPL1. . 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.
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 theluckystrike 验证,该账户拥有此仓库
代码最后更新于昨天
使用 MIT
在 1110 毫秒内响应(HTTP 200)
无需登录
已读取 10 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/theluckystrike-price-drop-alert-tracker)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于昨天,最新版本(0.23.2)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Price Drop Alert Tracker | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Featured on [Awesome MCP Servers](https://mcpservers.org) - directory listing | live hosted endpoint, free tier, no signup.
Ask your assistant what something costs right now. Point it at any product page and it reads the price off the page, remembers it, and tells you next time whether the price moved, how far, and whether it reached the number you were waiting for. It works on ordinary shop pages by reading the structured data most stores already publish (JSON-LD, Open Graph, microdata) and falling back to the visible price when they do not. When a large retailer blocks automated requests it says so plainly and lets you record the price yourself so the history stays intact. Everything is stored in a JSON file on your own machine.
Built by theluckystrike.
In the [official MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.theluckystrike%2Fprice-tracker-drop-alert-watch/versions/latest) (io.github.theluckystrike/price-tracker-drop-alert-watch).
Watch any product page for price drops from chat, no scraping service, no account, all local.
npm publish for @theluckystrike/mcp-price-tracker is pending. Until then, the .mcpb one-click bundle or a clone+build is the working path, both are verified below.
One-click (.mcpb): download price-tracker.mcpb from the latest release and double-click it in Claude Desktop: https://github.com/theluckystrike/mcp-servers/releases/latest
(claude_desktop_config.json):
{
"mcpServers": { "price-tracker": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-price-tracker"] } } }
Claude Code:
claude mcp add price-tracker -- npx -y @theluckystrike/mcp-price-tracker
(.cursor/mcp.json):
{
"mcpServers": { "price-tracker": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-price-tracker"] } } }
The npx form above starts working the moment the package is published. Until then, use the .mcpb bundle above, or build from source with exactly these three commands:
git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-servers
npm install npm run build -w packages/mcp-license -w servers/price-tracker
Then point your client's command at node with one arg: the absolute path to servers/price-tracker/dist/index.js.
To run in Pro mode set MCP_LICENSE_KEY in the same config block, or call license_activate once with your key.
| Tool | What it does |
|---|---|
price_check | Fetch a page now; returns price, currency, title, extraction confidence and the change against the last stored observation for that URL. No watch needed. |
watch_add | Start tracking a URL. Stores the first observation. Optional label, target_price, currency. |
watch_list | Every watch with current price, min, max, change, target, confidence and source. |
watch_remove | Stop tracking, by id or url. |
watch_refresh | Re-fetch one watch (id) or all of them (all: true); appends observations and returns current, previous, min, max, change % and target-hit flags. This is the only thing that checks prices. |
price_history | Stored observations for one watch, oldest first, optional limit. |
price_add_manual | Record a price you read yourself, for shops that block bots. Creates the watch if needed. |
alerts_pending | Watches whose latest price is at or below target, or which dropped 5% or more since the previous observation. Free. |
license_status | Free or Pro, and where to upgrade. |
license_activate | Activate a Pro key. Verified offline. |
Resource: prices://watches - JSON of every watch with its latest price.
Prompt: check_prices - refreshes every watch and summarises the drops and target hits in one command.
| You say | Tool |
|---|---|
| "What does this cost right now: \ ?" | price_check |
| "Watch that page and alert me if it goes under 40." | watch_add |
| "Show me everything I'm watching and whether anything dropped." | watch_refresh (all) then watch_list |
| "Stop tracking that laptop, I bought it elsewhere." | watch_remove |
| "Refresh my watches." | watch_refresh |
| "What's the price history on the bookshelf I'm watching?" | price_history |
| "I checked myself, it's 39.99 GBP in-store, log that." | price_add_manual |
| "Has anything I'm watching hit its target or dropped a lot?" | alerts_pending |
| "Am I on the free plan or Pro?" | license_status |
| "Here's my license key, activate it." | license_activate |
A real run against books.toscrape.com, from docs/USER_VALUE_R2.md, with WebFetch/WebSearch disallowed so the price-tracker's own tools had to answer:
You: What does this cost right now: https://books.toscrape.com/catalogue/...?
price_check { url: "https://books.toscrape.com/catalogue/..." } -> price 51.77, currency GBP, source regex-fallback, confidence low
Assistant: GBP 51.77. Confidence: low (regex-fallback) -- this page has no structured price data, so I read it from the visible text.
The confidence label is not decoration: books.toscrape.com carries no JSON-LD or microdata, so this is the one case in testing where the regex fallback was the only path to a number, and the model relayed the "low" label to the user unprompted rather than stating 51.77 as a fact.
There is no scheduler and no daemon. A watch is a stored history, not a subscription: prices are re-read only when watch_refresh runs, and alerts_pending reports on what is already stored. The working pattern is to say "refresh my watches" at the start of a session (or run the check_prices prompt), then ask what dropped.
| Free | Pro ($19 one-time) | |
|---|---|---|
price_check | Unlimited | Unlimited |
alerts_pending | Yes, unlimited | Yes, unlimited |
| Watches | 3 | Unlimited |
| History per watch | Last 30 observations | Full history |
watch_refresh one item | Yes | Yes |
watch_refresh all at once | No | Yes |
price_add_manual | Yes | Yes |
| Redirect check and extraction confidence | Yes | Yes |
Get Pro - $19 for this server, $39 for every server, lifetime.
In order: JSON-LD Product/Offer (price, priceCurrency, lowPrice), microdata itemprop="price", Open Graph og:price:amount / product:price:amount, meta itemprop, data-price attributes, common price class and id hints (including Amazon's a-offscreen), and finally a regex over the visible text of the first 200 KB. European and US separators are both understood, so 1.299,00 EUR and 1,299.00 USD both become 1299.00.
Prices are stored as decimal strings in the major unit with a . decimal separator and no grouping, for example "1299.00". Timestamps are ISO 8601 UTC.
Every reading carries a confidence: high for JSON-LD, microdata, meta itemprop and Open Graph; medium for data-price attributes and price class or id hints; low for the regex fallback. A low reading on a page with no product title is reported but never stored.
Where a page describes several products in JSON-LD (recommendations, "customers also bought"), the offers of one product are never pooled with another's: the product whose name matches the page title wins, otherwise the first product carrying offers. Crossed-out and previous prices ( , , , and classes such as old-price, was, compare-at-price, list-price, rrp) are skipped, so a struck 199 next to a live 99 reports 99. An ISO code written next to the number ("$10 USD") wins over the currency guessed from the domain, and twitter:data1 - free text such as "Free shipping over $50" - is not read as a price.
Pages are fetched with a desktop browser User-Agent, a 12 second timeout, redirects followed, and a 2 MB body cap. After the fetch the final URL is compared with the one you asked for: if the shop redirected off the product path - a different path depth, a category or home page, or a generic title such as "Products", "Home", the shop name alone, or "not found" - you get the shop redirected to , which is not a product page instead of the cheapest item on the listing it landed on. A redirect that only inserts a canonical slug in front of the same product id or path (Newegg, Amazon /dp/, Zalando-style URLs) is accepted, not refused.
Watches and their price history live in one JSON file: ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/price-tracker/watches.json. Every mutation (watch_add, watch_remove, watch_refresh, price_add_manual) happens under an advisory lock file, .../price-tracker/.lock, held across the load-mutate-save cycle so two refreshes running at once cannot interleave. price_check and read-only tools do not need the lock. Saves write to a temporary file and rename it into place, so an interrupted write cannot leave a half-written file. To back up your watch history, copy watches.json.
Only a missing file counts as "no watches yet". If watches.json exists but cannot be read or parsed, the server never treats it as empty: the unreadable bytes are moved to watches.json.corrupt- , the fault is written to stderr, and every tool answers with an error naming that file until the server is restarted. A damaged database can therefore never be silently overwritten by the next price you record.
price_add_manual is the working answer for a blocked shop.watch_refresh. This is not a missing feature; a local stdio server has no business running a daemon on your machine.price_check and alerts_pending are unlimited on free.low-confidence regex reading is still reported, but never silently treated as certain, pass it on to the user as an estimate, not a fact..mcpb bundle or the clone-and-build path above until it lands.servers/price-tracker/dist/index.js after npm run build. Point your client's command at node with that absolute path as the only argument.node -v.price_add_manual if the shop keeps redirecting.