io.github.teamsincetoday/newsletter-commerce-mcp
NPM · NEWSLETTER-COMMERCE-MCP
Extract shoppable products from newsletter content with affiliate signals.
Available components
Last scanned (18 hours ago)
Scores higher than 56% 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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 52 of 129 dependencies flagged as unhealthy (1 deprecated). 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 230 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 607 tokens (~202/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 +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.
- 20 Nov 26 −1
- Stability: pass → 0.93 functional
- 14 Nov 26 0
- Stability: 0.97 → pass security
- 13 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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/newsletter-commerce-mcp@0.1.3
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 129 packages
| Packages resolved | 129 |
|---|---|
| Deprecated | 1 |
| Stale | 51 |
| 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 →
analyze_newsletter_sponsors ~221
Identify sponsored sections in a newsletter and estimate advertising value: CPM, read-through rate, and sponsor-reader fit score. Returns each sponsor's name, placement type (dedicated section, inline, footer), estimated CPM based on industry benchmarks, and audience fit score. Revenue estimates are benchmark averages — not live ad-platform data. Use for advertising intelligence, sponsor acquisition research, and ad placement optimization. Use this tool for sponsor metrics only; for the full affiliate product and link list use extract_newsletter_products instead. Reuses cached extraction when newsletter_id matches a prior extract_newsletter_products call. Example: newsletter_id='tldr-2026-03-12' → returns [{sponsor:'Warp', placement:'dedicated_section', estimated_cpm:40, fit_score:0.85}].
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional API key for paid access beyond the free tier |
| content | string | yes | Newsletter content as HTML or plain text |
| newsletter_id | string | – | Optional newsletter issue identifier — uses cached extraction if available |
No output schema declared.
No examples provided.
extract_newsletter_products ~217
Extract affiliate links, product recommendations, and sponsored mentions from newsletter content. Pass the newsletter body directly as HTML or plain text — does not fetch content from URLs. Supports Substack, Ghost, and Beehiiv HTML plus plain text. Returns product name, category, affiliate link URL, recommendation strength, and sponsor flag. Call this before analyze_newsletter_sponsors or track_product_trends — both tools reuse its cache. Use for monetization analysis, affiliate auditing, and cross-issue tracking. Example: newsletter_id='morning-brew-2026-03-12', category_filter=['saas','physical_goods'].
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional API key for paid access beyond the free tier |
| category_filter | array | – | Optional list of categories to include: saas, physical_goods, course, supplement, book, service, media, other |
| content | string | yes | Newsletter content as HTML or plain text |
| newsletter_id | string | – | Optional newsletter issue identifier for caching and trend tracking |
No output schema declared.
No examples provided.
track_product_trends ~169
Compare affiliate product mentions and brand frequency across multiple newsletter issues to detect rising, stable, and declining trends. Returns trend velocity, mention count per issue, and category breakdown. No AI call — computed from cached extraction data only. Use for affiliate marketing optimization, editorial product tracking, and sponsor category analysis. Requires prior extract_newsletter_products call for each newsletter_id — returns an error listing missing IDs if any are not in cache. Example: newsletter_ids=['issue-101','issue-102'].
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional API key for paid access beyond the free tier |
| category_filter | array | – | Optional category filter to narrow trend analysis |
| newsletter_ids | array | yes | List of newsletter issue IDs to analyze. Each must have been previously extracted via extract_newsletter_products. |
No output schema declared.
No examples provided.
How do I install the io.github.teamsincetoday/newsletter-commerce-mcp server?
io.github.teamsincetoday/newsletter-commerce-mcp runs locally as an npm package, launched with npx -y newsletter-commerce-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · newsletter-commerce-mcp
claude mcp add teamsincetoday-newsletter-commerce-mcp -- npx -y newsletter-commerce-mcp
What is the io.github.teamsincetoday/newsletter-commerce-mcp server?
io.github.teamsincetoday/newsletter-commerce-mcp is listed in the public MCP registry as io.github.teamsincetoday/newsletter-commerce-mcp. Extract shoppable products from newsletter content with affiliate signals. This page covers its npm package (newsletter-commerce-mcp).
Is the io.github.teamsincetoday/newsletter-commerce-mcp server safe to use?
io.github.teamsincetoday/newsletter-commerce-mcp scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 io.github.teamsincetoday/newsletter-commerce-mcp server expose?
io.github.teamsincetoday/newsletter-commerce-mcp exposes 3 tools: extract_newsletter_products, analyze_newsletter_sponsors, track_product_trends. Their descriptions and schemas cost roughly 607 tokens of context every time the server is loaded.
Is the io.github.teamsincetoday/newsletter-commerce-mcp server still maintained?
io.github.teamsincetoday/newsletter-commerce-mcp 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 io.github.teamsincetoday/newsletter-commerce-mcp server under?
io.github.teamsincetoday/newsletter-commerce-mcp 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 io.github.teamsincetoday/newsletter-commerce-mcp server?
VerifyMCP ran 16 checks on io.github.teamsincetoday/newsletter-commerce-mcp, 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.