io.github.shashwatgtm/craft-gtm-mcp
NPM · @SHASHWATGTMALPHA/CRAFT-GTM-MCP · SCANNED SEP 22
8 strategic GTM tools: PMF, Launch, Interviews, Retention, Partners, Crisis, Competitive Intel
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 → 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 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
- 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 248 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1020 tokens (~127/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 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 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
How do I install the io.github.shashwatgtm/craft-gtm-mcp server?
io.github.shashwatgtm/craft-gtm-mcp runs locally as an npm package, launched with npx -y @shashwatgtmalpha/craft-gtm-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-gtm-mcp
claude mcp add shashwatgtm-craft-gtm-mcp -- npx -y @shashwatgtmalpha/craft-gtm-mcp
{
"mcpServers": {
"shashwatgtm-craft-gtm-mcp": {
"command": "npx",
"args": [
"-y",
"@shashwatgtmalpha/craft-gtm-mcp"
]
}
}
} {
"servers": {
"shashwatgtm-craft-gtm-mcp": {
"command": "npx",
"args": [
"-y",
"@shashwatgtmalpha/craft-gtm-mcp"
]
}
}
} codex mcp add shashwatgtm-craft-gtm-mcp -- npx -y @shashwatgtmalpha/craft-gtm-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shashwatgtm-craft-gtm-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@shashwatgtmalpha/craft-gtm-mcp"
],
"enabled": true
}
}
} openclaw mcp add shashwatgtm-craft-gtm-mcp --command npx --arg -y --arg @shashwatgtmalpha/craft-gtm-mcp
mcp_servers:
shashwatgtm-craft-gtm-mcp:
command: "npx"
args: ["-y", "@shashwatgtmalpha/craft-gtm-mcp"] {
"McpServers": {
"shashwatgtm-craft-gtm-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@shashwatgtmalpha/craft-gtm-mcp"
]
}
}
} assistant mcp add shashwatgtm-craft-gtm-mcp -t stdio -c npx -a -y @shashwatgtmalpha/craft-gtm-mcp
{
"mcpServers": {
"shashwatgtm-craft-gtm-mcp": {
"command": "npx",
"args": [
"-y",
"@shashwatgtmalpha/craft-gtm-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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.77 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
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 22 Sept 2026 · Analysed npm/@shashwatgtmalpha/craft-gtm-mcp@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 →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
competitive_intel ~113
Competitive Intelligence Package: Generate battle cards per competitor, feature comparison matrix, win/loss framework, positioning map, trap questions, objection handlers, competitive response playbook, and monitoring system.
| Name | Type | Req | Description |
|---|---|---|---|
| common_objections | string | – | Objections in competitive deals |
| competitors | string | yes | 3-5 key competitors (comma-separated) |
| market | string | yes | Target market |
| your_differentiators | string | yes | Your unique value propositions |
| your_product | string | yes | Your product name and description |
No output schema declared.
No examples provided.
craft_gtm_analyzer ~113
CRAFT Strategy Analyzer: Analyze any GTM strategy document against CRAFT principles (Character, Result, Artifact, Frame, Timeline). Returns CRAFT score 0-100, dimension assessment, gap analysis, and improvement recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| desired_outcome | string | – | What it should achieve |
| document_content | string | yes | Strategy document to analyze |
| document_type | string | yes | Type: GTM plan, launch plan, positioning |
| intended_audience | string | – | Who will use this document |
No output schema declared.
No examples provided.
crisis_planner ~114
Crisis Response Framework: Generate crisis playbook with 4 severity levels, stakeholder communication matrix, response team structure, crisis-specific playbooks (security breach, outage, PR), statement templates, FAQ bank, and post-crisis review process.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name |
| industry | string | yes | Industry/sector |
| potential_crises | string | yes | Types: product issues, security, PR, operational |
| spokesperson | string | – | Who speaks for company |
| stakeholders | string | – | Key stakeholders |
No output schema declared.
No examples provided.
customer_interview_kit ~128
Customer Research Framework: Generate complete interview kit with 5-phase script, question bank by category (JTBD, pain points, value, competition, decisions), follow-up prompts, insight synthesis template, and cross-interview pattern analysis framework.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_segment | string | yes | Specific persona/segment to interview |
| duration | string | – | Target interview length |
| interview_type | string | yes | Type: discovery, validation, feedback, churn |
| key_questions | string | – | Primary research questions (2-3) |
| research_objective | string | yes | What you're trying to learn |
No output schema declared.
No examples provided.
launch_commander ~147
Launch Sequence Planner: Generate complete 12-week launch plan with week-by-week timeline (6 weeks pre-launch, launch week, 4 weeks post), hour-by-hour launch day schedule, channel coordination, RACI matrix, contingency plans, and success metrics dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | Available budget |
| channels | string | – | Available channels: marketing, sales, PR, partners |
| goals | string | yes | Launch objectives and success metrics |
| launch_date | string | yes | Target launch date |
| product_feature | string | yes | Product/feature being launched |
| target_segments | string | yes | Primary and secondary audience segments |
| team | string | – | Team members and roles |
No output schema declared.
No examples provided.
partner_architect ~132
Partner Program Framework: Design complete partner program with 4-tier structure (Registered→Silver→Gold→Platinum), commission model, enablement curriculum, recruitment playbook, joint business planning template, and success metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Your company name |
| current_partnerships | string | – | Existing partnerships |
| partner_goals | string | yes | What you want to achieve via partners |
| partner_types | string | yes | Types: resellers, integrations, referrals, agencies |
| product | string | yes | Product/service for partnership |
| resources | string | – | Team and budget for partner program |
No output schema declared.
No examples provided.
pmf_scorecard ~149
Product-Market Fit Assessment: Generate comprehensive PMF scorecard with 5-dimension analysis (Market Demand 25%, Customer Satisfaction 25%, Competitive Position 20%, Product Performance 20%, Market Validation 10%), weighted scoring 0-100, gap identification, and 90-day action plan.
| Name | Type | Req | Description |
|---|---|---|---|
| current_metrics | string | yes | Key metrics: MRR, churn, NPS, CAC, LTV, growth rate |
| customer_feedback | string | – | Qualitative insights from customers |
| product | string | yes | Product/service name and brief description |
| target_market | string | yes | Specific market segment you're targeting |
| time_in_market | string | – | How long since launch |
No output schema declared.
No examples provided.
retention_playbook ~124
Retention Strategy Framework: Generate comprehensive retention system with customer health score model (5 components, 100 points), intervention playbooks by segment (healthy/at-risk/critical), early warning alerts, save playbooks with email templates, and success metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| churn_reasons | string | yes | Known primary churn factors |
| current_churn_rate | string | yes | Current churn rate and timeframe |
| customer_lifecycle | string | – | Typical journey stages |
| customer_segment | string | yes | Customer segment to focus on |
| resources | string | – | CS team size and tools |
No output schema declared.
No examples provided.
What is the io.github.shashwatgtm/craft-gtm-mcp server?
io.github.shashwatgtm/craft-gtm-mcp is listed in the public MCP registry as io.github.shashwatgtm/craft-gtm-mcp. 8 strategic GTM tools: PMF, Launch, Interviews, Retention, Partners, Crisis, Competitive Intel. This page covers its npm package (@shashwatgtmalpha/craft-gtm-mcp).
Is the io.github.shashwatgtm/craft-gtm-mcp server safe to use?
io.github.shashwatgtm/craft-gtm-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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-gtm-mcp server expose?
io.github.shashwatgtm/craft-gtm-mcp exposes 8 tools: pmf_scorecard, launch_commander, customer_interview_kit, retention_playbook, partner_architect, and 3 more. Their descriptions and schemas cost roughly 1,020 tokens of context every time the server is loaded.
Is the io.github.shashwatgtm/craft-gtm-mcp server still maintained?
io.github.shashwatgtm/craft-gtm-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 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-gtm-mcp server under?
io.github.shashwatgtm/craft-gtm-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.