Remote MCP · Endpoint

gtm.help MCP server

No. gtm.help answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://gtm.help/mcp

The last check completed an MCP handshake.

Registry name
help.gtm/gtm-help
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.85 s
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Your go-to-market plan, plays and opportunities from gtm.help, inside any AI agent.
Listing
From the official MCP registry (active).
Recent checks of gtm.help
CheckedResultHandshake
43 minutes agoHandshake completed2.85 s
9 days agoHandshake completed1.80 s
10 days agoHandshake completed162 ms
11 days agoHandshake completed1.66 s
12 days agoHandshake completed1.82 s
14 days agoHandshake completed2.05 s
14 days agoHandshake completed1.15 s
15 days agoHandshake completed3.25 s
17 days agoHandshake completed2.11 s
19 days agoHandshake completed525 ms
21 days agoHandshake completed1.73 s
24 days agoHandshake completed2.03 s
26 days agoHandshake completed1.87 s
28 days agoHandshake completed3.07 s

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with gtm.help and makes no claim about it beyond what these checks measured.