# io.github.shashwatgtm/revenue-enablement-mcp (remote · revenue-enablement.gtmhelix.com)

Revenue Enablement: 12 deal and sales enablement tools by Helix GTM Consulting

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `revenue-enablement.gtmhelix.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/revenue-enablement.md), [page](https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/revenue-enablement)
- npm · `@shashwatgtmalpha/revenue-enablement-mcp`: 81/100, [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

- Endpoint: `https://revenue-enablement.gtmhelix.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.30`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3868 tokens (~322/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**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.shashwatgtm/revenue-enablement-mcp server?

io.github.shashwatgtm/revenue-enablement-mcp is a hosted endpoint at https://revenue-enablement.gtmhelix.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http shashwatgtm-revenue-enablement-mcp 'https://revenue-enablement.gtmhelix.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "shashwatgtm-revenue-enablement-mcp": {
      "url": "https://revenue-enablement.gtmhelix.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shashwatgtm-revenue-enablement-mcp": {
      "type": "http",
      "url": "https://revenue-enablement.gtmhelix.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.shashwatgtm-revenue-enablement-mcp]
url = "https://revenue-enablement.gtmhelix.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shashwatgtm-revenue-enablement-mcp": {
      "type": "remote",
      "url": "https://revenue-enablement.gtmhelix.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shashwatgtm-revenue-enablement-mcp --url 'https://revenue-enablement.gtmhelix.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  shashwatgtm-revenue-enablement-mcp:
    url: "https://revenue-enablement.gtmhelix.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "shashwatgtm-revenue-enablement-mcp": {
      "Transport": "http",
      "Url": "https://revenue-enablement.gtmhelix.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add shashwatgtm-revenue-enablement-mcp -t streamable-http -u 'https://revenue-enablement.gtmhelix.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "shashwatgtm-revenue-enablement-mcp": {
      "type": "http",
      "url": "https://revenue-enablement.gtmhelix.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-04 (score 80, +1)

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

### 2026-11-02 (score 79, +1)

- [security] Tool “roi_business_case_builder” rewrote its description, which is the text the model reads
- [security] Tool “deal_strategy_coach” rewrote its description, which is the text the model reads
- [security] Tool “pricing_negotiation_guide” rewrote its description, which is the text the model reads
- [cosmetic] “roi_business_case_builder” added an optional parameter “annual_cash_benefit”
- [cosmetic] “pricing_negotiation_guide” added an optional parameter “pricing_authority_status”
- [cosmetic] “deal_strategy_coach” added an optional parameter “blocker_status”
- [cosmetic] “deal_strategy_coach” added an optional parameter “economic_buyer_engagement”
- [cosmetic] “deal_strategy_coach” added an optional parameter “incumbent_status”
- [cosmetic] “deal_strategy_coach” added an optional parameter “project_status”
- [cosmetic] “discovery_question_bank” added an optional parameter “contact_permission”
- [cosmetic] “roi_business_case_builder” reworded the description of “industry”
- [cosmetic] “roi_business_case_builder” reworded the description of “known_metrics”
- [cosmetic] “account_plan_builder” reworded the description of “known_contacts”

### 2026-10-31 (score 78, +1)

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

### 2026-10-29 (score 77, 0)

- [cosmetic] “account_plan_builder” reworded the description of “known_contacts”
- [cosmetic] “mutual_action_plan_generator” reworded the description of “known_process_steps”
- [cosmetic] “mutual_action_plan_generator” reworded the description of “target_close_date”

### 2026-10-28 (score 77, +1)

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

### 2026-10-26 (score 76, +1)

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

### 2026-10-24 (score 75, +1)

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

### 2026-10-22 (score 74, +1)

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

## MCP tools (12)

### `account_plan_builder` (~266 tokens)

Account Plan Builder

Generate strategic account plans with power mapping (one row per contact you name), whitespace analysis, competitive questions and an answer for each objection. Builds a 90-day plan from the contacts, products, threats and notes you give it; it does not look the account up.

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, one per line or separated by semicolons, for example: Head of RevOps (champion); CFO. Each entry becomes one row, so put other notes in account notes
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string): Your product/service offering

### `deal_strategy_coach` (~345 tokens)

Deal Strategy Coach

Get deal-specific winning strategies based on deal stage, competitive dynamics, and stakeholder positions. Provides tactical next steps and risk mitigation. Ask the user to confirm blocker status, economic buyer engagement, incumbent status and project status when those facts affect the score; typed facts take precedence over text.

Input parameters:

- `blocker_status` (string): Ask whether any blocker is present. A confirmed typed fact overrides word reading.
- `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
- `economic_buyer_engagement` (string): Ask whether the budget holder actively participates in this decision. Overrides word reading.
- `incumbent_status` (string): Ask whether the buyer already uses a competing supplier. Overrides word reading.
- `next_steps` (string): Currently planned next steps
- `project_status` (string): Ask whether the project is still active. A cancelled project is held, without a close plan.
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string): What you are selling

### `discovery_question_bank` (~291 tokens)

Discovery Question Bank

Writes a discovery question list from the framework you choose (MEDDPICC, BANT, SPICED, Challenger, Gap Selling or all five) and what you already know about the prospect. Returns an opening for the conversation, questions in the language of the prospect's sector and on what your solution covers, the questions for each part of the framework, a closing for the call and what to say to an objection. It uses only the inputs you give and says which it did not get.

Input parameters:

- `contact_permission` (string): Optional confirmed fact. Ask whether this person permits further contact; this answer overrides contact-refusal wording in the notes.
- `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_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string): Your product/solution for relevant questions

