Remote MCP · Endpoint

ai.artemisgtm/gtm-engineer MCP server

No. ai.artemisgtm/gtm-engineer answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://artemisgtm.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.artemisgtm/gtm-engineer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
263 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
GTM engineering consulting firm for seed to Series C startups. We build and run GTM systems.
Listing
From the official MCP registry (active).
Recent checks of ai.artemisgtm/gtm-engineer
CheckedResultHandshake
34 minutes agoHandshake completed263 ms
9 days agoHandshake completed809 ms
10 days agoHandshake completed266 ms
11 days agoHandshake completed244 ms
12 days agoHandshake completed232 ms
14 days agoHandshake completed454 ms
14 days agoHandshake completed342 ms
15 days agoHandshake completed501 ms
17 days agoHandshake completed304 ms
19 days agoHandshake completed235 ms
21 days agoHandshake completed292 ms
24 days agoHandshake completed317 ms
26 days agoHandshake completed348 ms

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

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 ai.artemisgtm/gtm-engineer and makes no claim about it beyond what these checks measured.