AfterLaunch: the agentic growth marketing engine
REMOTE · AFTERLAUNCH.IO · SCANNED SEP 20
Growth marketing, SEO and GEO as agent tools: ranked moves, ship them, AI answer visibility.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7834 tokens (~139/item across 56 items; 56 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management96
- Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 1 breaking changes, 0 auth/transport breaks, 15 additions. See how to fix → Fail
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 57 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the AfterLaunch: the agentic growth marketing engine MCP server?
AfterLaunch: the agentic growth marketing engine is a hosted endpoint at https://afterlaunch.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · afterlaunch.io
claude mcp add --transport http io-afterlaunch-agentic-growth-marketing 'https://afterlaunch.io/api/mcp'
{
"mcpServers": {
"io-afterlaunch-agentic-growth-marketing": {
"url": "https://afterlaunch.io/api/mcp"
}
}
} {
"servers": {
"io-afterlaunch-agentic-growth-marketing": {
"type": "http",
"url": "https://afterlaunch.io/api/mcp"
}
}
} [mcp_servers.io-afterlaunch-agentic-growth-marketing] url = "https://afterlaunch.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-afterlaunch-agentic-growth-marketing": {
"type": "remote",
"url": "https://afterlaunch.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add io-afterlaunch-agentic-growth-marketing --url 'https://afterlaunch.io/api/mcp' --transport streamable-http
mcp_servers:
io-afterlaunch-agentic-growth-marketing:
url: "https://afterlaunch.io/api/mcp" {
"McpServers": {
"io-afterlaunch-agentic-growth-marketing": {
"Transport": "http",
"Url": "https://afterlaunch.io/api/mcp"
}
}
} assistant mcp add io-afterlaunch-agentic-growth-marketing -t streamable-http -u 'https://afterlaunch.io/api/mcp'
{
"mcpServers": {
"io-afterlaunch-agentic-growth-marketing": {
"type": "http",
"url": "https://afterlaunch.io/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 0
- Tool “get_business_context” rewrote its description, which is the text the model reads security
- 16 Sept 26 0
- Tool “record_content” rewrote its description, which is the text the model reads security
- New tool “get_experiments” functional
- 13 Sept 26 0
- “accept_move” reworded the description of “expected_legacy_state” cosmetic
- “review_move” reworded the description of “expected_legacy_state” cosmetic
- “ship_move” reworded the description of “expected_legacy_state” cosmetic
3 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 12 Sept 26 0
- Tool “get_move” rewrote its description, which is the text the model reads security
- Tool “record_content” rewrote its description, which is the text the model reads security
- “record_content” added an optional parameter “adopt_legacy” cosmetic
- “record_content” added an optional parameter “expected_updated_at” cosmetic
- “record_content” added an optional parameter “research” cosmetic
- 11 Sept 26 −1
- Tool coverage: 77% → 70% ▼ functional
- New tool “get_content_calendar” functional
- New tool “record_content” functional
- “redraft_output” added an optional parameter “draft_fence” cosmetic
- “update_draft” added an optional parameter “draft_fence” cosmetic
- 10 Sept 26 0
- Tool “get_output” rewrote its description, which is the text the model reads security
- 9 Sept 26 −1
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_move” rewrote its description, which is the text the model reads security
- Tool “list_queue” rewrote its description, which is the text the model reads security
- Tool “pick_up_job” rewrote its description, which is the text the model reads security
- Tool “report_job” rewrote its description, which is the text the model reads security
- Tool “ship_move” rewrote its description, which is the text the model reads security
- Tool coverage: 96% → 77% ▼ functional
- “pick_up_job” added a required parameter “attempt_id”, so existing callers break ▼ functional
- “report_job” added a required parameter “attempt_id”, so existing callers break ▼ functional
- “ship_move” added a required parameter “attempt_id”, so existing callers break ▼ functional
- “ship_move” added a required parameter “completion_kind”, so existing callers break ▼ functional
- “ship_move” added a required parameter “founder_confirmed”, so existing callers break ▼ functional
- “ship_move” added a required parameter “job_id”, so existing callers break ▼ functional
- New tool “accept_move” functional
- New tool “review_move” functional
- “report_job” added an optional parameter “prepared_content” cosmetic
- “ship_move” added an optional parameter “expected_legacy_state” cosmetic
- “ship_move” added an optional parameter “expected_legacy_updated_at” cosmetic
- “ship_move” added an optional parameter “expected_move_state” cosmetic
- “ship_move” added an optional parameter “expected_move_updated_at” cosmetic
- “ship_move” added an optional parameter “note” cosmetic
- “ship_move” added an optional parameter “published_url” cosmetic
- “report_job” reworded the description of “asset_url” cosmetic
- “ship_move” dropped the optional parameter “asset_url” cosmetic
- 7 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_move” rewrote its description, which is the text the model reads security
- Tool “list_feed” rewrote its description, which is the text the model reads security
- “list_feed” reworded the description of “verbosity” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://afterlaunch.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=afterlaunch.io | CN=YE1,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6bca2c8bf02047fd49a536f12b2873c6753 |
| SANs: *.afterlaunch.io, afterlaunch.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of afterlaunch.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| afterlaunch.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://afterlaunch.io/.well-known/oauth-protected-resource/api/mcp", scope="read act write"
Bearer resource_metadata="https://afterlaunch.io/.well-known/oauth-protected-resource/api/mcp", scope="read act write"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Protected resource metadata
| Document | https://afterlaunch.io/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://afterlaunch.io/api/mcp |
| Authorisation server | https://afterlaunch.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://afterlaunch.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://afterlaunch.io/api/mcp | HTTPS enforced | 301 | https://afterlaunch.io/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
start_connection ~140
Connect a growth data source or distribution channel: mint a one-time link the FOUNDER opens in their own browser to approve it. You never complete the consent yourself; it is bound to their session. Returns url (hand it to the founder), poll_token, poll_after_seconds and expires_at; the link lasts 15 minutes. Then poll_connection until it reports connected. Refuses in plain words, before minting anything, when a connector is shut on this account. Free, spends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Which connector to connect. Use a provider id from list_connections: ga4, gsc, gbp, linkedin or reddit. |
No output schema declared.
No examples provided.
track_prompt ~172
Add one buyer question to the AI visibility (GEO) set AfterLaunch measures this product on. Free, spends nothing. Two honest consequences: changing the set makes the NEXT scheduled scan run at full depth instead of skipping ahead, and it re-baselines the week-over-week trend, because a comparison across two different question sets is not a real move. So add deliberately rather than churning the list. 10 to 200 characters, deduplicated, hard cap of 15. Requires the 'config' scope and the Founder plan; on a free trial the questions stay readable and create_checkout mints the upgrade link.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The buyer question to track, as a real person would ask an AI assistant, e.g. "What is the best invoicing tool for UK freelancers?". |
No output schema declared.
No examples provided.
undo_move ~95
Restore a just-shipped or just-skipped growth move to pending: the self-correction verb for a wrong ship_move or skip_move. Free; requires the 'act' scope. Idempotent on a move already pending. It never unwinds a real channel publish: a posted output stays posted, and an archived or expired move cannot be restored.
| Name | Type | Req | Description |
|---|---|---|---|
| move_id | string | yes | Move id (uuid), from list_feed. |
No output schema declared.
No examples provided.
untrack_prompt ~120
Remove one buyer question from the AI visibility (GEO) set, freeing a slot against the cap of 15. Free, spends nothing. Same two honest consequences as track_prompt: the next scheduled scan runs at full depth, and the week-over-week trend re-baselines. Matched on the question text, ignoring case and punctuation, and IDEMPOTENT. Requires the 'config' scope and the Founder plan.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The tracked question to remove, from list_tracked_prompts. Matched ignoring case and punctuation. |
No output schema declared.
No examples provided.
update_draft ~114
Replace a pending growth move's marketing draft body before shipping. A draft carrying an unfilled placeholder or a broken link is refused rather than saved. Free; requires the 'act' scope.
| Name | Type | Req | Description |
|---|---|---|---|
| draft_content | string | yes | The replacement draft body, 1 to 20000 characters. |
| draft_fence | object | – | For a content pilot edit, return draft_fence unchanged from get_move or get_output. Refresh after a conflict. |
| move_id | string | yes | Move id (uuid), from list_feed. |
No output schema declared.
No examples provided.
whoami ~75
Confirm the AfterLaunch key works before any growth or marketing work: which product run it is bound to, its scopes, tier and trial_ends_at, plus onboarding (feed_ready is false while the Growth Snapshot deep scan is still building, so wait before reading the Feed) and credits once metering is live. Call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the AfterLaunch: the agentic growth marketing engine MCP server?
AfterLaunch: the agentic growth marketing engine is an MCP server listed in the public MCP registry as io.afterlaunch/agentic-growth-marketing. Growth marketing, SEO and GEO as agent tools: ranked moves, ship them, AI answer visibility. This page covers its hosted endpoint (https://afterlaunch.io/api/mcp).
Is the AfterLaunch: the agentic growth marketing engine MCP server safe to use?
AfterLaunch: the agentic growth marketing engine scores 90 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AfterLaunch: the agentic growth marketing engine MCP server expose?
AfterLaunch: the agentic growth marketing engine exposes 56 tools: get_content_calendar, record_content, get_experiments, whoami, list_feed, and 51 more. Their descriptions and schemas cost roughly 7,111 tokens of context every time the server is loaded.
Does the AfterLaunch: the agentic growth marketing engine MCP server require authentication?
Yes. AfterLaunch: the agentic growth marketing engine asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the AfterLaunch: the agentic growth marketing engine MCP server still maintained?
AfterLaunch: the agentic growth marketing engine is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.