Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.shashwatgtm/impact-mcp

NPM · @SHASHWATGTMALPHA/IMPACT-MCP · SCANNED AUG 3

Hypothesis-Driven B2B Positioning Engine - 8 strategic positioning tools

−14 this week 59 Trust /100
Trust breakdown (6 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 →

Supply Chain Security70
  • 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
  • Only part of the dependency tree could be resolved (13 of 14), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).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 Management23
  • Stability observed for 7 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
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @shashwatgtmalpha/impact-mcp

# add to Claude Code
claude mcp add shashwatgtm-impact-mcp -- npx -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"]
// 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.

  • 2 Aug 26 +20
    • Known CVEs: unverified → fail security
    • Malware scan: unverified → pass security
    • Stability: unverified → 0.20 functional
    • Dependency health: unverified → partial functional
  • 1 Aug 26 −5
    • Known CVEs: fail → unverified security
    • Dependency health: partial → unverified functional
  • 31 Jul 26 −20
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −9
    • Provenance: fail → unverified security
    • Install scripts: pass → unverified security
    • License: pass → unverified functional
    • Maintenance: pass → unverified functional
    • Licence: MIT functional
  • 27 Jul 26 +46
    • CVE-2025-66414 affects this package: high security
    • Provenance: unverified → fail security
    • Known CVEs: unverified → fail security
    • Install scripts: unverified → pass security
    • Security disclosure: unverified → fail functional
    • Tool coverage: unverified → 100 functional
    • License: unverified → pass functional
    • Maintenance: unverified → pass functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
    • Licence: MIT functional
  • 26 Jul 26 27

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 3 Aug 2026 · Analysed npm/@shashwatgtmalpha/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

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

13 packages in the resolved dependency tree · 13 deprecated · 6 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

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.

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.