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-server

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

IMPACT Framework - B2B Positioning & Messaging Tools by Shashwat Ghosh

0 this week 83 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 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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 675 tokens (~84/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 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
Install

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

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

# add to Claude Code
claude mcp add shashwatgtm-impact-mcp-server -- npx -y @shashwatgtmalpha/impact-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "shashwatgtm-impact-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@shashwatgtmalpha/impact-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "shashwatgtm-impact-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@shashwatgtmalpha/impact-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add shashwatgtm-impact-mcp-server -- npx -y @shashwatgtmalpha/impact-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shashwatgtm-impact-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@shashwatgtmalpha/impact-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add shashwatgtm-impact-mcp-server --command npx --arg -y --arg @shashwatgtmalpha/impact-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  shashwatgtm-impact-mcp-server:
    command: "npx"
    args: ["-y", "@shashwatgtmalpha/impact-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "shashwatgtm-impact-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@shashwatgtmalpha/impact-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add shashwatgtm-impact-mcp-server -t stdio -c npx -a -y @shashwatgtmalpha/impact-mcp-server
// mcp.json
{
  "mcpServers": {
    "shashwatgtm-impact-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@shashwatgtmalpha/impact-mcp-server"
      ]
    }
  }
}
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 +1
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 19 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 18 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 11 Sept 26 +1
    • Security disclosure: fail → unverified 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 22 Sept 2026 · Analysed npm/@shashwatgtmalpha/impact-mcp-server@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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~675 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 ~92

Select optimal market category and beachhead strategy (A phase)

NameTypeReqDescription
best_customersstringDescription of your best/most successful customers
company_namestringyesYour company name
current_categorystringCurrent market category you compete in
expansion_goalsstringWhere you want to expand to
product_descriptionstringyesBrief description of your product/service

No output schema declared.

No examples provided.

impact_craft_message ~105

Create positioning statements and message architecture (C phase)

NameTypeReqDescription
categorystringyesMarket category
company_namestringyesYour company name
key_benefitstringyesPrimary benefit delivered
key_differentiatorstringyesMain differentiation
main_alternativestringyesPrimary competitor or alternative
product_descriptionstringyesBrief description of your product/service
target_customerstringyesWho is this for?

No output schema declared.

No examples provided.

impact_full_audit ~95

Complete positioning audit using all IMPACT phases

NameTypeReqDescription
biggest_challengestringBiggest positioning/messaging challenge
company_namestringyesYour company name
current_positioningstringCurrent positioning statement if any
main_competitorsstringKey competitors
product_descriptionstringyesBrief description of your product/service
target_marketstringyesTarget market/customer

No output schema declared.

No examples provided.

impact_get_framework ~28

Get IMPACT Framework documentation and methodology

NameTypeReqDescription
componentstringyesFramework component to retrieve

No output schema declared.

No examples provided.

impact_identify_champions ~103

Analyze and identify ideal customers and internal champions (I phase)

NameTypeReqDescription
company_namestringyesYour company name
current_customersstringDescription of current successful customers
product_descriptionstringyesBrief description of your product/service
sales_cyclestringTypical sales cycle length
target_marketstringTarget market or industry
typical_deal_sizestringTypical deal size or price point

No output schema declared.

No examples provided.

impact_map_alternatives ~84

Map competitive landscape and alternatives (M phase)

NameTypeReqDescription
company_namestringyesYour company name
direct_competitorsstringKnown direct competitors
problem_solvedstringyesThe main problem your product solves
product_descriptionstringyesBrief description of your product/service
target_customerstringTarget customer description

No output schema declared.

No examples provided.

impact_pinpoint_value ~88

Discover and articulate unique differentiation (P phase)

NameTypeReqDescription
claimed_differentiatorsstringWhat you currently claim as differentiators
company_namestringyesYour company name
competitor_claimsstringWhat competitors claim
customer_feedbackstringWhat customers say they value most
product_descriptionstringyesBrief description of your product/service

No output schema declared.

No examples provided.

impact_translate_execution ~80

Plan tactical deployment across channels (T phase)

NameTypeReqDescription
company_namestringyesYour company name
current_channelsstringCurrent marketing/sales channels
key_messagesstringyesTop 3 key messages
positioning_statementstringyesYour core positioning statement
target_personasstringyesPrimary personas to reach

No output schema declared.

No examples provided.

Common questions

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

io.github.shashwatgtm/impact-mcp-server is listed in the public MCP registry as io.github.shashwatgtm/impact-mcp-server. IMPACT Framework - B2B Positioning & Messaging Tools by Shashwat Ghosh. This page covers its npm package (@shashwatgtmalpha/impact-mcp-server).

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

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

io.github.shashwatgtm/impact-mcp-server 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 675 tokens of context every time the server is loaded.

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

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

io.github.shashwatgtm/impact-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.