Remote MCP · Endpoint

io.github.shashwatgtm/impact-mcp MCP server

No. io.github.shashwatgtm/impact-mcp answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://impact.gtmhelix.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.shashwatgtm/impact-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.30 s
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
IMPACT: 8 B2B positioning and messaging tools by Helix GTM Consulting
Website
https://tools.gtmhelix.com/connectors/
Repository
https://github.com/shashwatgtm/impact-mcp
Listing
From the official MCP registry (active).
Recent checks of io.github.shashwatgtm/impact-mcp
CheckedResultHandshake
16 minutes agoHandshake completed1.30 s
9 days agoHandshake completed372 ms
9 days agoHandshake completed1.19 s
11 days agoHandshake completed602 ms
12 days agoHandshake completed2.73 s
13 days agoHandshake completed118 ms
14 days agoHandshake completed104 ms
14 days agoHandshake completed282 ms
16 days agoHandshake completed139 ms
19 days agoHandshake completed445 ms
21 days agoHandshake completed506 ms
24 days agoHandshake completed236 ms
26 days agoHandshake completed525 ms
28 days agoHandshake completed334 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.shashwatgtm/impact-mcp and makes no claim about it beyond what these checks measured.