### `roi_business_case_builder` (~575 tokens)

ROI Business Case Builder

Build an ROI business case from the buyer's own figures: annual value estimate, or current annual cost with expected improvement percent. With them it calculates the ROI, payback, three-year value and sensitivity. Without them it shows no ROI: it names the inputs to add and gives the structure of the case (the cost lines to price, your quoted results as reference points, the questions to ask). Ask finance for the cash-only annual benefit when an investment decision depends on cash.

Input parameters:

- `annual_cash_benefit` (number): Optional buyer-confirmed annual cash benefit in US dollars, excluding staff time without a cash release. Ask finance to separate cash from non-cash value. Compared with the annual solution price; a c…
- `annual_revenue` (number): Customer annual revenue. Shown as your input; it is not turned into a value
- `annual_value_estimate` (number): Optional: the buyer's own estimate of the annual value in dollars; used as the value when given
- `company_size` (string): Company size tier
- `current_annual_cost` (number): Optional: what the problem or the current process costs the buyer a year, in dollars (their figure)
- `current_process` (string): How they do it today. Separate the ways of working with a semicolon: each becomes a cost line to price. Not used in the calculation
- `customer_name` (string): Customer/prospect name
- `employee_count` (number): Number of employees. Shown as your input; it is not turned into a value
- `expected_improvement_percent` (number): Optional: the share of that annual cost the buyer expects to save, in percent (their figure)
- `implementation_timeline` (string): Expected implementation time. Shown in the output; not used in the calculation
- `industry` (string): The customer's industry, in any words. Used for wording and sector notes only: no industry figure is applied to the calculation. A return needs the buyer's own figures (annual value estimate, or curr…
- `known_metrics` (string): Metrics the prospect shared, or results you can quote. Listed as reference points, never as the buyer's figures; to turn the buyer's figures into the value, give current annual cost and expected impr…
- `primary_value_driver` (string, required): Primary value category
- `solution_price` (number): Annual cost of your solution
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string, required): Your product/solution

### `mutual_action_plan_generator` (~266 tokens)

Mutual Action Plan Generator

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, separated by semicolons or new lines (for example: Pilot; security review; procurement). Each step becomes its own milestone
- `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). A Saturday or Sunday date moves to the Friday before, and the plan says so
- `technical_evaluators` (string): Technical evaluators involved
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string): What you are selling

### `win_loss_analyzer` (~296 tokens)

Win/Loss Analyzer

Writes a short win/loss review of one deal, a competitor pattern or a set of deals from the details you give. Returns a write-up in plain sentences that names the outcome, the stated reason in the buyer's words, what the reason points to and what the buyer weighed, then the questions for the review call and sector notes. It adds no figure or reason you did not give, and says plainly what the outcome or reason would add when it is missing.

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_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string): What you were selling

### `proposal_section_writer` (~282 tokens)

Proposal Section Writer

Writes the proposal section you choose, such as an executive summary, solution overview or pricing justification, for a named buyer. Returns the section as sentences built from your solution, the buyer's challenges, your differentiators, pricing and success measures, with sector notes. It invents no figure, customer or date, and says once which inputs were not given.

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): Adds a one-line note at the top of the executive summary on what this audience looks for
- `section_type` (string, required): Proposal section to generate
- `success_metrics` (string): Expected outcomes/metrics
- `tone` (string): Tone for the proposal (changes only the opening of the executive summary)
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string, required): Your product/solution

### `email_sequence_generator` (~335 tokens)

Email Sequence Generator

Writes a multi-email sequence by persona, stage and objective, such as prospecting, nurture, follow-up or re-engagement. Returns each email with its subject, send day and body, built from your solution, the pain point, the value proposition, your proof and the ask, and a note on what you did not give. No placeholder is left in a body, and no result or statistic is invented.

Input parameters:

- `call_to_action` (string): Desired action (meeting, demo, reply)
- `key_value_prop` (string): Primary value proposition
- `num_emails` (number): Accepted but not used yet: each sequence type has a fixed number of emails
- `sender_context` (string): Context about sender (role, shared connections, etc.)
- `sequence_type` (string, required): Type of email sequence. cold_outreach, warm_follow_up, post_demo and re_engagement have their own templates; the other types return a general outline
- `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_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string, required): Your product/solution

