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

IMPACT: 8 B2B positioning and messaging tools by Helix GTM Consulting

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

## Components

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

## Channel facts

- Endpoint: `https://impact.gtmhelix.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.2.27`

## 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**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2620 tokens (~291/item across 9 items; 8 tools + 1 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.
  - Structured output schemas are declared (13% of tools); any adoption earns full credit.
- **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 10 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.
  - Supports UI / widget rendering.

## Install

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

io.github.shashwatgtm/impact-mcp is a hosted endpoint at https://impact.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-impact-mcp 'https://impact.gtmhelix.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "shashwatgtm-impact-mcp": {
      "type": "http",
      "url": "https://impact.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 83, +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-03 (score 82, 0)

- [security] Resource “Impact Full Audit result” now points somewhere else: ui://helix-wave3-f166d12d8c05/impact_full_audit.html → ui://helix-wave3-6b8120611bee/impact_full_audit.html

### 2026-11-02 (score 82, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “impact_full_audit” rewrote its description, which is the text the model reads
- [functional improvement] Tool “impact_full_audit” now declares an output schema
- [functional] The server now declares the “resources” capability
- [functional] First check of Schema quality: 100
- [functional] First check of Tool coverage: 13
- [functional] First check of Capabilities: pass
- [functional] Schema quality: excellent → good
- [functional] New resource “Impact Full Audit result”
- [cosmetic] “impact_anchor_market” reworded the description of “current_customers”
- [cosmetic] “impact_anchor_market” reworded the description of “customer_pain”
- [cosmetic] “impact_full_audit” reworded the description of “customer_feedback”
- [cosmetic] “impact_full_audit” reworded the description of “key_differentiation”
- [cosmetic] “impact_full_audit” reworded the description of “product_description”
- [cosmetic] “impact_full_audit” reworded the description of “target_customer”
- [cosmetic] “impact_get_framework” reworded the description of “sector”
- [cosmetic] “impact_full_audit” reworded the description of “problem_solved”

### 2026-10-31 (score 79, +1)

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

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

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

### 2026-10-28 (score 77, 0)

- [security] Tool “impact_craft_message” rewrote its description, which is the text the model reads
- [security] Tool “impact_full_audit” rewrote its description, which is the text the model reads
- [security] Tool “impact_get_framework” rewrote its description, which is the text the model reads
- [security] Tool “impact_identify_champions” rewrote its description, which is the text the model reads
- [security] Tool “impact_map_alternatives” rewrote its description, which is the text the model reads
- [security] Tool “impact_pinpoint_value” rewrote its description, which is the text the model reads
- [security] Tool “impact_translate_execution” rewrote its description, which is the text the model reads
- [security] Tool “impact_anchor_market” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 242 → 302
- [functional] Schema quality: good → excellent
- [cosmetic] “impact_anchor_market” reworded the description of “potential_segments”

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

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

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

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

## MCP tools (8)

### `impact_get_framework` (~209 tokens)

IMPACT Framework Guide

Returns the IMPACT positioning method step by step: identify champions, map alternatives, pinpoint value, anchor in a market, craft the message and translate it to execution, with a template or checklist for each step. An optional focus phase returns one step only, and your sector adds that sector's buyer roles, measures and proof points.

Input parameters:

- `focus_phase` (string): Specific phase to focus on (identify/map/pinpoint/anchor/craft/translate)
- `sector` (string): Your sector in your own words (for example logistics tech, fintech, SaaS, vertical SaaS, AI native, IT services, telecom, software or cybersecurity). Adds how the six steps read in that sector. The s…
- `your_sector` (string): 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.

### `impact_identify_champions` (~250 tokens)

Identify Champions

Takes what your product does and the problem it solves, and returns hypotheses for who buys it: the champion, the economic buyer, the technical influencer, commercial and control reviewers and daily users, with warning signs of an anti-champion, a path to develop the champion and what to give them. Optional company name, target company type, price point and sector fit the roles to your market. These are roles to test, not named people.

Input parameters:

- `company_name` (string): Your company name
- `price_point` (string): What you charge, with the period, in your own words (for example "$50,000 a year" or "$3,750 per month")
- `problem_solved` (string, required): The core problem you solve
- `product_description` (string, required): What your product does (1-2 sentences)
- `target_company_type` (string): Type of companies you target (e.g., "mid-size fintech companies", "enterprise manufacturers")
- `your_sector` (string): 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.

