io.github.shashwatgtm/gtm-alpha-consultant
REMOTE · GTMALPHA.GTMHELIX.COM · 2 COMPONENTS
GTM Alpha: go to market consultation (EPIC) by Helix GTM Consulting
Available components
Last scanned (17 minutes ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 903 tokens (~301/item across 3 items; 3 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 Management63
- Stability observed for 19 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Tool “epic_audit” changed its title: EPIC scores (in Claude) → EPIC scores cosmetic
- Tool “generate_roadmap” changed its title: GTM Roadmap (in Claude) → GTM Roadmap cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 28 Oct 26 +1
- Tool “gtm_consultation” changed its title: Free EPIC audit (in your browser and in Claude) → EPIC motion scores and first 30 days cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 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.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://gtmalpha.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=gtmalpha.gtmhelix.com | CN=YE2,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6d88bab920c0183df53b8b713273e6b277d |
| SANs: gtmalpha.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 gtmalpha.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 |
| gtmalpha.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 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gtmalpha.gtmhelix.com/mcp | Verified | 200 | |
| http (plaintext) | http://gtmalpha.gtmhelix.com/mcp | HTTPS enforced | 301 | https://gtmalpha.gtmhelix.com/mcp |
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 →
epic_audit EPIC scores ~336
Get EPIC framework scores for your GTM strategy: Ecosystem and ABM, Product-Led Growth, Inbound and Outbound, Community-Led, each 1 to 10, with the lead motion, warnings and notes, and the sector's buying committee and usual objections when your inputs name the sector. Add the optional inputs for a full score; without them the result is marked preliminary.
| Name | Type | Req | Description |
|---|---|---|---|
| acv_usd | number | – | Optional. Average contract value per year in US dollars (for example 42000) |
| business_stage | string | – | Stage: pre-seed, seed, series-a, series-b, series-c, bootstrapped (growth counts as Series B) |
| challenge | string | yes | Describe your GTM situation |
| company_name | string | – | Optional. Your company or product name, repeated in the answer |
| current_channels | string | – | Optional. What you do today (content, outbound, events, partnerships, PLG, community) |
| deal_cycle_days | number | – | Optional. Days from first touch to closed-won (for example 120) |
| deal_source | string | – | Optional. Where the majority of deals come from |
| geography | string | – | Optional. Primary market |
| industry | string | – | Your industry |
| nrr_percent | number | – | Optional. Net revenue retention in percent (for example 108) |
| self_serve | boolean | – | Optional. true if customers can sign up and get value without talking to sales |
| tam_accounts | number | – | Optional. Number of addressable accounts (for example 2500) |
No output schema declared.
No examples provided.
generate_roadmap GTM Roadmap ~192
Return a GTM action plan for one EPIC motion (E Ecosystem and ABM, P Product-Led Growth, I Inbound and Outbound, C Community-Led) over 30, 60 or 90 days: immediate, short-term and medium-term steps, without the self-serve steps when your business model is not a software subscription. Builds text from the inputs only.
| Name | Type | Req | Description |
|---|---|---|---|
| business_model | string | – | Optional. How you charge: software subscription, services, connectivity, per transaction, marketplace, hardware plus software, or investment management. Steps that need a product people can try on th… |
| primary_focus | string | yes | EPIC motion to plan for: E, P, I or C |
| timeframe | string | – | 30-day, 60-day or 90-day (default 90-day) |
No output schema declared.
No examples provided.
gtm_consultation EPIC motion scores and first 30 days ~375
Scores the four motions from 1 to 10 with the documented rubric, names the primary and secondary motion, and lists the first 30 days of steps for the primary motion, with sector notes when your inputs name the sector. Add the optional inputs (ACV, deal cycle, NRR, TAM, self-serve, deal source, geography) for a full score; without them the result is marked preliminary.
| Name | Type | Req | Description |
|---|---|---|---|
| acv_usd | number | – | Optional. Average contract value per year in US dollars (for example 42000) |
| 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 |
| business_stage | string | – | Stage: pre-seed, seed, series-a, series-b, series-c, bootstrapped (growth counts as Series B) |
| company_name | string | – | Company name |
| current_channels | string | – | Optional. What you do today (content, outbound, events, partnerships, PLG, community) |
| deal_cycle_days | number | – | Optional. Days from first touch to closed-won (for example 120) |
| deal_source | string | – | Optional. Where the majority of deals come from |
| geography | string | – | Optional. Primary market |
| gtm_challenge | string | yes | Your GTM challenge |
| industry | string | – | Your industry |
| nrr_percent | number | – | Optional. Net revenue retention in percent (for example 108) |
| self_serve | boolean | – | Optional. true if customers can sign up and get value without talking to sales |
| tam_accounts | number | – | Optional. Number of addressable accounts (for example 2500) |
No output schema declared.
No examples provided.
How do I install the io.github.shashwatgtm/gtm-alpha-consultant MCP server?
io.github.shashwatgtm/gtm-alpha-consultant is a hosted endpoint at https://gtmalpha.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 · gtmalpha.gtmhelix.com
claude mcp add --transport http shashwatgtm-gtm-alpha-consultant 'https://gtmalpha.gtmhelix.com/mcp'
What is the io.github.shashwatgtm/gtm-alpha-consultant MCP server?
io.github.shashwatgtm/gtm-alpha-consultant is an MCP server listed in the public MCP registry as io.github.shashwatgtm/gtm-alpha-consultant. GTM Alpha: go to market consultation (EPIC) by Helix GTM Consulting. This page covers its hosted endpoint (https://gtmalpha.gtmhelix.com/mcp).
Is the io.github.shashwatgtm/gtm-alpha-consultant MCP server safe to use?
io.github.shashwatgtm/gtm-alpha-consultant scores 79 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/gtm-alpha-consultant MCP server expose?
io.github.shashwatgtm/gtm-alpha-consultant exposes 3 tools: gtm_consultation, epic_audit, generate_roadmap. Their descriptions and schemas cost roughly 903 tokens of context every time the server is loaded.
Does the io.github.shashwatgtm/gtm-alpha-consultant MCP server require authentication?
No. We connected to io.github.shashwatgtm/gtm-alpha-consultant without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.shashwatgtm/gtm-alpha-consultant MCP server still maintained?
io.github.shashwatgtm/gtm-alpha-consultant 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.