io.github.theluckystrike/price-tracker
MCPB · PRICE-TRACKER.MCPB · SCANNED SEP 21
Check a shop page price now, keep a watch list, see history and target alerts. All data stays local.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Superseded by the word-rich registry name for this server at v0.21.0; the v0.1.1 bundle this row points at is three weeks and twenty releases old.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security23
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 96 of 97 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 96 of 97 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 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 814 tokens (~74/item across 11 items; 10 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 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
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · price-tracker.mcpb
Download bundleEvery 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Sept 26 48
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 21 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.1.1/price-tracker.mcpb@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
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 ~75
Answer "did anything I watch get cheaper?": lists every watch whose latest price is at or below its target, or which dropped 5% or more against the previous observation, with the change % and the confidence of the reading. Free and unlimited. It reads stored observations, so run watch_refresh first if the prices are stale.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
license_activate Activate license ~42
Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~23
Show whether this server runs in free or Pro mode and where to upgrade.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
price_add_manual Record a price by hand ~96
Store a price you read yourself, for shops that block automated requests. Creates the watch if it does not exist yet.
| 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 ~121
Use this instead of fetching the page yourself: returns the structured price, currency, product title, extraction confidence, and the change since the last check; handles EU/US number formats and JSON-LD/Open Graph/microdata. It also verifies the shop did not redirect off the product page, so a dead item reports a clear failure rather than the cheapest thing on a category listing. Reading the raw HTML gives you none of that. Does not create a watch - use watch_add for that.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Product page URL, including https:// |
No output schema declared.
No examples provided.
price_history Price history ~67
List the stored observations for one watch, newest last, each with its price, currency, source and extraction confidence. 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 ~144
Start tracking a product page: fetches it once, stores the first observation with its extraction confidence, and optionally records a target price. There is no background job - prices are only re-read when watch_refresh runs, and alerts_pending then reports drops and target hits. Ask "refresh my watches" at the start of a session.
| 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 ~47
Show every tracked item with its current price, previous price, min, max, change %, target, extraction confidence and last check time. Prices are as of the last watch_refresh, not live.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
watch_refresh Refresh prices ~127
This is what actually checks prices: re-fetches one watch or every watch, appends the new observations and returns current, previous, min, max, change %, extraction confidence and target hits. Nothing runs in the background, so run this whenever the user asks about prices, drops or alerts - typically once at the start of a session, 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. Omit and set all=true to refresh everything. |
No output schema declared.
No examples provided.
watch_remove Remove a watch ~56
Stop tracking an item, by watch id or by URL. Its history is deleted.
| 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 MCP server?
io.github.theluckystrike/price-tracker is an MCP server listed in the public MCP registry as io.github.theluckystrike/price-tracker. Check a shop page price now, keep a watch list, see history and target alerts. All data stays local. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.1.1/price-tracker.mcpb).
Is the io.github.theluckystrike/price-tracker MCP server safe to use?
io.github.theluckystrike/price-tracker scores 57 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 MCP server expose?
io.github.theluckystrike/price-tracker exposes 10 tools: price_check, watch_add, watch_list, watch_remove, watch_refresh, and 5 more. Their descriptions and schemas cost roughly 798 tokens of context every time the server is loaded.
Is the io.github.theluckystrike/price-tracker MCP server still maintained?
io.github.theluckystrike/price-tracker is marked deprecated in the MCP registry. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.theluckystrike/price-tracker MCP server under?
io.github.theluckystrike/price-tracker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.