# io.github.shashwatgtm/craft-gtm-mcp (remote · craft-gtm.gtmhelix.com)

CRAFT GTM: 8 go to market strategy tools by Helix GTM Consulting

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `craft-gtm.gtmhelix.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/shashwatgtm-craft-gtm-mcp/craft-gtm.md), [page](https://verifymcp.io/servers/shashwatgtm-craft-gtm-mcp/craft-gtm)
- npm · `@shashwatgtmalpha/craft-gtm-mcp`: 75/100, [markdown](https://verifymcp.io/servers/shashwatgtm-craft-gtm-mcp/shashwatgtmalpha-craft-gtm-mcp.md), [page](https://verifymcp.io/servers/shashwatgtm-craft-gtm-mcp/shashwatgtmalpha-craft-gtm-mcp)

## Channel facts

- Endpoint: `https://craft-gtm.gtmhelix.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.2.23`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3035 tokens (~379/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

io.github.shashwatgtm/craft-gtm-mcp is a hosted endpoint at https://craft-gtm.gtmhelix.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http shashwatgtm-craft-gtm-mcp 'https://craft-gtm.gtmhelix.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "shashwatgtm-craft-gtm-mcp": {
      "url": "https://craft-gtm.gtmhelix.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shashwatgtm-craft-gtm-mcp": {
      "type": "http",
      "url": "https://craft-gtm.gtmhelix.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.shashwatgtm-craft-gtm-mcp]
url = "https://craft-gtm.gtmhelix.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shashwatgtm-craft-gtm-mcp": {
      "type": "remote",
      "url": "https://craft-gtm.gtmhelix.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shashwatgtm-craft-gtm-mcp --url 'https://craft-gtm.gtmhelix.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  shashwatgtm-craft-gtm-mcp:
    url: "https://craft-gtm.gtmhelix.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "shashwatgtm-craft-gtm-mcp": {
      "Transport": "http",
      "Url": "https://craft-gtm.gtmhelix.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add shashwatgtm-craft-gtm-mcp -t streamable-http -u 'https://craft-gtm.gtmhelix.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "shashwatgtm-craft-gtm-mcp": {
      "type": "http",
      "url": "https://craft-gtm.gtmhelix.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 79, 0)

- [cosmetic] “launch_commander” reworded the description of “industry”
- [cosmetic] “partner_architect” reworded the description of “industry”
- [cosmetic] “pmf_scorecard” reworded the description of “target_market”
- [cosmetic] “retention_playbook” reworded the description of “industry”
- [cosmetic] “craft_gtm_analyzer” reworded the description of “industry”
- [cosmetic] “competitive_intel” reworded the description of “industry”

### 2026-11-01 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `pmf_scorecard` (~446 tokens)

PMF Scorecard

Takes your product, target market and current metrics (MRR, ACV, churn, NPS, CAC, LTV, retention, activation and similar) and returns a product-market fit scorecard that scores each dimension against example benchmark ranges. Reads the business model from your inputs and leaves the activation score out for services, connectivity and investment businesses. Quotes your customer feedback and answers it.

Input parameters:

- `business_model` (string): Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other in…
- `current_metrics` (string, required): Your current metrics, written as text (the tool reads the figures from it). Include any of: MRR, ARR, ACV, churn rate, NPS, CAC, LTV, retention rate, activation rate, DAU/MAU, trial conversion, reven…
- `customer_feedback` (string): Optional: Qualitative feedback themes, one per line or separated by semicolons (for example 'Customers like X; they struggle with Y'). Each theme is quoted and answered
- `product` (string, required): Product name and brief description
- `target_market` (string, required): Benchmark segment for scoring (for example enterprise SaaS, telecom or logistics tech). Ask the user to confirm it when it differs from the product description. The selected benchmark and its stated…
- `time_in_market` (string): How long the product has been in market (shown in the scorecard)
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

### `launch_commander` (~426 tokens)

Launch Commander

Takes what you are launching, the launch type, your target segments and your goals, and returns a phased launch plan with tasks, a messaging table and success metrics. Give a date for a dated timeline, or enter 'TBD' or a quarter such as 'Q2 2027' for a flexible plan. Tasks and the messaging table follow the sector and business model read from your inputs, and each goal is filed under its own metric.

Input parameters:

- `available_channels` (string): Optional: Marketing channels available (comma-separated). E.g., 'email, linkedin, blog, webinar, PR, paid_ads, community'
- `budget_level` (string): Budget affects recommended tactics
- `business_model` (string): Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other in…
- `goals` (string, required): Launch success metrics (for example '40 qualified meetings, $300K pipeline, 5 reference customers')
- `industry` (string): Optional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what i…
- `launch_date` (string): Target launch date. Accepts: 'YYYY-MM-DD', 'Q1 2027', 'March 2027', or 'TBD' for planning mode
- `launch_type` (string, required): Type of launch determines plan complexity
- `product_feature` (string, required): What you're launching (product/feature name and description)
- `target_segments` (string, required): Target customer segments (comma-separated)
- `team_size` (string): Marketing/GTM team size affects task distribution
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

### `customer_interview_kit` (~286 tokens)

Customer Interview Kit

Takes the interview type, the product context and the person you are interviewing, and returns an interview guide that fits the interview type, the sector (chosen, or read from your inputs) and the product complexity. Questions use the sector's own language, your hypotheses are kept whole, and synthesis templates are included.

Input parameters:

- `business_model` (string): Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other in…
- `industry` (string): Industry affects terminology and context. Leave it out and the sector is read from your other inputs
- `interview_type` (string, required): Type of interview determines question focus
- `key_hypotheses` (string): Optional: Hypotheses to validate during interview, one per line or separated by semicolons
- `product_complexity` (string): Affects technical depth of questions
- `product_context` (string, required): Product/service being researched
- `target_persona` (string, required): Who you're interviewing (role/title)
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

### `retention_playbook` (~398 tokens)

Retention Playbook

Takes your customer segment, business model and current churn rate, and returns a retention playbook with health signals, interventions and an email draft for each churn reason. If you do not know why customers leave, leave the churn reasons out and you get a churn discovery kit with a framework for finding out. Health signals and interventions follow the business model, each churn reason gets its own answer, and your current interventions and data signals are used.

Input parameters:

- `available_data_signals` (string): What you can track (comma-separated). E.g., 'login frequency, support tickets, SLA attainment, QBR attendance'
- `business_model` (string, required): Business model affects health score weighting. enterprise_contract is read further from your text when it names services, connectivity or investment
- `churn_reasons` (string): Optional: known churn reasons, comma-separated. If you do not know them, leave this blank and you get a churn discovery kit with a framework for finding the reasons
- `cs_team_size` (string): CS team capacity affects intervention strategy
- `current_churn_rate` (string, required): Current churn rate (e.g., '5%' or '5% monthly')
- `current_interventions` (string): Optional: What retention tactics you already do (listed and compared with the playbook)
- `customer_segment` (string, required): Customer segment to focus on
- `industry` (string): Optional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what i…
- `product` (string): Optional: Your product or company name, used in the title and the email drafts
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

### `partner_architect` (~392 tokens)

Partner Architect

Takes your company, product, partner model, partner goal and deal size, and returns a partner program with tiers, example commission amounts and KPIs, with a different structure for resellers, referrals, integrations, agencies, affiliates and white label. Uses your stated goal, existing partners and deal size, and names the partner types that fit your sector's buying committee.

Input parameters:

- `business_model` (string): Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other in…
- `company` (string, required): Your company name
- `existing_partners` (string): Optional: Current partner types/count, one per line or separated by semicolons (listed in the plan)
- `industry` (string): Optional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what i…
- `partner_goals` (string, required): Revenue/growth targets from partners (shown as the target of the first KPI row)
- `partner_model` (string, required): Partner type determines program structure
- `partner_support_capacity` (string): How much partner support can you provide?
- `product` (string, required): Product partners will sell/integrate
- `your_deal_size` (string, required): Average deal size as one amount (e.g., '$5000 ACV', '$5K' or '$500/month'; a range is refused). It scales the example commission amounts; the example rates are fixed
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

### `crisis_planner` (~374 tokens)

Crisis Planner

Takes your company, industry, customer base and data sensitivity, and returns crisis playbooks with a response team and notification steps for each crisis. Name the crises you know of to get those playbooks. If you leave them out, the tool uses a default set of common crises for your sector (not ranked by likelihood). Each compliance item you list is used in the notification steps.

Input parameters:

- `business_model` (string): Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other in…
- `company` (string, required): Company name
- `company_size` (string): Affects response team structure
- `compliance_requirements` (string): Optional: Relevant compliance, comma-separated (for example ISO 27001, SOC 2, GDPR). Each item is named in the notification steps
- `customer_base` (string, required): Customer type affects communication approach
- `data_sensitivity` (string, required): Data sensitivity affects security protocols
- `industry` (string, required): Industry affects which crises to prioritize
- `potential_crises` (string): Optional: crisis types to plan for, comma-separated. If not provided, the tool uses a default set of common crises for your sector (not ranked by likelihood). Options: data_breach, service_outage, sl…
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

### `competitive_intel` (~454 tokens)

Competitive Intel

Takes your product and the competitors you name, and returns one battle card per competitor built from your strengths, weaknesses, competitor details, objections, wins and losses. Each competitor detail goes to the competitor it names, each objection gets its own answer, and strengths and gaps taken from wins and losses are your own words.

Input parameters:

- `business_model` (string): Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other in…
- `common_objections` (string): Sales objections you hear (comma-separated). E.g., 'too expensive, missing X feature, competitor has better Y'
- `competitor_details` (string): Optional: Any known details about competitors, one per line or separated by semicolons. E.g., 'Competitor A is cheaper; Competitor B targets enterprise'. Each detail goes to the competitor it names
- `competitors` (string, required): Competitor names, comma-separated. You get one battle card for each competitor named
- `industry` (string): Optional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what i…
- `recent_losses` (string): Why you lost deals to competitors: used as your gaps when none are given
- `recent_wins` (string): Why customers chose you over competitors: used as your strengths when none are given
- `your_product` (string, required): Your product name and brief description
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_strengths` (string): Optional: what you do better, comma-separated. Taken from your wins, in your own words, if not provided
- `your_weaknesses` (string): Optional: where competitors beat you, comma-separated. Taken from your losses, in your own words, if not provided

### `craft_gtm_analyzer` (~259 tokens)

CRAFT GTM Analyzer

Takes the text of a GTM document or plan and returns an analysis against the CRAFT framework, with a score for each dimension. Each dimension is scored only on what the plan contains (Timeline counts real dates, durations and quarters), the tool shows the plan's own line for each, names only the elements that are missing and suggests sections to add.

Input parameters:

- `desired_outcome` (string): Optional: What action should this document drive
- `document_content` (string, required): The GTM document or plan to analyze. Paste the full text: the tool reads it and scores it against the framework
- `document_type` (string, required): Type of document (shown in the analysis)
- `industry` (string): Optional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what i…
- `intended_audience` (string): Optional: Who will read/approve this document
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/shashwatgtm-craft-gtm-mcp/craft-gtm#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 73
- 2026-10-19: 73
- 2026-10-18: 72
- 2026-10-17: 72

## Common questions

### 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. CRAFT GTM: 8 go to market strategy tools by Helix GTM Consulting. This page covers its hosted endpoint (https://craft-gtm.gtmhelix.com/mcp).

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

io.github.shashwatgtm/craft-gtm-mcp scores 80 out of 100 on VerifyMCP. 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 3,035 tokens of context every time the server is loaded.

### Does the io.github.shashwatgtm/craft-gtm-mcp server require authentication?

No. We connected to io.github.shashwatgtm/craft-gtm-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://craft-gtm.gtmhelix.com/mcp
- Repository: https://github.com/shashwatgtm/craft-gtm-mcp
- Website: https://tools.gtmhelix.com/connectors/
- Changelog RSS feed: https://verifymcp.io/servers/shashwatgtm-craft-gtm-mcp/craft-gtm.xml
- Changelog JSON feed: https://verifymcp.io/servers/shashwatgtm-craft-gtm-mcp/craft-gtm.json
- HTML version of this page: https://verifymcp.io/servers/shashwatgtm-craft-gtm-mcp/craft-gtm