marketinque — launch plan & backlink index
REMOTE · MARKETINQUE.COM · SCANNED SEP 28
A 349-step SaaS launch plan and 958 backlink sources as tools an agent reads, acts on and records.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1597 tokens (~159/item across 10 items; 8 tools + 2 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the marketinque — launch plan & backlink index MCP server?
marketinque — launch plan & backlink index is a hosted endpoint at https://marketinque.com/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 · marketinque.com
claude mcp add --transport http com-marketinque-launch-plan 'https://marketinque.com/mcp'
{
"mcpServers": {
"com-marketinque-launch-plan": {
"url": "https://marketinque.com/mcp"
}
}
} {
"servers": {
"com-marketinque-launch-plan": {
"type": "http",
"url": "https://marketinque.com/mcp"
}
}
} [mcp_servers.com-marketinque-launch-plan] url = "https://marketinque.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-marketinque-launch-plan": {
"type": "remote",
"url": "https://marketinque.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-marketinque-launch-plan --url 'https://marketinque.com/mcp' --transport streamable-http
mcp_servers:
com-marketinque-launch-plan:
url: "https://marketinque.com/mcp" {
"McpServers": {
"com-marketinque-launch-plan": {
"Transport": "http",
"Url": "https://marketinque.com/mcp"
}
}
} assistant mcp add com-marketinque-launch-plan -t streamable-http -u 'https://marketinque.com/mcp'
{
"mcpServers": {
"com-marketinque-launch-plan": {
"type": "http",
"url": "https://marketinque.com/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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 36.0.0 → 37.0.0 functional
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Tool “join_waitlist” rewrote its description, which is the text the model reads security
- 23 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 35.0.0 → 36.0.0 functional
- 22 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_directory” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- New prompt “intake” functional
- Server version: 22.0.0 → 35.0.0 functional
- “list_directories” reworded the description of “unrecorded_only” cosmetic
- 21 Sept 26 68
First indexed and scored.
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 28 Sept 2026 · Probed https://marketinque.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=marketinque.com | CN=YE2,O=Let's Encrypt,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5c060133bba1e63af93fc148ad220dd0a96 |
| SANs: marketinque.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 marketinque.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| marketinque.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://marketinque.com/mcp | Verified | 200 | |
| http (plaintext) | http://marketinque.com/mcp | HTTPS enforced | 308 | https://marketinque.com/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 →
get_directory One directory ~121
One directory from the index: domain rating, dofollow, price, category, the submission page URL (or where to look for it), account_required (the page redirected to a sign-in when probed — most rows want a sign-in at submit anyway), founder_fills (a form an agent cannot drive), the note from the last session that worked it, and — for a project — the outcome already recorded. Read the note before opening the page. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The catalog slug, e.g. "saashub". |
No output schema declared.
No examples provided.
get_plan The launch plan ~242
The launch plan. With no `node`: the outline — phases and objectives with step counts. With `node` (a phase or objective slug): every step under it, with status and whether it is unlocked. Anonymous callers pass `done`/`not_applicable`/`traits`; a project uses its own.
| Name | Type | Req | Description |
|---|---|---|---|
| done | array | – | Step slugs already done — the "done" list of marketinque.json. Free tier only; a project's own ticks are used instead and this is ignored. |
| node | string | – | A phase or objective slug from the outline, e.g. "p2" or "p2-dr-assets". |
| not_applicable | array | – | Step slugs the founder ruled out — the "not_applicable" list of marketinque.json. Free tier only; ignored for a project. |
| traits | array | – | Product traits that decide which steps apply (b2b, b2c, ai-native, dev-tool, no-code, mcp, has-integrations, eu-traffic, mobile-app); omit for the generic plan. Free tier only; a project's saved trai… |
No output schema declared.
No examples provided.
get_step One step in full ~294
One plan step in full: title, detail, the target URL where it happens, the play it follows, the prerequisite slugs and whether they are met (unlocked), how it verifies (self, evidence URL or an automatic signal), minutes and cost, and founder_steps when part of the step is the founder’s own (an account, a handle): the exact page and what to do there, to hand over rather than do. Read it before working a step that next_steps or get_plan returned; the slug comes from those. Read-only; no side effects.
| Name | Type | Req | Description |
|---|---|---|---|
| done | array | – | Step slugs already done — the "done" list of marketinque.json. Free tier only; a project's own ticks are used instead and this is ignored. |
| not_applicable | array | – | Step slugs the founder ruled out — the "not_applicable" list of marketinque.json. Free tier only; ignored for a project. |
| slug | string | yes | The step slug exactly as get_plan or next_steps returned it, e.g. "p2-dest-alternatives". |
| traits | array | – | Product traits that decide which steps apply (b2b, b2c, ai-native, dev-tool, no-code, mcp, has-integrations, eu-traffic, mobile-app); omit for the generic plan. Free tier only; a project's saved trai… |
No output schema declared.
No examples provided.
get_submission_kit The submission kit ~51
What every directory form asks for, written once. A project returns its product profile and brand dossier plus the state of the five kit steps; anonymous callers get the five steps to draft from the product site.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
join_waitlist Ask for a marketinque project ~135
Put the founder on the marketinque waitlist for a project (the idea queue, kit, dossier, signals, nightly routine — free for now, opening by waitlist). Call ONLY after the founder gave you their email and said yes in this session; `confirmed` attests that. One email, no spam; they can unsubscribe from any mail.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | True only if the founder explicitly agreed to join, in this session. |
| string | yes | The founder’s email, as they gave it. | |
| product_url | string | – | Their product, so the invitation can refer to it. |
No output schema declared.
No examples provided.
list_directories Directories to submit to ~210
Places that give a startup a backlink, one phase at a time in the order that works. Default phase bl-sprint: the 95 free, dofollow, page-scoped, graded rows. Each row carries its submission page (or where to find it) and, for a project, the listing already recorded.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by the catalog category, e.g. "AI Tools", "Software Reviews". |
| limit | integer | – | Default 25. |
| min_dr | integer | – | Only rows with at least this domain rating (0–100). |
| offset | integer | – | Rows to skip, for paging past `limit`. |
| phase | string | – | bl-sprint (default) · bl-reach (free, nofollow/host-scoped) · bl-paid · bl-optional · bl-tail |
| unrecorded_only | boolean | – | Project only: skip rows already recorded — listed, submitted or skipped. The next batch, in one call. |
No output schema declared.
No examples provided.
next_steps What to do next ~267
The next unlocked, unstarted steps in tree order, and a sprint packed into `minutes`. Anonymous callers pass `done`/`not_applicable` (from marketinque.json) and `traits`; a project uses its own.
| Name | Type | Req | Description |
|---|---|---|---|
| checkable_only | boolean | – | Only steps with a target to record or an automatic check. |
| done | array | – | Step slugs already done — the "done" list of marketinque.json. Free tier only; a project's own ticks are used instead and this is ignored. |
| free_only | boolean | – | Only steps that cost nothing. |
| limit | integer | – | How many next steps to list (default 8). |
| minutes | integer | – | Time available now; the sprint is packed into it (default 120). |
| not_applicable | array | – | Step slugs the founder ruled out — the "not_applicable" list of marketinque.json. Free tier only; ignored for a project. |
| traits | array | – | Product traits that decide which steps apply (b2b, b2c, ai-native, dev-tool, no-code, mcp, has-integrations, eu-traffic, mobile-app); omit for the generic plan. Free tier only; a project's saved trai… |
No output schema declared.
No examples provided.
whoami Who is calling ~30
Which mode this connection is in — anonymous (read-only) or a project — and what that unlocks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the marketinque — launch plan & backlink index MCP server?
marketinque — launch plan & backlink index is an MCP server listed in the public MCP registry as com.marketinque/launch-plan. A 349-step SaaS launch plan and 958 backlink sources as tools an agent reads, acts on and records. This page covers its hosted endpoint (https://marketinque.com/mcp).
Is the marketinque — launch plan & backlink index MCP server safe to use?
marketinque — launch plan & backlink index scores 71 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 marketinque — launch plan & backlink index MCP server expose?
marketinque — launch plan & backlink index exposes 8 tools: whoami, join_waitlist, get_plan, get_step, next_steps, and 3 more. Their descriptions and schemas cost roughly 1,350 tokens of context every time the server is loaded.
Does the marketinque — launch plan & backlink index MCP server require authentication?
No. We connected to marketinque — launch plan & backlink index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the marketinque — launch plan & backlink index MCP server still maintained?
marketinque — launch plan & backlink index is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.