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/revenue-enablement-mcp

REMOTE · REVENUE-ENABLEMENT.GTMHELIX.COM · 2 COMPONENTS

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

+3 this week 80 Trust /100

Last scanned (23 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 4 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 26 +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.

  • 2 Nov 26 +1
    • 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 security
    • “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 “known_metrics” cosmetic
    • “roi_business_case_builder” reworded the description of “industry” cosmetic
    • “account_plan_builder” reworded the description of “known_contacts” cosmetic
  • 31 Oct 26 +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.

  • 29 Oct 26 0
    • “mutual_action_plan_generator” reworded the description of “known_process_steps” cosmetic
    • “account_plan_builder” reworded the description of “known_contacts” cosmetic
    • “mutual_action_plan_generator” reworded the description of “target_close_date” cosmetic

    3 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 28 Oct 26 +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.

  • 26 Oct 26 +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.

  • 24 Oct 26 +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.

  • 22 Oct 26 +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.

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 4 Nov 2026 · Probed https://revenue-enablement.gtmhelix.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=revenue-enablement.gtmhelix.com CN=YE2,O=Let's Encrypt,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA384 547e82fa23d3ca3bd3f6b3b694d3fd6e5de
SANs: revenue-enablement.gtmhelix.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of revenue-enablement.gtmhelix.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
gtmhelix.com. present 23401, 43960 13, 13 Verified
revenue-enablement.gtmhelix.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://revenue-enablement.gtmhelix.com/mcp Verified 200
http (plaintext) http://revenue-enablement.gtmhelix.com/mcp HTTPS enforced 301 https://revenue-enablement.gtmhelix.com/mcp
MCP tools · 12 exposed · ~3,868 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_plan_builder ~266

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.

NameTypeReqDescription
account_namestringyesCompany/account name
account_notesstring–Any additional context about the account
competitive_threatsstring–Known competitors in the account
current_arrnumber–Current ARR with this account (0 for prospects)
current_productsstring–Products/services they currently use from you
expansion_opportunitiesstring–Potential expansion areas or whitespace
industrystring–Industry vertical
known_contactsstring–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_sectorstring–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_solutionstring–Your product/service offering

No output schema declared.

No examples provided.

champion_enablement_kit ~278

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.

NameTypeReqDescription
asset_typestringyesType of enablement asset
budget_contextstring–Budget situation and pricing
champion_namestring–Champion name
champion_rolestring–Champion role/title
champion_winsstring–How this makes the champion look good
competitive_contextstring–Competitive alternatives being considered
key_value_pointsstring–Key value points to emphasize
known_objectionsstring–Expected objections from stakeholders
target_stakeholderstring–Who the champion needs to convince
urgency_driversstring–Why act now
your_sectorstring–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_solutionstringyesYour product/solution

No output schema declared.

No examples provided.

competitive_trap_setter ~293

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.

NameTypeReqDescription
business_modelstring–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_personastring–Role of key evaluator
buyer_prioritiesstring–What the buyer cares most about
competitorstringyesPrimary competitor to position against
competitor_weaknessesstring–Known competitor weaknesses
evaluation_stagestring–Stage of competitive evaluation
trap_typestring–Type of competitive positioning
your_sectorstring–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_solutionstringyesYour product/solution
your_strengthsstring–Your key differentiators

No output schema declared.

No examples provided.

deal_strategy_coach ~345

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.

NameTypeReqDescription
blocker_statusstring–Ask whether any blocker is present. A confirmed typed fact overrides word reading.
blockersstring–Known blockers or objections
champion_statusstring–Champion identification status
close_datestring–Target close date
competitorsstring–Competitors in the deal and their position
days_in_stagenumber–Days the deal has been in current stage
deal_namestringyesDeal/opportunity name
deal_stagestringyesCurrent deal stage
deal_valuenumber–Deal value in dollars
economic_buyerstring–Economic buyer name and engagement level
economic_buyer_engagementstring–Ask whether the budget holder actively participates in this decision. Overrides word reading.
incumbent_statusstring–Ask whether the buyer already uses a competing supplier. Overrides word reading.
next_stepsstring–Currently planned next steps
project_statusstring–Ask whether the project is still active. A cancelled project is held, without a close plan.
your_sectorstring–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_solutionstring–What you are selling

No output schema declared.

No examples provided.

demo_script_builder ~288

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.

NameTypeReqDescription
attendeesstring–Other attendees and their roles
competitor_contextstring–Competitor being displaced or compared
customer_industrystring–Customer industry
demo_durationnumber–Demo duration in minutes
demo_typestringyesType of demo
desired_outcomestring–What you want to achieve from this demo
key_pain_pointsstring–Pain points to address in demo
known_objectionsstring–Known objections to address
must_show_featuresstring–Features that must be demonstrated
primary_audiencestring–Primary demo audience (role/persona)
your_sectorstring–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_solutionstringyesYour product/solution

No output schema declared.

No examples provided.

discovery_question_bank ~291

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.

NameTypeReqDescription
contact_permissionstring–Optional confirmed fact. Ask whether this person permits further contact; this answer overrides contact-refusal wording in the notes.
deal_stagestring–Stage of conversation
frameworkstringyesDiscovery framework to use
gaps_to_fillstring–Specific information gaps to address
known_metricsstring–Metrics/KPIs already discussed
known_pain_pointsstring–Pain points already identified
prospect_industrystring–Prospect industry for context
prospect_rolestring–Role of person you are meeting with
your_sectorstring–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_solutionstring–Your product/solution for relevant questions

No output schema declared.

No examples provided.

email_sequence_generator ~335

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.

NameTypeReqDescription
call_to_actionstring–Desired action (meeting, demo, reply)
key_value_propstring–Primary value proposition
num_emailsnumber–Accepted but not used yet: each sequence type has a fixed number of emails
sender_contextstring–Context about sender (role, shared connections, etc.)
sequence_typestringyesType 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_proofstring–Customer names, stats, or proof points
specific_pain_pointstring–Specific pain point to address
target_industrystring–Target industry for context
target_personastringyesTarget persona (e.g., VP Sales, CTO, CFO)
tonestring–Email tone
your_sectorstring–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_solutionstringyesYour product/solution

No output schema declared.

No examples provided.

mutual_action_plan_generator ~266

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

NameTypeReqDescription
blockersstring–Known blockers or concerns
buyer_championstring–Champion name and title
current_stagestring–Current deal stage
deal_namestringyesDeal/opportunity name
economic_buyerstring–Economic buyer name and title
known_process_stepsstring–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_requirementsstring–Known requirements or evaluation criteria
procurement_contactstring–Procurement contact if known
target_close_datestringyesTarget close date (YYYY-MM-DD). A Saturday or Sunday date moves to the Friday before, and the plan says so
technical_evaluatorsstring–Technical evaluators involved
your_sectorstring–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_solutionstring–What you are selling

No output schema declared.

No examples provided.

pricing_negotiation_guide ~353

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.

NameTypeReqDescription
approval_authoritystring–Who has final approval on pricing
business_modelstring–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_leveragestring–Buyer leverage points (size, reference potential, etc.)
competitor_pricestring–Competitor pricing if known
deal_valuenumber–Current deal value
decision_timelinestring–When decision needs to be made
discount_requestednumber–Discount percentage requested
pricing_authority_statusstring–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.
scenariostringyesNegotiation scenario
value_deliveredstring–Quantified value your solution delivers. Used in the value reframe, word for word; the guide adds no value figure of its own
your_leveragestring–Your leverage points (unique features, timeline, etc.)
your_sectorstring–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_solutionstring–Your product/solution. Named in the guide and used, with your leverage, to read the sector and how you charge

No output schema declared.

No examples provided.

proposal_section_writer ~282

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.

NameTypeReqDescription
customer_challengesstring–Key challenges identified
customer_industrystring–Customer industry
customer_namestring–Customer name
implementation_approachstring–How you will implement
key_differentiatorsstring–Why you vs alternatives
pricingstring–Pricing details if relevant
primary_audiencestring–Adds a one-line note at the top of the executive summary on what this audience looks for
section_typestringyesProposal section to generate
success_metricsstring–Expected outcomes/metrics
tonestring–Tone for the proposal (changes only the opening of the executive summary)
your_sectorstring–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_solutionstringyesYour product/solution

No output schema declared.

No examples provided.

roi_business_case_builder ~575

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.

NameTypeReqDescription
annual_cash_benefitnumber–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_revenuenumber–Customer annual revenue. Shown as your input; it is not turned into a value
annual_value_estimatenumber–Optional: the buyer's own estimate of the annual value in dollars; used as the value when given
company_sizestring–Company size tier
current_annual_costnumber–Optional: what the problem or the current process costs the buyer a year, in dollars (their figure)
current_processstring–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_namestring–Customer/prospect name
employee_countnumber–Number of employees. Shown as your input; it is not turned into a value
expected_improvement_percentnumber–Optional: the share of that annual cost the buyer expects to save, in percent (their figure)
implementation_timelinestring–Expected implementation time. Shown in the output; not used in the calculation
industrystring–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_metricsstring–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_driverstringyesPrimary value category
solution_pricenumber–Annual cost of your solution
your_sectorstring–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_solutionstringyesYour product/solution

No output schema declared.

No examples provided.

win_loss_analyzer ~296

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.

NameTypeReqDescription
analysis_typestringyesType of analysis
competitor_wonstring–Competitor who won (if applicable)
deal_detailsstring–Deal details, can be rough notes, CRM export, or structured data
deal_outcomestring–Deal outcome for single deal analysis
deal_valuenumber–Deal value
loss_reasonstring–Stated loss reason (for lost deals)
multiple_dealsstring–For portfolio analysis: summary of multiple deals
sales_cycle_daysnumber–Length of sales cycle
stakeholders_involvedstring–Key stakeholders and their positions
your_sectorstring–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_solutionstring–What you were selling

No output schema declared.

No examples provided.

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.

remote · revenue-enablement.gtmhelix.com

# add to Claude Code
claude mcp add --transport http shashwatgtm-revenue-enablement-mcp 'https://revenue-enablement.gtmhelix.com/mcp'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.