com.mambabuilt/mcp-creator-change-monitor
NPM · @MAMBALABSDEV/MCP-CREATOR-CHANGE-MONITOR
Recheck a named influencer watchlist and return what moved since the run before it.
Available components
Last scanned (20 hours ago)
Scores higher than 71% of npm servers
Category Marketing and SEO
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
- 31 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 15 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1052 tokens (~1052/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 Management97
- Stability observed for 29 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 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Stability: pass → 0.97 functional
- 13 Nov 26 0
- Stability: 0.97 → pass security
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 1.2.0 → 1.2.1 functional
- 4 Nov 26 −4
- Stability: pass → 0.70 functional
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 · Analysed npm/@mambalabsdev/mcp-creator-change-monitor@1.2.1
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 | 31 |
| Tree resolution | Complete |
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 →
monitor_influencer_changes Recheck an Influencer Watchlist for Changes ~1,052
Rereads a named watchlist of creator handles and compares every field against the state the previous run on that same list name recorded. Returns one row per change with change_type, change_from, change_to, and previous_run_at, alongside the creator handle, profile URL, follower count, newsletter status, bio link, and manager email. The first run on a new list name records the baseline and returns it, so there is something to compare against next time. Each list name keeps its own baseline, so one account can watch a client roster, a prospect list, and a competitor set without them mixing. Turning off the link recheck keeps the pass to profiles only, which is faster and cheaper on a large list. Charges $0.002 per run plus $0.008 per creator rechecked, $0.01 per change found, and $0.01 per Instagram bio fetch when one is needed. Contributes the public records in its rows to a shared creator pool, free and on by default; `contribute_to_shared_pool` explains it and turns it off. A run that does not succeed is returned as an error with its run ID and status. Use it to track creators you already know over time; to find new creators use Influencer Finder, and for a one off profile read use Influencer Profile Scraper. Requires an APIFY_TOKEN and consumes Apify credits. Reads public data only and writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_size | integer | – | Rows fetched at once. Leave empty for the measured per platform default; the measurement is in the README. Higher is faster and, above the measured point, loses rows. |
| check_links | boolean | – | Rechecks newsletter status, products, and manager contact on every run. Uncheck for a follower and bio link only check at lower cost: the link columns then keep the values from the last run that read… |
| contribute_to_shared_pool | boolean | – | On by default. Contributes the public records this run finds to a shared creator and agency pool that all users of this actor read from, so a later run reads what this one found. Only public data alr… |
| escalate_on_block | boolean | – | On by default. A profile fetch that comes back as a bot detection page is retried once over the residential proxy. On Instagram the bio, bio link, and following are read from the profile page over re… |
| handles | array | – | One per line. A profile URL on any supported platform (https://www.tiktok.com/@name, https://www.instagram.com/name/, https://www.youtube.com/@name, a Pinterest, Twitch, or Threads profile, an Apple… |
| list_name | string | – | Names the saved state. The first run for a list returns one first_seen row per creator as the baseline; later runs with the same name return only changes. Letters, digits, dot, dash, underscore. Defa… |
| match_agencies | boolean | – | Matches the domain of a manager or business email against the bundled talent agency list and fills agency_name, agency_domain, and agency_match_method. Charged per matched row (event agency-match). D… |
| max_charge_usd | number | – | Optional. The run stops before any charge that would take this run past this amount, delivers every row already charged, and drops the rest. Leave empty to rely only on the maximum cost per run set i… |
| platforms | array | – | Which platforms a bare @handle is looked up on. A full profile URL carries its own platform and ignores this. This actor does not search; pass the creators you want read. Supported: TikTok, Instagram… |
| twitch_app_token | string | – | Optional. An app access token for your Twitch client id (client credentials flow). Used only for Twitch reads, never stored or logged. |
| twitch_client_id | string | – | Optional. Your own registered Twitch application client id. With `twitch_app_token` the Twitch reads use the official Helix API instead of the public web endpoint. Never a Mamba Labs credential. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-creator-change-monitor server?
com.mambabuilt/mcp-creator-change-monitor runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-creator-change-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-creator-change-monitor
claude mcp add com-mambabuilt-mcp-creator-change-monitor -- npx -y @mambalabsdev/mcp-creator-change-monitor
What is the com.mambabuilt/mcp-creator-change-monitor server?
com.mambabuilt/mcp-creator-change-monitor is listed in the public MCP registry as com.mambabuilt/mcp-creator-change-monitor. Recheck a named influencer watchlist and return what moved since the run before it. This page covers its npm package (@mambalabsdev/mcp-creator-change-monitor).
Is the com.mambabuilt/mcp-creator-change-monitor server safe to use?
com.mambabuilt/mcp-creator-change-monitor scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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-creator-change-monitor server expose?
com.mambabuilt/mcp-creator-change-monitor exposes 1 tool: monitor_influencer_changes. Their descriptions and schemas cost roughly 1,052 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-creator-change-monitor server still maintained?
com.mambabuilt/mcp-creator-change-monitor 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 licence is the com.mambabuilt/mcp-creator-change-monitor server under?
com.mambabuilt/mcp-creator-change-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.
What did VerifyMCP test on the com.mambabuilt/mcp-creator-change-monitor server?
VerifyMCP ran 16 checks on com.mambabuilt/mcp-creator-change-monitor, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.