Home / MCP registry index / io.github.shashwatgtm/revenue-enablement-mcp
io.github.shashwatgtm/revenue-enablement-mcp
io.github.shashwatgtm/revenue-enablement-mcp in the official MCP registry.
Endpoint https://revenue-enablement.gtmhelix.com/mcp. Source: github.com/shashwatgtm/revenue-enablement-mcp.
The registry describes it as: Revenue Enablement: 12 deal and sales enablement tools by Helix GTM Consulting
We read its 12 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
account_plan_builder deal_strategy_coach discovery_question_bank roi_business_case_builder mutual_action_plan_generator win_loss_analyzer proposal_section_writer email_sequence_generator demo_script_builder pricing_negotiation_guide champion_enablement_kit competitive_trap_setter
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-shashwatgtm-revenue-enablement-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.