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

io.github.shashwatgtm/craft-content-mcp

NPM · @SHASHWATGTMALPHA/CRAFT-CONTENT-MCP · 2 COMPONENTS

CRAFT Content: 8 B2B content tools by Helix GTM Consulting

+5 this week 82 Trust /100

Last scanned (15 hours ago)

Scores higher than 71% of npm servers

Category Marketing and SEO

Trust breakdown (7 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 → 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 & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1443 tokens (~180/item across 8 items; 8 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

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 →

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.

  • 18 Nov 26 +5
    • Stability: fail → pass ▲ security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 62 to 65.

  • 10 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 69 to 62.

  • 9 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 4 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 3 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 1 Nov 26 0
    • Package version: 1.0.1 → 2.2.22 functional
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 21 Nov 2026 · Analysed npm/@shashwatgtmalpha/craft-content-mcp@2.2.22

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 →

MCP tools · 8 exposed · ~1,443 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. 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 →

Tool Tokens
case_study_generator ~195

Generate case studies with DISCOVERY MODE. If you have the full story, get a complete case study. If not, get interview questions to gather the story first.

NameTypeReqDescription
challengestring–The customer's challenge/problem (required for full mode)
customer_industrystring–Customer's industry for context
customer_namestringyesCustomer/company name
customer_quotestring–Optional: Direct quote from customer
interview_notesstring–Optional: Raw interview notes or transcript. Parsed into a case study when mode is 'full'
modestring–full = generate case study (requires challenge/solution/results), discovery = generate interview questions to gather story
resultsstring–Quantifiable outcomes (required for full mode)
solutionstring–How your product solved it (required for full mode)
your_productstringyesYour product/service name

No output schema declared.

No examples provided.

content_repurposer ~160

Transform source content into multiple formats. Just paste content: we'll generate the 5 most useful formats by default, or specify exactly what you need.

NameTypeReqDescription
brand_voicestring–Brand voice to maintain
key_messagestring–Optional: Core message to emphasize across all formats
source_contentstringyesOriginal content to repurpose (blog post, article, transcript, etc.)
source_typestringyesWhat type of content is the source
target_formatsstring–OPTIONAL: Formats to generate (comma-separated). Defaults to: linkedin_post, twitter_thread, email, blog_summary, quote_cards. Other options: infographic_outline, video_script, podcast_talking_points…

No output schema declared.

No examples provided.

craft_content_improver ~157

Analyze content for clarity, structure and engagement, score each area, and return suggestions, including a version with common jargon replaced and long sentences split.

NameTypeReqDescription
audiencestring–OPTIONAL: Who is this content for? Helps tailor improvements.
contentstringyesContent to analyze
content_typestringyesType of content affects evaluation criteria
goalstring–OPTIONAL: What should this content achieve? (e.g., 'drive signups', 'educate readers'). If not given, a goal is chosen from the content type (for example 'Get meetings booked' for a sales email)
tone_preferencestring–Desired tone (accepted for compatibility; it does not change the analysis)

No output schema declared.

No examples provided.

newsletter_builder ~164

Build newsletter content. Just have a topic? We'll suggest key points. Have key points? We'll craft the content.

NameTypeReqDescription
audience_segmentstring–Audience segment affects tone and depth
cta_goalstringyesWhat action should readers take? (e.g., 'sign up for webinar', 'try feature', 'read blog')
key_pointsstring–OPTIONAL: Key points to cover (comma-separated). If not provided, the tool suggests 5 points based on the topic and newsletter type
newsletter_typestring–Type of newsletter
previous_topicsstring–Optional: Recent newsletter topics to avoid repetition and suggest connections
tonestring–Writing tone
topicstringyesMain topic/theme of the newsletter

No output schema declared.

No examples provided.

sales_enablement_content ~217

Generate sales content. Know your objections? Get complete handlers. New product with no sales data yet? We'll suggest likely objections based on your product type.

NameTypeReqDescription
common_objectionsstring–OPTIONAL: Sales objections you hear (comma-separated). If not provided, we'll suggest likely objections for your product type
competitor_objectionsstring–Optional: 'Why not [competitor]' objections
price_contextstring–Optional: Your pricing vs market (e.g., 'Premium, 20% above market', 'Budget option', 'Mid-market')
productstringyesProduct name and what it does
proof_pointsstringyesEvidence for claims: case studies, metrics, quotes (comma-separated)
sales_stagestring–What stage of sales funnel
target_personastringyesWho sales is pitching to (role, company type)
value_propsstring–OPTIONAL: Key value propositions (comma-separated). Will be DERIVED from proof points if not provided

No output schema declared.

No examples provided.

testimonial_capture ~139

Generate testimonial request emails, interview questions, and formatted outputs. Discovery-focused by design.

NameTypeReqDescription
customer_companystringyesCustomer's company
customer_namestringyesCustomer name
customer_rolestring–Customer's job title
incentivestring–Optional: What you're offering in return
relationship_contextstring–How long they've been a customer, key interactions
success_storystringyesBrief description of their success with your product
testimonial_typestringyesType of testimonial needed
use_casestring–Where will this testimonial be used? (website, sales deck, etc.)

No output schema declared.

No examples provided.

thought_leadership_series ~231

Generate thought leadership article drafts (about 600 to 800 words each) from your topic, your take and your proof points. Without proof points, the drafts include suggested proof points to gather. Drafts contain placeholders to complete before publishing.

NameTypeReqDescription
article_typestring–Style of articles
author_backgroundstring–Optional: Your role and why you're credible (e.g., '15 years in enterprise sales')
num_articlesnumber–Number of articles to generate (1-5)
proof_pointsstring–OPTIONAL: Evidence supporting your take: personal stories, client examples, data/stats (comma-separated). If not provided, we'll suggest proof points to gather
target_readerstringyesWho should read this? Be specific (e.g., 'B2B SaaS founders struggling with churn' not just 'marketers')
topicstringyesThe topic you want to establish authority on
your_takestringyesYour unique perspective or opinion on this topic. What do you believe that others don't? What's your contrarian view?

No output schema declared.

No examples provided.

webinar_script ~180

Generate webinar scripts. Know your takeaways? Get a complete script. Still planning? We'll suggest takeaways based on topic and type.

NameTypeReqDescription
durationstring–Webinar length
include_pollsboolean–Include interactive poll suggestions
key_takeawaysstring–OPTIONAL: 3-5 things attendees should learn (comma-separated). If not provided, we'll suggest based on topic
product_mention_levelstring–Whether to add product tie-in placeholders to the script ('none' leaves them out)
speakersstring–Optional: Speaker names and titles (comma-separated)
target_audiencestringyesWho will attend (e.g., 'Marketing managers at B2B SaaS companies')
topicstringyesWebinar topic/title
webinar_typestringyesType of webinar determines structure

No output schema declared.

No examples provided.

Install

How do I install the io.github.shashwatgtm/craft-content-mcp server?

io.github.shashwatgtm/craft-content-mcp runs locally as an npm package, launched with npx -y @shashwatgtmalpha/craft-content-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 · @shashwatgtmalpha/craft-content-mcp

# add to Claude Code
claude mcp add shashwatgtm-craft-content-mcp -- npx -y @shashwatgtmalpha/craft-content-mcp
Common questions

What is the io.github.shashwatgtm/craft-content-mcp server?

io.github.shashwatgtm/craft-content-mcp is listed in the public MCP registry as io.github.shashwatgtm/craft-content-mcp. CRAFT Content: 8 B2B content tools by Helix GTM Consulting. This page covers its npm package (@shashwatgtmalpha/craft-content-mcp).

Is the io.github.shashwatgtm/craft-content-mcp server safe to use?

io.github.shashwatgtm/craft-content-mcp 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 io.github.shashwatgtm/craft-content-mcp server expose?

io.github.shashwatgtm/craft-content-mcp exposes 8 tools: case_study_generator, newsletter_builder, webinar_script, content_repurposer, thought_leadership_series, and 3 more. Their descriptions and schemas cost roughly 1,443 tokens of context every time the server is loaded.

Is the io.github.shashwatgtm/craft-content-mcp server still maintained?

io.github.shashwatgtm/craft-content-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.shashwatgtm/craft-content-mcp server under?

io.github.shashwatgtm/craft-content-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.shashwatgtm/craft-content-mcp server?

VerifyMCP ran 16 checks on io.github.shashwatgtm/craft-content-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.