### `impact_map_alternatives` (~275 tokens)

Map Alternatives

Takes your product and its category, and returns a map of the alternatives your buyers weigh: one card for each competitor you name, the status-quo options you list and doing nothing, where you can lead, and discovery questions to learn more. Optional competitor weaknesses and your strengths fill the cards, and your sector adds its questions and objections. It uses only what you give and says what would sharpen the map.

Input parameters:

- `category` (string, required): Your product category (e.g., "cloud security monitoring", "last-mile delivery software")
- `competitor_weaknesses` (string): Known competitor weaknesses or customer complaints, one per line or separated by semicolons. A weakness that names a competitor is shown on its card
- `competitors` (array): List of competitor names, and the status-quo options your buyers use (for example "spreadsheets"). A description in brackets after a name is kept
- `your_product` (string, required): What your product does
- `your_sector` (string): 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): What you do better than competitors, one per line or separated by semicolons

### `impact_pinpoint_value` (~284 tokens)

Pinpoint Value

Takes your target customer, the main outcome they get and what you do that others do not, and returns value proposition statements in three versions, a value matrix for your own figures, proof points ranked from customer results to social proof, versions for different audiences and channels, and questions to test the value. Optional product name, category, customer results and business model shape it.

Input parameters:

- `business_model` (string): How you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used to choose proof types; read from your inputs when not given
- `category` (string): Product category
- `customer_metrics` (string): Any customer results data (e.g., "critical exposures down 70% in one quarter; audit preparation from 3 weeks to 4 days")
- `key_outcome` (string, required): The main result customers achieve
- `product_name` (string): Your product/company name
- `target_customer` (string, required): Who you serve (e.g., "cloud security leads at mid-size fintech companies")
- `unique_capability` (string, required): What you do that others cannot/don't
- `your_sector` (string): 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.

### `impact_anchor_market` (~524 tokens)

Anchor Market

Takes what your product does and the segments you are weighing, and returns a beachhead market choice: your segments ranked from your own customers, pain and deal size when you give all three (the answer says which method it used), otherwise scored on keywords in their names; a TAM/SAM/SOM calculation that uses only the company counts, deal size and percentages you give; a three-year expansion path and an ICP hypothesis for the chosen segment. It never chooses a segment you did not name: without segments it recommends none and explains how to find yours from your own customers.

Input parameters:

- `average_deal_size` (string): Your annual contract value (ACV) as one amount (e.g., "$50,000", "$50K" or "$1.5M"); a range is refused
- `company_counts` (string): How many companies you could sell to in each segment, one per line or separated by semicolons (for example "Mid-market fintech: 3,200; Enterprise banks: 600"). A single number is read as the count fo…
- `current_customers` (string): Description of your current/best customers. With customer pain and average deal size it ranks the segments (the answer says which method it used); without them it is shown only and the keyword preset…
- `customer_pain` (string): The problem your best customers describe, in their words. With current customers and average deal size it ranks the segments from your own inputs; without them the keyword presets are used
- `percent_matching_icp` (number): The percent of those companies that match your ideal customer profile (for example 25). Needed for SAM
- `potential_segments` (array): The market segments you are weighing, in your own words (for example Mid-market fintech, Enterprise banks, Small retail chains). Needed for a recommendation: without segments no segment is chosen, an…
- `product_description` (string, required): What your product does
- `sales_cycle` (string): Typical sales cycle length. Shown in the output; not used in the scoring
- `year_one_share_percent` (number): The share of the matching companies you expect to win in year one, in percent (for example 1). Needed for SOM
- `your_sector` (string): 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.

### `impact_craft_message` (~292 tokens)

Craft Message

Takes your target customer, the key benefit and what sets you apart, and returns a positioning statement (full and one sentence), a message hierarchy from tagline to three supporting pillars, versions for different audiences, objection handling and ways to test the message. Optional product name, customer need, category, main competitor and business model fit it to your market. It writes from your own words, in whole sentences.

Input parameters:

- `business_model` (string): How you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used to choose the cost and proof lines; read from your inputs when not given
- `competitor` (string): Primary alternative/competitor
- `customer_need` (string): The need they have, written as an action (for example "lose days chasing low-risk cloud alerts")
- `differentiation` (string, required): Your unique differentiation
- `key_benefit` (string, required): Primary benefit/reason to buy
- `product_category` (string): Your product category, written as a noun phrase (for example "cloud security monitoring platform")
- `product_name` (string): Your product name
- `target_customer` (string, required): Target customer description
- `your_sector` (string): 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.

### `impact_translate_execution` (~282 tokens)

Translate Execution

Takes a positioning statement, your target customer and the key benefit, and returns copy to edit for the channels you choose: a website hero, a LinkedIn tagline and post drafts, a three-email cold sequence, a sales deck outline and a 15-minute demo script, with calls to action that fit your business model and the order to work the channels in. Optional channels, product name and business model shape it.

Input parameters:

- `business_model` (string): How you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used to choose calls to action and commercial terms; read from your inputs when not given
- `channels` (array): Which channels to cover, from website, linkedin, cold_email, sales_deck and product_demo. Others are listed as not covered; with none, all five are covered
- `key_benefit` (string, required): Primary benefit, written as an action (for example "fix critical exposures first")
- `positioning_statement` (string, required): Your core positioning statement
- `product_name` (string): Your product name
- `target_customer` (string, required): Target customer profile
- `your_sector` (string): 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.

### `impact_full_audit` (~400 tokens)

IMPACT Full Audit

Use for a full positioning review or when someone asks help me explain why we are different. Ask what the product does, who it serves and the problem it solves before calling; never invent these or fill missing facts with placeholders such as Not supplied. Clarify what unlabelled numbers mean. For a request only to phrase a message, impact_craft_message also fits; use this tool for the full review. Returns input completeness scores, supplied proof, a positioning draft and next actions. Scores measure how complete the inputs are, not how strong the positioning is. Never invent proof.

Input parameters:

- `business_model` (string): How you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used in the plan; read from your inputs when not given. It does not change the score
- `company_name` (string): Your company name
- `competitors` (array): Main competitors
- `current_positioning` (string): Your current positioning statement or tagline
- `customer_feedback` (string): Customer feedback actually supplied by the user. Leave out if absent; never invent quotes or outcomes.
- `key_differentiation` (string): A difference the user can describe. Leave out if unknown; do not invent uniqueness or proof.
- `problem_solved` (string, required): The problem the user says they solve. Ask if missing; do not invent or use a placeholder.
- `product_description` (string, required): What the product or service does, in the user's words. Ask if missing; do not invent or use a placeholder.
- `target_customer` (string, required): Who it serves, as supplied by the user. Ask if missing. Keep staff ranges as ranges and clarify unlabelled numbers.
- `your_sector` (string): 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.

Output parameters:

- `plainText` (string)
- `positioningAudit`

## Diagnostics

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

## Score history

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

## Common questions

### What is the io.github.shashwatgtm/impact-mcp server?

io.github.shashwatgtm/impact-mcp is listed in the public MCP registry as io.github.shashwatgtm/impact-mcp. IMPACT: 8 B2B positioning and messaging tools by Helix GTM Consulting. This page covers its hosted endpoint (https://impact.gtmhelix.com/mcp).

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

io.github.shashwatgtm/impact-mcp scores 83 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/impact-mcp server expose?

io.github.shashwatgtm/impact-mcp exposes 8 tools: impact_get_framework, impact_identify_champions, impact_map_alternatives, impact_pinpoint_value, impact_anchor_market, and 3 more. Their descriptions and schemas cost roughly 2,516 tokens of context every time the server is loaded.

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

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

### Is the io.github.shashwatgtm/impact-mcp server still maintained?

io.github.shashwatgtm/impact-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://impact.gtmhelix.com/mcp
- Repository: https://github.com/shashwatgtm/impact-mcp
- Website: https://tools.gtmhelix.com/connectors/
- Changelog RSS feed: https://verifymcp.io/servers/shashwatgtm-impact-mcp/impact.xml
- Changelog JSON feed: https://verifymcp.io/servers/shashwatgtm-impact-mcp/impact.json
- HTML version of this page: https://verifymcp.io/servers/shashwatgtm-impact-mcp/impact