io.github.shashwatgtm/revenue-enablement-mcp
NPM · @SHASHWATGTMALPHA/REVENUE-ENABLEMENT-MCP · SCANNED SEP 22
Deal Strategy & Sales Enablement - 12 revenue acceleration tools
Available components
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
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 248 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- 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 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
How do I install the io.github.shashwatgtm/revenue-enablement-mcp server?
io.github.shashwatgtm/revenue-enablement-mcp runs locally as an npm package, launched with npx -y @shashwatgtmalpha/revenue-enablement-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/revenue-enablement-mcp
claude mcp add shashwatgtm-revenue-enablement-mcp -- npx -y @shashwatgtmalpha/revenue-enablement-mcp
{
"mcpServers": {
"shashwatgtm-revenue-enablement-mcp": {
"command": "npx",
"args": [
"-y",
"@shashwatgtmalpha/revenue-enablement-mcp"
]
}
}
} {
"servers": {
"shashwatgtm-revenue-enablement-mcp": {
"command": "npx",
"args": [
"-y",
"@shashwatgtmalpha/revenue-enablement-mcp"
]
}
}
} codex mcp add shashwatgtm-revenue-enablement-mcp -- npx -y @shashwatgtmalpha/revenue-enablement-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shashwatgtm-revenue-enablement-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@shashwatgtmalpha/revenue-enablement-mcp"
],
"enabled": true
}
}
} openclaw mcp add shashwatgtm-revenue-enablement-mcp --command npx --arg -y --arg @shashwatgtmalpha/revenue-enablement-mcp
mcp_servers:
shashwatgtm-revenue-enablement-mcp:
command: "npx"
args: ["-y", "@shashwatgtmalpha/revenue-enablement-mcp"] {
"McpServers": {
"shashwatgtm-revenue-enablement-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@shashwatgtmalpha/revenue-enablement-mcp"
]
}
}
} assistant mcp add shashwatgtm-revenue-enablement-mcp -t stdio -c npx -a -y @shashwatgtmalpha/revenue-enablement-mcp
{
"mcpServers": {
"shashwatgtm-revenue-enablement-mcp": {
"command": "npx",
"args": [
"-y",
"@shashwatgtmalpha/revenue-enablement-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 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.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 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.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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/revenue-enablement-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 →
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 →
account_plan_builder ~160
Generate strategic account plans with power mapping, whitespace analysis, and expansion strategies. Provides actionable 90-day plans based on account intelligence.
| Name | Type | Req | Description |
|---|---|---|---|
| account_name | string | yes | 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 |
No output schema declared.
No examples provided.
champion_enablement_kit ~176
Create internal selling tools for your champion. Generates executive briefs, internal business cases, objection responses, and presentation talking points.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | yes | 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 | yes | Your product/solution |
No output schema declared.
No examples provided.
competitive_trap_setter ~133
Generate landmine questions and competitive positioning tactics. Helps expose competitor weaknesses during evaluation without being negative.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_persona | string | – | Role of key evaluator |
| buyer_priorities | string | – | What the buyer cares most about |
| competitor | string | yes | 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 | yes | Your product/solution |
| your_strengths | string | – | Your key differentiators |
No output schema declared.
No examples provided.
deal_strategy_coach ~174
Get deal-specific winning strategies based on deal stage, competitive dynamics, and stakeholder positions. Provides tactical next steps and risk mitigation.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Deal/opportunity name |
| deal_stage | string | yes | 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 |
No output schema declared.
No examples provided.
demo_script_builder ~183
Create outcome-focused demo scripts tailored to specific personas and use cases. Includes discovery questions, feature-to-value mapping, and objection handling.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Your product/solution |
No output schema declared.
No examples provided.
discovery_question_bank ~148
Get contextual discovery questions using MEDDPICC, BANT, SPICED, or custom frameworks. Questions adapt based on what you already know about the prospect.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_stage | string | – | Stage of conversation |
| framework | string | yes | 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 |
No output schema declared.
No examples provided.
email_sequence_generator ~201
Generate multi-touch email sequences by persona, stage, and objective. Creates prospecting, nurture, follow-up, and re-engagement sequences.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Target persona (e.g., VP Sales, CTO, CFO) |
| tone | string | – | Email tone |
| your_solution | string | yes | Your product/solution |
No output schema declared.
No examples provided.
mutual_action_plan_generator ~177
Generate collaborative close plans with milestones, owners, and dates. Creates alignment between buyer and seller on path to decision.
| Name | Type | Req | Description |
|---|---|---|---|
| blockers | string | – | Known blockers or concerns |
| buyer_champion | string | – | Champion name and title |
| current_stage | string | – | Current deal stage |
| deal_name | string | yes | 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 | yes | Target close date (YYYY-MM-DD) |
| technical_evaluators | string | – | Technical evaluators involved |
| your_solution | string | – | What you are selling |
No output schema declared.
No examples provided.
pricing_negotiation_guide ~171
Get value-based pricing defense strategies and negotiation tactics. Helps maintain deal value while addressing discount requests.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
proposal_section_writer ~166
Generate customized proposal sections tailored to specific buyers. Creates executive summaries, solution overviews, pricing justifications, and more.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Proposal section to generate |
| success_metrics | string | – | Expected outcomes/metrics |
| tone | string | – | Tone for the proposal |
| your_solution | string | yes | Your product/solution |
No output schema declared.
No examples provided.
roi_business_case_builder ~167
Build quantified ROI business cases with documented assumptions, industry benchmarks, and executive-ready summaries. Generates defensible value calculations.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Primary value category |
| solution_price | number | – | Annual cost of your solution |
| your_solution | string | yes | Your product/solution |
No output schema declared.
No examples provided.
win_loss_analyzer ~180
Analyze deal outcomes to identify patterns, improve win rates, and refine sales strategy. Works with single deals or deal portfolios.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_type | string | yes | 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 |
No output schema declared.
No examples provided.
What is the io.github.shashwatgtm/revenue-enablement-mcp server?
io.github.shashwatgtm/revenue-enablement-mcp is listed in the public MCP registry as io.github.shashwatgtm/revenue-enablement-mcp. Deal Strategy & Sales Enablement - 12 revenue acceleration tools. This page covers its npm package (@shashwatgtmalpha/revenue-enablement-mcp).
Is the io.github.shashwatgtm/revenue-enablement-mcp server safe to use?
io.github.shashwatgtm/revenue-enablement-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/revenue-enablement-mcp server expose?
io.github.shashwatgtm/revenue-enablement-mcp exposes 12 tools: account_plan_builder, deal_strategy_coach, discovery_question_bank, roi_business_case_builder, mutual_action_plan_generator, and 7 more. Their descriptions and schemas cost roughly 2,036 tokens of context every time the server is loaded.
Is the io.github.shashwatgtm/revenue-enablement-mcp server still maintained?
io.github.shashwatgtm/revenue-enablement-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/revenue-enablement-mcp server under?
io.github.shashwatgtm/revenue-enablement-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.