io.github.teamsincetoday/newsletter-commerce-mcp
NPM · NEWSLETTER-COMMERCE-MCP · SCANNED AUG 3
Extract shoppable products from newsletter content with affiliate signals.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (131 of 135), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (131 of 135), 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 120 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).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 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
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.
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.
npm · newsletter-commerce-mcp
claude mcp add teamsincetoday-newsletter-commerce-mcp -- npx -y newsletter-commerce-mcp
codex mcp add teamsincetoday-newsletter-commerce-mcp -- npx -y newsletter-commerce-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"teamsincetoday-newsletter-commerce-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"newsletter-commerce-mcp"
],
"enabled": true
}
}
} openclaw mcp add teamsincetoday-newsletter-commerce-mcp --command npx --arg -y --arg newsletter-commerce-mcp
mcp_servers:
teamsincetoday-newsletter-commerce-mcp:
command: "npx"
args: ["-y", "newsletter-commerce-mcp"] {
"mcpServers": {
"teamsincetoday-newsletter-commerce-mcp": {
"command": "npx",
"args": [
"-y",
"newsletter-commerce-mcp"
]
}
}
} 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.
- 3 Aug 26 +15
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 2 Aug 26 +43
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 1 Aug 26 −28
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 31 Jul 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −39
- Known CVEs: partial → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- License: pass → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: MIT functional
- 28 Jul 26 +50
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- Licence: MIT functional
- 27 Jul 26 26
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 131 packages
131 packages in the resolved dependency tree · 131 deprecated · 49 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.