com.mambabuilt/mcp-newsletter-sponsor-tracker
NPM · @MAMBALABSDEV/MCP-NEWSLETTER-SPONSOR-TRACKER
Who sponsors a newsletter, or which newsletters a brand sponsors, from public archives.
Available components
Last scanned (6 hours ago)
Scores higher than 25% 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 Security13
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
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 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 441 tokens (~441/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 Management33
- Stability observed for 10 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 (13)
- Install scripts
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (3)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
- Known CVEs in Supply Chain SecurityKnown CVEs could not be checked: the version this server declares is not published in its registry.
- Dependency health in Supply Chain SecurityDependency health could not be checked: the version this server declares is not published in its registry.
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.
- 5 Nov 26 −25
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 1.0.0 → 1.0.1 functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 54
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 5 Nov 2026 · Analysed npm/@mambalabsdev/mcp-newsletter-sponsor-tracker@1.0.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 →
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 →
track_newsletter_sponsors Track newsletter sponsors ~441
Find who sponsors a newsletter, or which newsletters a brand sponsors, from public newsletter archives (Substack archive JSON, beehiiv and other sitemaps, RSS). mode newsletter: give newsletter_urls (for example notboring.co) and get one row per sponsor found in the newest issues, with sponsor name, domain, link without tracking, placements, share of issues, first and last issue seen, and issue links, plus one free summary row per newsletter. mode brand: give brand_name and brand_domain (for example Attio, attio.com) and get the newsletters whose recent issues carry a sponsor placement for the brand, found through Google results and confirmed in each newsletter's own issues. A placement is a short block with a sponsor label (presented by, brought to you by, sponsored by, together with) and the first outside link beside it. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per sponsor row and, in brand mode, one brand search event.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_domain | string | – | Brand mode. The sponsor domain, for example attio.com. |
| brand_name | string | – | Brand mode. The sponsor name as newsletters print it, for example Attio. |
| issues_to_scan | string | – | Newest issues read per newsletter, 1 to 200; at most 20 in brand mode. Default 20. |
| max_charge_usd | string | – | Optional. The run stops before any row that would take its charges over this amount. |
| mode | string | – | newsletter (default): newsletter links in, sponsors out. brand: a brand in, the newsletters that ran its placements out. |
| newsletter_urls | array | – | Newsletter mode. Home page links or domains, up to 100, for example notboring.co. |
| newsletters_to_check | string | – | Brand mode. Candidate newsletters to confirm, 1 to 10. Default 10. |
| since_days | string | – | Stop at issues older than this many days. 0: no limit. Default 365. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-newsletter-sponsor-tracker server?
com.mambabuilt/mcp-newsletter-sponsor-tracker runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-newsletter-sponsor-tracker. 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-newsletter-sponsor-tracker
claude mcp add com-mambabuilt-mcp-newsletter-sponsor-tracker -- npx -y @mambalabsdev/mcp-newsletter-sponsor-tracker
What is the com.mambabuilt/mcp-newsletter-sponsor-tracker server?
com.mambabuilt/mcp-newsletter-sponsor-tracker is listed in the public MCP registry as com.mambabuilt/mcp-newsletter-sponsor-tracker. Who sponsors a newsletter, or which newsletters a brand sponsors, from public archives. This page covers its npm package (@mambalabsdev/mcp-newsletter-sponsor-tracker).
Is the com.mambabuilt/mcp-newsletter-sponsor-tracker server safe to use?
com.mambabuilt/mcp-newsletter-sponsor-tracker scores 48 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 com.mambabuilt/mcp-newsletter-sponsor-tracker server expose?
com.mambabuilt/mcp-newsletter-sponsor-tracker exposes 1 tool: track_newsletter_sponsors. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-newsletter-sponsor-tracker server still maintained?
com.mambabuilt/mcp-newsletter-sponsor-tracker is still listed as active in the MCP registry. We last reached this channel on 5 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-newsletter-sponsor-tracker server under?
com.mambabuilt/mcp-newsletter-sponsor-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.
What did VerifyMCP test on the com.mambabuilt/mcp-newsletter-sponsor-tracker server?
VerifyMCP ran 13 checks on com.mambabuilt/mcp-newsletter-sponsor-tracker, covering Install scripts, Source repository, Provenance, License and 9 more. 3 items could not be completed, a gap on our side rather than a finding about com.mambabuilt/mcp-newsletter-sponsor-tracker: Malware scan, Known CVEs and Dependency health. 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.