Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.closermethod/newsletter-growth-mcp

NPM · NEWSLETTER-GROWTH-MCP · SCANNED AUG 3

Newsletter growth loops, welcome-sequence architecture, subject-line and list-metric guidance.

+20 this week 64 Trust /100
Trust breakdown (6 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 →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), 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 (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 337 tokens (~56/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

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-growth-mcp

# add to Claude Code
claude mcp add closermethod-newsletter-growth-mcp -- npx -y newsletter-growth-mcp
# add to Codex CLI
codex mcp add closermethod-newsletter-growth-mcp -- npx -y newsletter-growth-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "closermethod-newsletter-growth-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "newsletter-growth-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add closermethod-newsletter-growth-mcp --command npx --arg -y --arg newsletter-growth-mcp
# ~/.hermes/config.yaml
mcp_servers:
  closermethod-newsletter-growth-mcp:
    command: "npx"
    args: ["-y", "newsletter-growth-mcp"]
// mcp.json
{
  "mcpServers": {
    "closermethod-newsletter-growth-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "newsletter-growth-mcp"
      ]
    }
  }
}
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.

  • 2 Aug 26 +45
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Tool coverage: 100 → unverified functional
    • License: unverified → pass functional
    • Schema quality: unverified → fair functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Dependency health: unverified → partial functional
    • Licence: MIT functional
  • 31 Jul 26 −5
    • 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 −20
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 44

    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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~337 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.

Tool Tokens
audit_subject_line ~49

Audit an email subject line: mobile truncation length, all-caps, spam phrases, fake Re:/Fwd:, specificity. Returns PASS/NEEDS WORK.

NameTypeReqDescription
subjectstringyes

No output schema declared.

No examples provided.

get_full_pack ~26

The complete newsletter library in one payload: growth loops, welcome sequence, metric reads.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_growth_loop ~64

Get a newsletter growth loop with mechanism, when it wins, execution rules, and failure mode. Loops: lead_magnet, social_repurpose, cross_promo, referral, sponsorship_swap. Omit for all loops + selection logic.

NameTypeReqDescription
loopstring

No output schema declared.

No examples provided.

get_monetization_readiness ~98

Given subscriber count (and optionally open/click rates as percents), returns readiness verdicts for the three monetization paths: own product, per-click sponsorships, flat-rate placements, with sequencing. Engagement monetizes; size impresses.

NameTypeReqDescription
click_ratenumberOptional: average click rate percent
open_ratenumberOptional: average open rate percent
subscribersnumberyesCurrent list size

No output schema declared.

No examples provided.

get_welcome_sequence ~50

The 6-email welcome sequence architecture: per-email job, timing, and subject shape (deliver → receipt → quick win → segment → soft offer → close), plus the one-job-per-email rules.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

interpret_list_metric ~50

Interpret a list metric against practitioner ranges: open_rate, click_rate, growth_rate, unsubscribe_rate, reply_rate. Returns healthy range, warning threshold, and the diagnostic.

NameTypeReqDescription
metricstringyes

No output schema declared.

No examples provided.