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/icp-intelligence-mcp

NPM · @SHASHWATGTMALPHA/ICP-INTELLIGENCE-MCP · SCANNED SEP 22

Deep ICP Analysis with Pattern Detection - 9 B2B targeting tools

0 this week 75 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 Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 807 tokens (~89/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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/icp-intelligence-mcp server?

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

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

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

  • 18 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.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 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.

  • 13 Sept 26 +1
    • Security disclosure: unverified → fail 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/icp-intelligence-mcp@1.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 · 9 exposed · ~807 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
account_prioritization ~48

Rank and prioritize accounts using multi-dimensional scoring

NameTypeReqDescription
accountsarrayList of accounts to prioritize
prioritization_weightsobjectCustom weights (must sum to 100)

No output schema declared.

No examples provided.

buyer_group_analyzer ~104

Map buyer group dynamics, influence relationships, and decision-making process

NameTypeReqDescription
deal_sizestringACV range (e.g., "$50K-100K")
known_stakeholdersarrayRoles you know are involved
product_categorystringyesWhat you sell
target_company_sizestringCompany size (e.g., "500-1000 employees")
typical_championstringYour typical champion role

No output schema declared.

No examples provided.

icp_deep_dive ~75

Analyze customer data to detect ICP patterns - firmographics, technographics, buying behavior

NameTypeReqDescription
customer_descriptionsstringAlternative: Describe your best customers in text format
customersarrayList of customer objects with available attributes
product_categorystringWhat type of product you sell

No output schema declared.

No examples provided.

icp_evolution_tracker ~99

Track how your ICP should evolve based on market changes and data

NameTypeReqDescription
current_icpstringyesYour current ICP definition
market_changesstringRecent market or competitive changes
recent_lossesstringDescription of recent lost deals
recent_winsstringDescription of recent successful customers
time_periodstringTime period for analysis (e.g., "Q4 2024")

No output schema declared.

No examples provided.

icp_gap_analysis ~72

Analyze gaps between current customer base and ideal ICP

NameTypeReqDescription
current_customersstringyesDescription of your current customer base
current_metricsobjectCurrent performance metrics
ideal_icpstringyesDescription of your ideal customer profile
target_metricsobjectTarget performance metrics

No output schema declared.

No examples provided.

icp_interview_synthesizer ~76

Extract ICP patterns from customer interview notes or transcripts

NameTypeReqDescription
analysis_focusstringWhat to focus on: pain_points, buying_journey, value_props, all
interview_notesarrayStructured interview notes
raw_transcriptsstringAlternative: Paste raw interview transcripts or notes

No output schema declared.

No examples provided.

icp_scoring_model ~80

Create qualification scoring model with auto-weighted criteria based on your success patterns

NameTypeReqDescription
product_categorystring
scoring_criteriaarrayCriteria for scoring with importance levels
success_correlationstringWhat correlates with success? (e.g., "deals with VP Sales champion close 2x faster")

No output schema declared.

No examples provided.

lookalike_signal_generator ~107

Generate platform-specific targeting criteria and search queries (generates criteria, not data)

NameTypeReqDescription
buying_triggersarrayEvents that trigger buying
champion_titlesarrayyesJob titles of your champions
icp_firmographicsobjectFirmographic criteria
icp_technographicsarrayTechnologies your ICP typically uses
platformsarrayPlatforms to generate criteria for (linkedin, google_ads, 6sense, zoominfo)

No output schema declared.

No examples provided.

tam_sam_som_calculator ~146

Calculate TAM/SAM/SOM using bottom-up methodology from your data (calculation framework, not data source)

NameTypeReqDescription
average_contract_valuenumberyesYour average ACV in dollars
data_sourcesstringWhere you got your numbers (for documentation)
icp_percentagenumberPercentage that match your ICP (1-100)
segment_namestringName of the market segment
total_potential_companiesnumberyesEstimated total companies that could buy (from LinkedIn, industry reports)
year1_market_share_targetnumberRealistic Year 1 market share percentage (typically 1-5%)

No output schema declared.

No examples provided.

Common questions

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

io.github.shashwatgtm/icp-intelligence-mcp is listed in the public MCP registry as io.github.shashwatgtm/icp-intelligence-mcp. Deep ICP Analysis with Pattern Detection - 9 B2B targeting tools. This page covers its npm package (@shashwatgtmalpha/icp-intelligence-mcp).

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

io.github.shashwatgtm/icp-intelligence-mcp scores 75 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/icp-intelligence-mcp server expose?

io.github.shashwatgtm/icp-intelligence-mcp exposes 9 tools: icp_deep_dive, icp_scoring_model, buyer_group_analyzer, tam_sam_som_calculator, lookalike_signal_generator, and 4 more. Their descriptions and schemas cost roughly 807 tokens of context every time the server is loaded.

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

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

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