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/impact-mcp

NPM · @SHASHWATGTMALPHA/IMPACT-MCP · SCANNED SEP 22

Hypothesis-Driven B2B Positioning Engine - 8 strategic positioning tools

0 this week 73 Trust /100
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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.6.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 7 of 14 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 823 tokens (~102/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 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
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

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

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

# add to Claude Code
claude mcp add shashwatgtm-impact-mcp -- npx -y @shashwatgtmalpha/impact-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "shashwatgtm-impact-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@shashwatgtmalpha/impact-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "shashwatgtm-impact-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@shashwatgtmalpha/impact-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add shashwatgtm-impact-mcp -- npx -y @shashwatgtmalpha/impact-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shashwatgtm-impact-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@shashwatgtmalpha/impact-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add shashwatgtm-impact-mcp --command npx --arg -y --arg @shashwatgtmalpha/impact-mcp
# ~/.hermes/config.yaml
mcp_servers:
  shashwatgtm-impact-mcp:
    command: "npx"
    args: ["-y", "@shashwatgtmalpha/impact-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "shashwatgtm-impact-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@shashwatgtmalpha/impact-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add shashwatgtm-impact-mcp -t stdio -c npx -a -y @shashwatgtmalpha/impact-mcp
// mcp.json
{
  "mcpServers": {
    "shashwatgtm-impact-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@shashwatgtmalpha/impact-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.

  • 22 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 21 Sept 26 0
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1

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

  • 19 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 18 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 16 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.

  • 15 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 14 Sept 26 0
    • Stability: 0.97 → pass security
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 22 Sept 2026 · Analysed npm/@shashwatgtmalpha/impact-mcp@2.0.0

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 14 packages
Packages resolved 14
Stale 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~823 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
impact_anchor_market ~120

Select beachhead market with scoring and TAM/SAM/SOM framework

NameTypeReqDescription
average_deal_sizestringOptional: Your ACV (e.g., "$50K")
current_customersstringOptional: Description of your current/best customers
potential_segmentsarrayList of potential market segments (e.g., ["Mid-market SaaS", "Enterprise Finance", "SMB Retail"])
product_descriptionstringyesWhat your product does
sales_cyclestringOptional: Typical sales cycle length

No output schema declared.

No examples provided.

impact_craft_message ~104

Build positioning statement and message hierarchy with variations

NameTypeReqDescription
competitorstringPrimary alternative/competitor
customer_needstringThe need or opportunity they have
differentiationstringyesYour unique differentiation
key_benefitstringyesPrimary benefit/reason to buy
product_categorystringYour product category
product_namestringYour product name
target_customerstringyesTarget customer description

No output schema declared.

No examples provided.

impact_full_audit ~121

Complete positioning audit with scoring and recommendations

NameTypeReqDescription
company_namestringYour company name
competitorsarrayMain competitors
current_positioningstringOptional: Your current positioning statement or tagline
customer_feedbackstringOptional: What customers say about you
key_differentiationstringWhat makes you unique
problem_solvedstringyesThe problem you solve
product_descriptionstringyesWhat your product does
target_customerstringyesWho you serve

No output schema declared.

No examples provided.

impact_get_framework ~48

Get complete IMPACT framework methodology with phase-by-phase guidance

NameTypeReqDescription
focus_phasestringOptional: specific phase to focus on (identify/map/pinpoint/anchor/craft/translate)

No output schema declared.

No examples provided.

impact_identify_champions ~118

Generate champion hypotheses from company/product context - no blanks, actionable insights

NameTypeReqDescription
company_namestringYour company name
price_pointstringOptional: ACV range (e.g., "$50K-100K")
problem_solvedstringyesThe core problem you solve
product_descriptionstringyesWhat your product does (1-2 sentences)
target_company_typestringType of companies you target (e.g., "Series B SaaS", "Enterprise manufacturing")

No output schema declared.

No examples provided.

impact_map_alternatives ~99

Analyze competitive landscape and find positioning whitespace

NameTypeReqDescription
categorystringyesYour product category (e.g., "Sales engagement", "Data platform")
competitor_weaknessesstringOptional: Known competitor weaknesses or customer complaints
competitorsarrayList of competitor names
your_productstringyesWhat your product does
your_strengthsstringOptional: What you do better than competitors

No output schema declared.

No examples provided.

impact_pinpoint_value ~121

Generate value proposition with quantification and proof points

NameTypeReqDescription
categorystringProduct category
customer_metricsstringOptional: Any customer results data (e.g., "40% faster, 3x pipeline")
key_outcomestringyesThe main result customers achieve
product_namestringYour product/company name
target_customerstringyesWho you serve (e.g., "B2B sales teams")
unique_capabilitystringyesWhat you do that others cannot/don't

No output schema declared.

No examples provided.

impact_translate_execution ~92

Adapt positioning for specific channels and touchpoints

NameTypeReqDescription
channelsarrayChannels to optimize for (e.g., ["website", "linkedin", "email", "sales_deck"])
key_benefitstringyesPrimary benefit
positioning_statementstringyesYour core positioning statement
product_namestringYour product name
target_customerstringyesTarget customer profile

No output schema declared.

No examples provided.

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. Hypothesis-Driven B2B Positioning Engine - 8 strategic positioning tools. This page covers its npm package (@shashwatgtmalpha/impact-mcp).

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

io.github.shashwatgtm/impact-mcp scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against 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/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 823 tokens of context every time the server is loaded.

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 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/impact-mcp server under?

io.github.shashwatgtm/impact-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.