_ registry / mcp streamable-http · checked 2h ago

revenue-enablement-mcp

https://revenue-enablement.gtmhelix.com

Registry code: 3723767981052e98

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://revenue-enablement.gtmhelix.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is revenue-enablement-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is revenue-enablement-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does revenue-enablement-mcp have?
12 tools: demo_script_builder, pricing_negotiation_guide, competitive_trap_setter, account_plan_builder, champion_enablement_kit, deal_strategy_coach, discovery_question_bank, roi_business_case_builder, ….
Is revenue-enablement-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
2,043ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 12 tools
12 never probed 0 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • demo_script_builder unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "demo_type",
    "your_solution"
  ],
  "properties": {
    "attendees": {
      "type": "string",
      "description": "Other attendees and their roles"
    },
    "demo_type": {
      "enum": [
        "first_look",
        "technical_deep_dive",
        "executive_overview",
        "competitive_displacement",
        "expansion_upsell",
        "proof_of_concept"
      ],
      "type": "string",
      "description": "Type of demo"
    },
    "demo_duration": {
      "type": "number",
      "minimum": 0,
      "description": "Demo duration in minutes"
    },
    "your_solution": {
      "type": "string",
      "description": "Your product/solution"
    },
    "desired_outcome": {
      "type": "string",
      "description": "What you want to achieve from this demo"
    },
    "key_pain_points": {
      "type": "string",
      "description": "Pain points to address in demo"
    },
    "known_objections": {
      "type": "string",
      "description": "Known objections to address"
    },
    "primary_audience": {
      "type": "string",
      "description": "Primary demo audience (role/persona)"
    },
    "customer_industry": {
      "type": "string",
      "description": "Customer industry"
    },
    "competitor_context": {
      "type": "string",
      "description": "Competitor being displaced or compared"
    },
    "must_show_features": {
      "type": "string",
      "description": "Features that must be demonstrated"
    }
  }
}
    arguments 62 lines
  • pricing_negotiation_guide unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "scenario"
  ],
  "properties": {
    "scenario": {
      "enum": [
        "discount_request",
        "budget_objection",
        "competitor_pricing",
        "procurement_pressure",
        "multi_year_negotiation",
        "enterprise_agreement",
        "renewal_negotiation"
      ],
      "type": "string",
      "description": "Negotiation scenario"
    },
    "deal_value": {
      "type": "number",
      "minimum": 0,
      "description": "Current deal value"
    },
    "your_leverage": {
      "type": "string",
      "description": "Your leverage points (unique features, timeline, etc.)"
    },
    "your_solution": {
      "type": "string",
      "description": "Accepted but not used yet by this tool"
    },
    "business_model": {
      "enum": [
        "saas",
        "services",
        "connectivity",
        "transactions",
        "marketplace",
        "hardware_software",
        "investment"
      ],
      "type": "string",
      "description": "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": {
      "type": "string",
      "description": "Buyer leverage points (size, reference potential, etc.)"
    },
    "value_delivered": {
      "type": "string",
      "description": "Quantified value your solution delivers. Shown in the output; the value example does not use it"
    },
    "competitor_price": {
      "type": "string",
      "description": "Competitor pricing if known"
    },
    "decision_timeline": {
      "type": "string",
      "description": "When decision needs to be made"
    },
    "approval_authority": {
      "type": "string",
      "description": "Who has final approval on pricing"
    },
    "discount_requested": {
      "type": "number",
      "minimum": 0,
      "description": "Discount percentage requested"
    }
  }
}
    arguments 72 lines
  • competitive_trap_setter unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "competitor",
    "your_solution"
  ],
  "properties": {
    "trap_type": {
      "enum": [
        "discovery_questions",
        "evaluation_criteria",
        "reference_questions",
        "technical_requirements",
        "commercial_terms",
        "all"
      ],
      "type": "string",
      "description": "Type of competitive positioning"
    },
    "competitor": {
      "type": "string",
      "description": "Primary competitor to position against"
    },
    "buyer_persona": {
      "type": "string",
      "description": "Role of key evaluator"
    },
    "your_solution": {
      "type": "string",
      "description": "Your product/solution"
    },
    "business_model": {
      "enum": [
        "saas",
        "services",
        "connectivity",
        "transactions",
        "marketplace",
        "hardware_software",
        "investment"
      ],
      "type": "string",
      "description": "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"
    },
    "your_strengths": {
      "type": "string",
      "description": "Your key differentiators"
    },
    "buyer_priorities": {
      "type": "string",
      "description": "What the buyer cares most about"
    },
    "evaluation_stage": {
      "enum": [
        "early",
        "mid",
        "late",
        "finalist"
      ],
      "type": "string",
      "description": "Stage of competitive evaluation"
    },
    "competitor_weaknesses": {
      "type": "string",
      "description": "Known competitor weaknesses"
    }
  }
}
    arguments 68 lines
  • account_plan_builder unknown 2h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "account_name"
  ],
  "properties": {
    "industry": {
      "type": "string",
      "description": "Industry vertical"
    },
    "current_arr": {
      "type": "number",
      "minimum": 0,
      "description": "Current ARR with this account (0 for prospects)"
    },
    "account_name": {
      "type": "string",
      "description": "Company/account name"
    },
    "account_notes": {
      "type": "string",
      "description": "Any additional context about the account"
    },
    "your_solution": {
      "type": "string",
      "description": "Your product/service offering"
    },
    "known_contacts": {
      "type": "string",
      "description": "Known contacts and their roles (can be rough notes)"
    },
    "current_products": {
      "type": "string",
      "description": "Products/services they currently use from you"
    },
    "competitive_threats": {
      "type": "string",
      "description": "Known competitors in the account"
    },
    "expansion_opportunities": {
      "type": "string",
      "description": "Potential expansion areas or whitespace"
    }
  }
}
    arguments 45 lines
  • champion_enablement_kit unknown 2h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "asset_type",
    "your_solution"
  ],
  "properties": {
    "asset_type": {
      "enum": [
        "executive_brief",
        "internal_business_case",
        "objection_responses",
        "presentation_talking_points",
        "email_to_stakeholder",
        "roi_one_pager",
        "competitive_comparison",
        "risk_assessment"
      ],
      "type": "string",
      "description": "Type of enablement asset"
    },
    "champion_name": {
      "type": "string",
      "description": "Champion name"
    },
    "champion_role": {
      "type": "string",
      "description": "Champion role/title"
    },
    "champion_wins": {
      "type": "string",
      "description": "How this makes the champion look good"
    },
    "your_solution": {
      "type": "string",
      "description": "Your product/solution"
    },
    "budget_context": {
      "type": "string",
      "description": "Budget situation and pricing"
    },
    "urgency_drivers": {
      "type": "string",
      "description": "Why act now"
    },
    "key_value_points": {
      "type": "string",
      "description": "Key value points to emphasize"
    },
    "known_objections": {
      "type": "string",
      "description": "Expected objections from stakeholders"
    },
    "target_stakeholder": {
      "type": "string",
      "description": "Who the champion needs to convince"
    },
    "competitive_context": {
      "type": "string",
      "description": "Competitive alternatives being considered"
    }
  }
}
    arguments 63 lines
  • deal_strategy_coach unknown 2h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "deal_name",
    "deal_stage"
  ],
  "properties": {
    "blockers": {
      "type": "string",
      "description": "Known blockers or objections"
    },
    "deal_name": {
      "type": "string",
      "description": "Deal/opportunity name"
    },
    "close_date": {
      "type": "string",
      "description": "Target close date"
    },
    "deal_stage": {
      "enum": [
        "prospecting",
        "discovery",
        "demo",
        "proposal",
        "negotiation",
        "closing",
        "stuck"
      ],
      "type": "string",
      "description": "Current deal stage"
    },
    "deal_value": {
      "type": "number",
      "minimum": 0,
      "description": "Deal value in dollars"
    },
    "next_steps": {
      "type": "string",
      "description": "Currently planned next steps"
    },
    "competitors": {
      "type": "string",
      "description": "Competitors in the deal and their position"
    },
    "days_in_stage": {
      "type": "number",
      "minimum": 0,
      "description": "Days the deal has been in current stage"
    },
    "your_solution": {
      "type": "string",
      "description": "What you are selling"
    },
    "economic_buyer": {
      "type": "string",
      "description": "Economic buyer name and engagement level"
    },
    "champion_status": {
      "enum": [
        "no_champion",
        "potential_champion",
        "confirmed_champion",
        "multi_threaded"
      ],
      "type": "string",
      "description": "Champion identification status"
    }
  }
}
    arguments 70 lines
  • discovery_question_bank unknown never probed

    Get contextual discovery questions using MEDDPICC, BANT, SPICED, Challenger or Gap Selling, or all five at once. Questions adapt based on what you already know about the prospect.

    mcp-tool

    {
  "type": "object",
  "required": [
    "framework"
  ],
  "properties": {
    "framework": {
      "enum": [
        "meddpicc",
        "bant",
        "spiced",
        "challenger",
        "gap_selling",
        "all"
      ],
      "type": "string",
      "description": "Discovery framework to use"
    },
    "deal_stage": {
      "enum": [
        "first_call",
        "discovery",
        "deep_dive",
        "technical",
        "executive"
      ],
      "type": "string",
      "description": "Stage of conversation"
    },
    "gaps_to_fill": {
      "type": "string",
      "description": "Specific information gaps to address"
    },
    "known_metrics": {
      "type": "string",
      "description": "Metrics/KPIs already discussed"
    },
    "prospect_role": {
      "type": "string",
      "description": "Role of person you are meeting with"
    },
    "your_solution": {
      "type": "string",
      "description": "Your product/solution for relevant questions"
    },
    "known_pain_points": {
      "type": "string",
      "description": "Pain points already identified"
    },
    "prospect_industry": {
      "type": "string",
      "description": "Prospect industry for context"
    }
  }
}
    arguments 55 lines
  • roi_business_case_builder unknown never probed

    Build an ROI business case from your inputs: the annual value comes from the buyer's own figures when you give them (annual_value_estimate, or current_annual_cost with expected_improvement_percent); otherwise from example assumptions and benchmarks labelled for you to replace. Includes ROI, payback and an executive summary.

    mcp-tool

    {
  "type": "object",
  "required": [
    "your_solution",
    "primary_value_driver"
  ],
  "properties": {
    "industry": {
      "type": "string",
      "description": "Industry for the example benchmarks: Technology, Financial_Services, Healthcare, Manufacturing or Retail (exact spelling). Any other value uses Technology"
    },
    "company_size": {
      "enum": [
        "startup",
        "smb",
        "mid_market",
        "enterprise"
      ],
      "type": "string",
      "description": "Company size tier"
    },
    "customer_name": {
      "type": "string",
      "description": "Customer/prospect name"
    },
    "known_metrics": {
      "type": "string",
      "description": "Metrics the prospect shared. Shown in the output; to turn them into the value, give current_annual_cost and expected_improvement_percent, or annual_value_estimate"
    },
    "your_solution": {
      "type": "string",
      "description": "Your product/solution"
    },
    "annual_revenue": {
      "type": "number",
      "minimum": 0,
      "description": "Customer annual revenue"
    },
    "employee_count": {
      "type": "number",
      "minimum": 0,
      "description": "Number of employees"
    },
    "solution_price": {
      "type": "number",
      "minimum": 0,
      "description": "Annual cost of your solution"
    },
    "current_process": {
      "type": "string",
      "description": "How they do it today. Shown in the output; not used in the calculation"
    },
    "current_annual_cost": {
      "type": "number",
      "minimum": 0,
      "description": "Optional: what the problem or the current process costs the buyer a year, in dollars (their figure)"
    },
    "primary_value_driver": {
      "enum": [
        "revenue_increase",
        "cost_reduction",
        "productivity",
        "risk_mitigation",
        "multiple"
      ],
      "type": "string",
      "description": "Primary value category"
    },
    "annual_value_estimate": {
      "type": "number",
      "minimum": 0,
      "description": "Optional: the buyer's own estimate of the annual value in dollars; used as the value when given"
    },
    "implementation_timeline": {
      "type": "string",
      "description": "Expected implementation time. Shown in the output; not used in the calculation"
    },
    "expected_improvement_percent": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Optional: the share of that annual cost the buyer expects to save, in percent (their figure)"
    }
  }
}
    arguments 85 lines
  • mutual_action_plan_generator unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "deal_name",
    "target_close_date"
  ],
  "properties": {
    "blockers": {
      "type": "string",
      "description": "Known blockers or concerns"
    },
    "deal_name": {
      "type": "string",
      "description": "Deal/opportunity name"
    },
    "current_stage": {
      "enum": [
        "discovery",
        "evaluation",
        "proposal",
        "negotiation",
        "procurement"
      ],
      "type": "string",
      "description": "Current deal stage"
    },
    "your_solution": {
      "type": "string",
      "description": "What you are selling"
    },
    "buyer_champion": {
      "type": "string",
      "description": "Champion name and title"
    },
    "economic_buyer": {
      "type": "string",
      "description": "Economic buyer name and title"
    },
    "target_close_date": {
      "type": "string",
      "description": "Target close date (YYYY-MM-DD)"
    },
    "known_requirements": {
      "type": "string",
      "description": "Known requirements or evaluation criteria"
    },
    "known_process_steps": {
      "type": "string",
      "description": "Known steps in their buying process"
    },
    "procurement_contact": {
      "type": "string",
      "description": "Procurement contact if known"
    },
    "technical_evaluators": {
      "type": "string",
      "description": "Technical evaluators involved"
    }
  }
}
    arguments 60 lines
  • win_loss_analyzer unknown never probed

    Structure a win/loss review of one deal or a set of deals: organizes the deal details you provide and returns the factors and questions to investigate.

    mcp-tool

    {
  "type": "object",
  "required": [
    "analysis_type"
  ],
  "properties": {
    "deal_value": {
      "type": "number",
      "minimum": 0,
      "description": "Deal value"
    },
    "loss_reason": {
      "type": "string",
      "description": "Stated loss reason (for lost deals)"
    },
    "deal_details": {
      "type": "string",
      "description": "Deal details, can be rough notes, CRM export, or structured data"
    },
    "deal_outcome": {
      "enum": [
        "won",
        "lost",
        "no_decision",
        "mixed"
      ],
      "type": "string",
      "description": "Deal outcome for single deal analysis"
    },
    "analysis_type": {
      "enum": [
        "single_deal",
        "deal_portfolio",
        "competitor_analysis",
        "loss_pattern"
      ],
      "type": "string",
      "description": "Type of analysis"
    },
    "your_solution": {
      "type": "string",
      "description": "What you were selling"
    },
    "competitor_won": {
      "type": "string",
      "description": "Competitor who won (if applicable)"
    },
    "multiple_deals": {
      "type": "string",
      "description": "For portfolio analysis: summary of multiple deals"
    },
    "sales_cycle_days": {
      "type": "number",
      "minimum": 0,
      "description": "Length of sales cycle"
    },
    "stakeholders_involved": {
      "type": "string",
      "description": "Key stakeholders and their positions"
    }
  }
}
    arguments 62 lines
  • proposal_section_writer unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "section_type",
    "your_solution"
  ],
  "properties": {
    "tone": {
      "enum": [
        "formal",
        "consultative",
        "bold",
        "conservative"
      ],
      "type": "string",
      "description": "Tone for the proposal (changes only the opening of the executive summary)"
    },
    "pricing": {
      "type": "string",
      "description": "Pricing details if relevant"
    },
    "section_type": {
      "enum": [
        "executive_summary",
        "problem_statement",
        "solution_overview",
        "implementation_plan",
        "pricing_justification",
        "risk_mitigation",
        "success_metrics",
        "company_overview",
        "case_studies",
        "next_steps"
      ],
      "type": "string",
      "description": "Proposal section to generate"
    },
    "customer_name": {
      "type": "string",
      "description": "Customer name"
    },
    "your_solution": {
      "type": "string",
      "description": "Your product/solution"
    },
    "success_metrics": {
      "type": "string",
      "description": "Expected outcomes/metrics"
    },
    "primary_audience": {
      "enum": [
        "c_suite",
        "vp_level",
        "director",
        "manager",
        "technical",
        "procurement"
      ],
      "type": "string",
      "description": "Accepted but not used yet: the text is the same for every audience"
    },
    "customer_industry": {
      "type": "string",
      "description": "Customer industry"
    },
    "customer_challenges": {
      "type": "string",
      "description": "Key challenges identified"
    },
    "key_differentiators": {
      "type": "string",
      "description": "Why you vs alternatives"
    },
    "implementation_approach": {
      "type": "string",
      "description": "How you will implement"
    }
  }
}
    arguments 79 lines
  • email_sequence_generator unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "sequence_type",
    "target_persona",
    "your_solution"
  ],
  "properties": {
    "tone": {
      "enum": [
        "professional",
        "casual",
        "urgent",
        "consultative",
        "provocative"
      ],
      "type": "string",
      "description": "Email tone"
    },
    "num_emails": {
      "type": "number",
      "minimum": 0,
      "description": "Accepted but not used yet: each sequence type has a fixed number of emails"
    },
    "social_proof": {
      "type": "string",
      "description": "Customer names, stats, or proof points"
    },
    "sequence_type": {
      "enum": [
        "cold_outreach",
        "warm_follow_up",
        "post_demo",
        "proposal_follow_up",
        "re_engagement",
        "nurture",
        "event_follow_up",
        "referral_request"
      ],
      "type": "string",
      "description": "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"
    },
    "your_solution": {
      "type": "string",
      "description": "Your product/solution"
    },
    "call_to_action": {
      "type": "string",
      "description": "Desired action (meeting, demo, reply)"
    },
    "key_value_prop": {
      "type": "string",
      "description": "Primary value proposition"
    },
    "sender_context": {
      "type": "string",
      "description": "Context about sender (role, shared connections, etc.)"
    },
    "target_persona": {
      "type": "string",
      "description": "Target persona (e.g., VP Sales, CTO, CFO)"
    },
    "target_industry": {
      "type": "string",
      "description": "Target industry for context"
    },
    "specific_pain_point": {
      "type": "string",
      "description": "Specific pain point to address"
    }
  }
}
    arguments 72 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3723767981052e98.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3723767981052e98/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3723767981052e98/badge.svg)](https://brick.blue/agent/3723767981052e98?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on gtmhelix.com 5 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.