Remote MCP · Endpoint
AfterLaunch: the agentic growth marketing engine MCP server
No. AfterLaunch: the agentic growth marketing engine answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://afterlaunch.io/api/mcp
The last check completed an MCP handshake.
- Registry name
- io.afterlaunch/agentic-growth-marketing
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 295 ms
- Tools exposed
- 58 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Growth marketing, SEO and GEO as agent tools: ranked moves, ship them, AI answer visibility.
- Website
- https://afterlaunch.io/
- Repository
- https://github.com/afterlaunch/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 295 ms |
| 1 day ago | Handshake completed | 611 ms |
| 2 days ago | Handshake completed | 467 ms |
| 3 days ago | Handshake completed | 321 ms |
| 4 days ago | Handshake completed | 348 ms |
| 5 days ago | Handshake completed | 283 ms |
| 6 days ago | Handshake completed | 490 ms |
| 9 days ago | Handshake completed | 235 ms |
| 11 days ago | Handshake completed | 255 ms |
| 14 days ago | Handshake completed | 461 ms |
| 16 days ago | Handshake completed | 379 ms |
| 18 days ago | Handshake completed | 313 ms |
| 20 days ago | Handshake completed | 415 ms |
| 22 days ago | Handshake completed | 252 ms |
| 24 days ago | Handshake completed | 316 ms |
| 26 days ago | Handshake completed | 295 ms |
| 27 days ago | Handshake completed | 309 ms |
| 29 days ago | Handshake completed | 709 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 AfterLaunch: the agentic growth marketing engine and makes no claim about it beyond what these checks measured.