### `demo_script_builder` (~288 tokens)

Demo Script Builder

Writes a demo script for the demo type, persona and use case you choose. Returns a timed run from opening to close, with spoken lines and a step for each feature you must show, tied to the pains you name, then discussion, close and follow-up lines and sector notes. The steps come from the parts of your solution and your pains, and the answer says where they came from and what it did not get.

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_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string, required): Your product/solution

### `pricing_negotiation_guide` (~353 tokens)

Pricing Negotiation Guide

Get value-based pricing defense strategies and negotiation tactics. Helps maintain deal value while addressing discount requests. Ask whether the user has authority to approve the proposed terms.

Input parameters:

- `approval_authority` (string): Who has final approval on pricing
- `business_model` (string): Optional: how you charge (software subscription, services, connectivity, per transaction, marketplace, hardware plus software, or investment management). Read from your other inputs when left out
- `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
- `pricing_authority_status` (string): Optional confirmed fact. Ask whether the user can approve this price or discount. Free-text role titles do not establish authority; unconfirmed authority holds commitment to terms.
- `scenario` (string, required): Negotiation scenario
- `value_delivered` (string): Quantified value your solution delivers. Used in the value reframe, word for word; the guide adds no value figure of its own
- `your_leverage` (string): Your leverage points (unique features, timeline, etc.)
- `your_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string): Your product/solution. Named in the guide and used, with your leverage, to read the sector and how you charge

### `champion_enablement_kit` (~278 tokens)

Champion Enablement Kit

Writes an internal selling asset for your champion, such as an executive brief, an internal business case, objection responses or presentation talking points, built from your solution, the customer's situation and the objections you expect. Returns the asset in the champion's voice with the recommendation, the answers to likely questions, the decision requested, a note on the reader and sector notes. It invents no figure or quote.

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_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string, required): Your product/solution

### `competitive_trap_setter` (~293 tokens)

Competitive Trap Setter

Writes landmine questions and positioning tactics against a named competitor, so the buyer's own criteria expose its weak points without negative selling. Returns the set-up, your strengths and the competitor's weak points as you gave them, discovery questions, criteria to establish, reference call questions, requirement and scenario traps, commercial terms and stage-specific tactics, with sector notes. Every line comes from your inputs and the sector, and none from an invented fact about the competitor.

Input parameters:

- `business_model` (string): Optional: how you charge (software subscription, services, connectivity, per transaction, marketplace, hardware plus software, or investment management). Read from your other inputs when left out
- `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_sector` (string): Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
- `your_solution` (string, required): Your product/solution
- `your_strengths` (string): Your key differentiators

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/revenue-enablement#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 73
- 2026-10-19: 72
- 2026-10-18: 72
- 2026-10-17: 72

## Common questions

### 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. Revenue Enablement: 12 deal and sales enablement tools by Helix GTM Consulting. This page covers its hosted endpoint (https://revenue-enablement.gtmhelix.com/mcp).

### Is the io.github.shashwatgtm/revenue-enablement-mcp server safe to use?

io.github.shashwatgtm/revenue-enablement-mcp scores 80 out of 100 on VerifyMCP. 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 3,868 tokens of context every time the server is loaded.

### Does the io.github.shashwatgtm/revenue-enablement-mcp server require authentication?

No. We connected to io.github.shashwatgtm/revenue-enablement-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the io.github.shashwatgtm/revenue-enablement-mcp server?

VerifyMCP ran 13 checks on io.github.shashwatgtm/revenue-enablement-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://revenue-enablement.gtmhelix.com/mcp
- Repository: https://github.com/shashwatgtm/revenue-enablement-mcp
- Website: https://tools.gtmhelix.com/connectors/
- Changelog RSS feed: https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/revenue-enablement.xml
- Changelog JSON feed: https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/revenue-enablement/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/revenue-enablement.json
- HTML version of this page: https://verifymcp.io/servers/shashwatgtm-revenue-enablement-mcp/revenue-enablement