# io.github.shashwatgtm/revenue-enablement-mcp (npm · @shashwatgtmalpha/revenue-enablement-mcp)

Deal Strategy & Sales Enablement - 12 revenue acceleration tools

- Trust score: 53/100 (low)
- Change this week: +9
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@shashwatgtmalpha/revenue-enablement-mcp`: 53/100 (this document), [markdown](https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/shashwatgtmalpha-revenue-enablement-mcp.md), [page](https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/shashwatgtmalpha-revenue-enablement-mcp)

## Channel facts

- Registry: `npm`
- Package: `@shashwatgtmalpha/revenue-enablement-mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 70/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.6.1, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (13 of 14), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 198 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2036 tokens (~169/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add shashwatgtm-revenue-enablement-mcp -- npx -y @shashwatgtmalpha/revenue-enablement-mcp
```

### Codex

```bash
codex mcp add shashwatgtm-revenue-enablement-mcp -- npx -y @shashwatgtmalpha/revenue-enablement-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shashwatgtm-revenue-enablement-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@shashwatgtmalpha/revenue-enablement-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shashwatgtm-revenue-enablement-mcp --command npx --arg -y --arg @shashwatgtmalpha/revenue-enablement-mcp
```

### Hermes

```yaml
mcp_servers:
  shashwatgtm-revenue-enablement-mcp:
    command: "npx"
    args: ["-y", "@shashwatgtmalpha/revenue-enablement-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "shashwatgtm-revenue-enablement-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@shashwatgtmalpha/revenue-enablement-mcp"
      ]
    }
  }
}
```

## 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-08-02 (score 53, +20)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Schema quality: unverified → good

### 2026-07-31 (score 33, −11)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 44)

First indexed and scored.

## MCP tools (12)

### `account_plan_builder` (~160 tokens)

Generate strategic account plans with power mapping, whitespace analysis, and expansion strategies. Provides actionable 90-day plans based on account intelligence.

Input parameters:

- `account_name` (string, required): Company/account name
- `account_notes` (string): Any additional context about the account
- `competitive_threats` (string): Known competitors in the account
- `current_arr` (number): Current ARR with this account (0 for prospects)
- `current_products` (string): Products/services they currently use from you
- `expansion_opportunities` (string): Potential expansion areas or whitespace
- `industry` (string): Industry vertical
- `known_contacts` (string): Known contacts and their roles (can be rough notes)
- `your_solution` (string): Your product/service offering

### `deal_strategy_coach` (~174 tokens)

Get deal-specific winning strategies based on deal stage, competitive dynamics, and stakeholder positions. Provides tactical next steps and risk mitigation.

Input parameters:

- `blockers` (string): Known blockers or objections
- `champion_status` (string): Champion identification status
- `close_date` (string): Target close date
- `competitors` (string): Competitors in the deal and their position
- `days_in_stage` (number): Days the deal has been in current stage
- `deal_name` (string, required): Deal/opportunity name
- `deal_stage` (string, required): Current deal stage
- `deal_value` (number): Deal value in dollars
- `economic_buyer` (string): Economic buyer name and engagement level
- `next_steps` (string): Currently planned next steps
- `your_solution` (string): What you are selling

### `discovery_question_bank` (~148 tokens)

Get contextual discovery questions using MEDDPICC, BANT, SPICED, or custom frameworks. Questions adapt based on what you already know about the prospect.

Input parameters:

- `deal_stage` (string): Stage of conversation
- `framework` (string, required): Discovery framework to use
- `gaps_to_fill` (string): Specific information gaps to address
- `known_metrics` (string): Metrics/KPIs already discussed
- `known_pain_points` (string): Pain points already identified
- `prospect_industry` (string): Prospect industry for context
- `prospect_role` (string): Role of person you are meeting with
- `your_solution` (string): Your product/solution for relevant questions

### `roi_business_case_builder` (~167 tokens)

Build quantified ROI business cases with documented assumptions, industry benchmarks, and executive-ready summaries. Generates defensible value calculations.

Input parameters:

- `annual_revenue` (number): Customer annual revenue
- `company_size` (string): Company size tier
- `current_process` (string): How they do it today (for comparison)
- `customer_name` (string): Customer/prospect name
- `employee_count` (number): Number of employees
- `implementation_timeline` (string): Expected implementation time
- `industry` (string): Industry for benchmarks
- `known_metrics` (string): Any metrics shared by prospect
- `primary_value_driver` (string, required): Primary value category
- `solution_price` (number): Annual cost of your solution
- `your_solution` (string, required): Your product/solution

### `mutual_action_plan_generator` (~177 tokens)

Generate collaborative close plans with milestones, owners, and dates. Creates alignment between buyer and seller on path to decision.

Input parameters:

- `blockers` (string): Known blockers or concerns
- `buyer_champion` (string): Champion name and title
- `current_stage` (string): Current deal stage
- `deal_name` (string, required): Deal/opportunity name
- `economic_buyer` (string): Economic buyer name and title
- `known_process_steps` (string): Known steps in their buying process
- `known_requirements` (string): Known requirements or evaluation criteria
- `procurement_contact` (string): Procurement contact if known
- `target_close_date` (string, required): Target close date (YYYY-MM-DD)
- `technical_evaluators` (string): Technical evaluators involved
- `your_solution` (string): What you are selling

### `win_loss_analyzer` (~180 tokens)

Analyze deal outcomes to identify patterns, improve win rates, and refine sales strategy. Works with single deals or deal portfolios.

Input parameters:

- `analysis_type` (string, required): Type of analysis
- `competitor_won` (string): Competitor who won (if applicable)
- `deal_details` (string): Deal details - can be rough notes, CRM export, or structured data
- `deal_outcome` (string): Deal outcome for single deal analysis
- `deal_value` (number): Deal value
- `loss_reason` (string): Stated loss reason (for lost deals)
- `multiple_deals` (string): For portfolio analysis: summary of multiple deals
- `sales_cycle_days` (number): Length of sales cycle
- `stakeholders_involved` (string): Key stakeholders and their positions
- `your_solution` (string): What you were selling

### `proposal_section_writer` (~166 tokens)

Generate customized proposal sections tailored to specific buyers. Creates executive summaries, solution overviews, pricing justifications, and more.

Input parameters:

- `customer_challenges` (string): Key challenges identified
- `customer_industry` (string): Customer industry
- `customer_name` (string): Customer name
- `implementation_approach` (string): How you will implement
- `key_differentiators` (string): Why you vs alternatives
- `pricing` (string): Pricing details if relevant
- `primary_audience` (string): Primary reader of proposal
- `section_type` (string, required): Proposal section to generate
- `success_metrics` (string): Expected outcomes/metrics
- `tone` (string): Tone for the proposal
- `your_solution` (string, required): Your product/solution

### `email_sequence_generator` (~201 tokens)

Generate multi-touch email sequences by persona, stage, and objective. Creates prospecting, nurture, follow-up, and re-engagement sequences.

Input parameters:

- `call_to_action` (string): Desired action (meeting, demo, reply)
- `key_value_prop` (string): Primary value proposition
- `num_emails` (number): Number of emails in sequence (3-7)
- `sender_context` (string): Context about sender (role, shared connections, etc.)
- `sequence_type` (string, required): Type of email sequence
- `social_proof` (string): Customer names, stats, or proof points
- `specific_pain_point` (string): Specific pain point to address
- `target_industry` (string): Target industry for context
- `target_persona` (string, required): Target persona (e.g., VP Sales, CTO, CFO)
- `tone` (string): Email tone
- `your_solution` (string, required): Your product/solution

### `demo_script_builder` (~183 tokens)

Create outcome-focused demo scripts tailored to specific personas and use cases. Includes discovery questions, feature-to-value mapping, and objection handling.

Input parameters:

- `attendees` (string): Other attendees and their roles
- `competitor_context` (string): Competitor being displaced or compared
- `customer_industry` (string): Customer industry
- `demo_duration` (number): Demo duration in minutes
- `demo_type` (string, required): Type of demo
- `desired_outcome` (string): What you want to achieve from this demo
- `key_pain_points` (string): Pain points to address in demo
- `known_objections` (string): Known objections to address
- `must_show_features` (string): Features that must be demonstrated
- `primary_audience` (string): Primary demo audience (role/persona)
- `your_solution` (string, required): Your product/solution

### `pricing_negotiation_guide` (~171 tokens)

Get value-based pricing defense strategies and negotiation tactics. Helps maintain deal value while addressing discount requests.

Input parameters:

- `approval_authority` (string): Who has final approval on pricing
- `buyer_leverage` (string): Buyer leverage points (size, reference potential, etc.)
- `competitor_price` (string): Competitor pricing if known
- `deal_value` (number): Current deal value
- `decision_timeline` (string): When decision needs to be made
- `discount_requested` (number): Discount percentage requested
- `scenario` (string, required): Negotiation scenario
- `value_delivered` (string): Quantified value your solution delivers
- `your_leverage` (string): Your leverage points (unique features, timeline, etc.)
- `your_solution` (string): Your product/solution

### `champion_enablement_kit` (~176 tokens)

Create internal selling tools for your champion. Generates executive briefs, internal business cases, objection responses, and presentation talking points.

Input parameters:

- `asset_type` (string, required): Type of enablement asset
- `budget_context` (string): Budget situation and pricing
- `champion_name` (string): Champion name
- `champion_role` (string): Champion role/title
- `champion_wins` (string): How this makes the champion look good
- `competitive_context` (string): Competitive alternatives being considered
- `key_value_points` (string): Key value points to emphasize
- `known_objections` (string): Expected objections from stakeholders
- `target_stakeholder` (string): Who the champion needs to convince
- `urgency_drivers` (string): Why act now
- `your_solution` (string, required): Your product/solution

### `competitive_trap_setter` (~133 tokens)

Generate landmine questions and competitive positioning tactics. Helps expose competitor weaknesses during evaluation without being negative.

Input parameters:

- `buyer_persona` (string): Role of key evaluator
- `buyer_priorities` (string): What the buyer cares most about
- `competitor` (string, required): Primary competitor to position against
- `competitor_weaknesses` (string): Known competitor weaknesses
- `evaluation_stage` (string): Stage of competitive evaluation
- `trap_type` (string): Type of competitive positioning
- `your_solution` (string, required): Your product/solution
- `your_strengths` (string): Your key differentiators

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/shashwatgtmalpha-revenue-enablement-mcp#diagnostics

## Score history

- 2026-08-03: 53
- 2026-08-02: 53
- 2026-08-01: 33
- 2026-07-31: 33
- 2026-07-30: 44
- 2026-07-28: 44
- 2026-07-27: 44

## Links

- npm package: https://www.npmjs.com/package/@shashwatgtmalpha/revenue-enablement-mcp
- Socket report: https://socket.dev/npm/package/@shashwatgtmalpha/revenue-enablement-mcp
- Repository: https://github.com/shashwatgtm/revenue-enablement-mcp
- Changelog RSS feed: https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/shashwatgtmalpha-revenue-enablement-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/shashwatgtmalpha-revenue-enablement-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/shashwatgtmalpha-revenue-enablement-mcp