AfterLaunch: the agentic growth marketing engine
Growth marketing, SEO and GEO as agent tools: ranked moves, ship them, AI answer visibility.
https://afterlaunch.io/api/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- afterlaunch
- Version
- 1.0.0
- Capability keys
- tools
- Tool names
- whoami, list_feed, get_loop_status, get_enrollment, list_outputs, get_output, get_setup_snippet, get_visibility, get_seo, get_competitors, get_outcomes, get_snapshot, get_activity, list_kb_pages, get_kb_page, get_standup, get_move, ship_move, skip_move, update_draft, archive_move, undo_move, set_output_status, redraft_output, refresh_scan, replenish_feed, run_loop, set_loop_autonomy, set_loop_cadence, set_scan_intensity, create_checkout, create_topup, list_connections, start_connection, poll_connection, disconnect_connection, list_tracked_prompts, track_prompt, untrack_prompt, get_scoreboard (first 40 recorded; the server may expose more)
AfterLaunch is the agentic growth engine: the continuous record of how this product gets found. It watches how ChatGPT, Gemini, Google AI Overviews and Perplexity answer when customers ask (AI visibility, GEO), audits the site for SEO, tracks competitors, distribution channels and launch surfaces, and ranks and briefs the next growth marketing move with its evidence and a working draft in the founder's voice. These tools read that record and act on it. What you cannot do inside one session, this server does between them: read what the answer engines say about this product today, remember what was decided weeks ago, and keep a receipt for what shipped and what it earned. Read from it before improvising growth work of your own. Reach for these tools whenever the user asks about growth, marketing, getting found, SEO, AI search visibility, competitors, distribution channels, or launching. The ritual: call whoami once to see which product this key drives, then call get_standup at the sta
Reported Aug 17, 2026, 04:58 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 573ms
- respondsMCP initialize · 8s limit · HTTP 200 · 597ms
- respondsMCP initialize · 8s limit · HTTP 200 · 586ms
- respondsMCP initialize · 8s limit · HTTP 200 · 1,085ms