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.

com.mambabuilt/mcp-competitor-price-stock-changelog-monitor

NPM · @MAMBALABSDEV/MCP-COMPETITOR-PRICE-STOCK-CHANGELOG-MONITOR

Competitor price, stock, plan, and changelog changes since your last run.

68 Trust /100

Last scanned (5 hours ago)

Scores higher than 38% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • 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 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 784 tokens (~784/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 22 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 21 Oct 26 53

    First indexed and scored.

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 23 Oct 2026 · Analysed npm/@mambalabsdev/mcp-competitor-price-stock-changelog-monitor@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~784 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
monitor_competitor_changes ~784

Watch competitor stores and SaaS sites and return only what changed since the last run with the same state_key. Give sites as domains or URLs (for example deathwishcoffee.com, linear.app). Shopify stores are read from their public product feed and WooCommerce stores from their public Store API, so you get price, compare at price, and stock changes per variant, plus new and removed products. SaaS sites are read from the pricing and changelog pages they link to, so you get plans added, removed, or repriced, and new changelog entries. Every site gets one row per run (site_baseline on the first check, then site_check with changes_found), plus one row per change with old and new values. Unreadable sites come back free with a row_status saying so. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per change row and per site check that is a first check or finds a change; an unchanged site is free.

NameTypeReqDescription
changelog_urlsarray–Changelog or release notes pages to read, when the site does not link to one from the homepage. An RSS or Atom feed the page declares is read first.
include_snapshotstring–true to also return one snapshot row per product variant, plan, and changelog entry on the first check of a site. Each snapshot row is billed as a snapshot row. Default false.
max_changes_per_sitestring–Change rows returned per site per run, up to 1000. The rest are counted in changes_found. Default 200.
max_charge_usdstring–Optional. The run stops before it would charge more than this.
max_productsstring–Products read from a store catalog per run, up to 5000. A store with more products than this is compared on the products read, and removed products are not reported for it. Default 250.
min_price_change_pctstring–Report a price change only when it is at least this many percent. 0 reports every change. Default 0.
pricing_urlsarray–Pricing pages to read, when the site does not link to its pricing page from the homepage.
product_urlsarray–Product pages on a store that is not Shopify or WooCommerce. Each page is read for its schema.org Product price and availability.
proxy_modestring–auto (default) sends requests directly and moves a host to the Apify proxy default pool only when that host refuses. A reliability setting: proxy use adds nothing to your price.
reset_statestring–true to ignore the saved state and record a new baseline for every site. Default false.
site_typestring–auto (default) reads the public Shopify product feed or the WooCommerce Store API when the site has one, and otherwise reads the pricing and changelog pages it links to.
sitesarrayyesCompetitor sites to watch, one per line: a domain (deathwishcoffee.com, linear.app) or a URL. A URL with a path is read as that page: a pricing page, a changelog page, or a product page. Up to 200 si…
state_keystring–Names the saved state, so separate schedules keep separate baselines. Runs with the same state key and site compare against each other.
watcharray–Any of: prices, stock, products, plans, changelog. prices covers price and compare at price per variant; stock covers in stock and out of stock; products covers new and removed products; plans covers…

No output schema declared.

No examples provided.

Install

How do I install the com.mambabuilt/mcp-competitor-price-stock-changelog-monitor server?

com.mambabuilt/mcp-competitor-price-stock-changelog-monitor runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-competitor-price-stock-changelog-monitor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @mambalabsdev/mcp-competitor-price-stock-changelog-monitor

# add to Claude Code
claude mcp add com-mambabuilt-mcp-competitor-price-stock-change -- npx -y @mambalabsdev/mcp-competitor-price-stock-changelog-monitor
Common questions

What is the com.mambabuilt/mcp-competitor-price-stock-changelog-monitor server?

com.mambabuilt/mcp-competitor-price-stock-changelog-monitor is listed in the public MCP registry as com.mambabuilt/mcp-competitor-price-stock-changelog-monitor. Competitor price, stock, plan, and changelog changes since your last run. This page covers its npm package (@mambalabsdev/mcp-competitor-price-stock-changelog-monitor).

Is the com.mambabuilt/mcp-competitor-price-stock-changelog-monitor server safe to use?

com.mambabuilt/mcp-competitor-price-stock-changelog-monitor scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. 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 com.mambabuilt/mcp-competitor-price-stock-changelog-monitor server expose?

com.mambabuilt/mcp-competitor-price-stock-changelog-monitor exposes 1 tool: monitor_competitor_changes. Their descriptions and schemas cost roughly 784 tokens of context every time the server is loaded.

Is the com.mambabuilt/mcp-competitor-price-stock-changelog-monitor server still maintained?

com.mambabuilt/mcp-competitor-price-stock-changelog-monitor is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the com.mambabuilt/mcp-competitor-price-stock-changelog-monitor server under?

com.mambabuilt/mcp-competitor-price-stock-changelog-monitor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.