Skip to content

marketinque — launch plan & backlink index MCP server

com.marketinque/launch-planmarketinque.comstreamable-httpv64.0.0Scanned

A 498-step SaaS launch plan and 958 backlink sources as tools an agent reads, acts on and records.

16 tools: 6 change things and 10 only read.

Tools: 0 delete, 0 irreversible, 6 write, 10 read.
  • Reads private data · 4
  • Reads text others write · 4
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the marketinque — launch plan & backlink index MCP server can do

The marketinque — launch plan & backlink index MCP server is published by marketinque.com, a domain the MCP Registry verified. It has 16 tools. It can create or change data (6 tools: join_waitlist, define_term, next_steps, whats_next and 2 more), but cannot delete data. 10 tools only read.

4 tools read private data (get_play, list_directories, get_directory and 1 more); 4 tools bring in text other people can write (get_step, get_play, search_plays and 1 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 7 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 64.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

16 tools

Changes things 6Claude Code: ask
  • define_termThe short definition of a marketing term from the library: the 28 glossary terms (MQL, CAC, dark funnel…), the 19 marketing disciplines and the 9 funnel frameworks (AIDA, AARRR, th…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The short definition of a marketing term from the library: the 28 glossary terms (MQL, CAC, dark funnel…), the 19 marketing disciplines and the 9 funnel frameworks (AIDA, AARRR, the flywheel…). Exact name or slug matches come first, then partial ones. Each match has its kind, definition, page URL and related pages. Read-only; no side effects.

    Annotations the server declares

    • readOnlyHint: true
  • do_marketingCall this FIRST when asked to "do my marketing", "automate user acquisition", "grow this", or to run the daily marketing routine.1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "do_marketing" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this FIRST when asked to "do my marketing", "automate user acquisition", "grow this", or to run the daily marketing routine. It returns the run sheet for the product’s stage: the recurring work due this week, the steps you can finish alone (packed into `minutes`), the ones to draft for the founder up to the send button, the founder’s own list, what to ask about past work, and the order to do it all in, with the rules for sending. `mode: "unattended"` is for a scheduled run with nobody there: no questions, no changes to the product, drafts go to the queue. Read-only; the work is done with the other tools it names.

    Annotations the server declares

    • readOnlyHint: true
  • join_waitlistPut the founder on the marketinque waitlist for a project (the idea queue, kit, dossier, signals, nightly routine — free for now, opening by waitlist).No findings

    Why it is in this group

    • The description's first verb is "put": a word for a change.
    Description, as the server wrote it
    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.
  • next_stepsThe next unlocked, unstarted steps in tree order, and a sprint packed into `minutes`.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The next unlocked, unstarted steps in tree order, and a sprint packed into `minutes`. Each step says its impact (1–3), whether it is on the core path, who can do it (agent, agent-drafts, founder) and whether it repeats. `core_only` keeps the minimum path; `who: "agent"` gives the batch an agent can finish alone. `this_week` lists recurring steps that are due again. Anonymous callers pass `done`/`not_applicable` (from marketinque.json) and `traits`; a project uses its own.

    Annotations the server declares

    • readOnlyHint: true
  • record_outcomeRecord the founder’s answer to “did it work?” for a play or plan step they ran: worked, some or nothing, and how many weeks since it shipped.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Record the founder’s answer to “did it work?” for a play or plan step they ran: worked, some or nothing, and how many weeks since it shipped. Only from the founder’s own words, after it has run two weeks or more; never your guess. whats_next and next_steps list what is due (outcomes_due, ask_outcomes). Answers are pooled across everyone who uses marketinque and shown per play once three different founders have answered, so the next founder learns what works; the note is never shown. A later answer replaces an earlier one.
  • whats_nextUse this when asked "what should I do next?" or "give me the next working idea".No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Use this when asked "what should I do next?" or "give me the next working idea". Works out the product’s stage (pass `stage`, or it is read from the plan); with no project, pass `product_url` and the site is checked first so what it already does is skipped; then returns the three best next steps for that stage, each with why now, how to do it (the play’s steps or the step’s own how-to), minutes, and how you will know it is done; one unfinished ship-ready basic beside them; and three library plays that suit the stage and audience. next_steps is the plain checklist in plan order; this is the recommendation. Read-only.

    Annotations the server declares

    • readOnlyHint: true
Only reads 10Show 10 read-only tools
  • get_directoryOne 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 p…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_directory" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_directory" says "get" and "directory": it reads files.
    • private-dataThe description's first sentence says "directory": it reads files.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_planThe launch plan.No findings

    Why it is in this group

    • The name "get_plan" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_playOne marketing play from the library in full: its type, summary, the reusable pattern, its own steps (or a note that the channel’s standard steps apply), constraints, who it suits, …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_play" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    • untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
    Description, as the server wrote it
    One marketing play from the library in full: its type, summary, the reusable pattern, its own steps (or a note that the channel’s standard steps apply), constraints, who it suits, what it costs, its standing (backed: a platform doc, law, study, dataset or tool doc was read, or a claim supports it; practitioner: only posts, threads or vendor material; our-idea: no source), each source with how well it was read, the wiki topics that list it and the plan steps that follow it. The slug comes from search_plays, get_topic, get_step or search_knowledge. Read-only; no side effects.

    Annotations the server declares

    • readOnlyHint: true
  • get_stepOne plan step in full: title, detail, the target URL where it happens, the play it follows (its URL and its text: summary, pattern, steps, constraints), the prerequisite slugs and …Reads text others writeNo findings

    Why it is in this group

    • The name "get_step" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    One plan step in full: title, detail, the target URL where it happens, the play it follows (its URL and its text: summary, pattern, steps, constraints), 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.

    Annotations the server declares

    • readOnlyHint: true
  • get_submission_kitWhat every directory form asks for, written once.Reads private dataNo findings

    Why it is in this group

    • The name "get_submission_kit" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "directory": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_topicOne wiki topic (a subject a founder looks up, e.g.No findings

    Why it is in this group

    • The name "get_topic" says "get": a word for reading.
    Description, as the server wrote it
    One wiki topic (a subject a founder looks up, e.g. "backlinks-and-directories", "retention-and-churn"): its two-sentence summary, every plan step it gathers in plan order grouped by objective (slug, title, detail, time), and for the topics with a written guide the 40–60 word answer it leads with (in_short), its question-shaped "Do it" sections with their steps in reading order (do_it; a section can name a step from outside the topic) and its FAQ; the plays that explain how, the source-checked claims with their sources and how well each was read, and the related topics. The same content as /wiki/<topic> and /wiki/<topic>.md. Read-only; no side effects.

    Annotations the server declares

    • readOnlyHint: true
  • list_directoriesPlaces that give a startup a backlink, one phase at a time in the order that works.Reads private dataNo findings

    Why it is in this group

    • The name "list_directories" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_directories" says "list" and "directory": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • search_knowledgeSearch the library: the source-checked claims behind the launch plan's statistics, and (with a `query`) the wiki topics, plays and defined terms that match.No findings

    Why it is in this group

    • The name "search_knowledge" says "search": a word for reading.
    Description, as the server wrote it
    Search the library: the source-checked claims behind the launch plan's statistics, and (with a `query`) the wiki topics, plays and defined terms that match. Each claim says what kind it is (standard, evidence, practitioner-consensus, our-take), how strong it is and why, when it was last checked, the sources it cites with how well each was read, and the plan steps that rely on it. `topics`, `plays` and `terms` are short records: open one with get_topic, get_play or define_term. Use it before quoting a number from the plan or from a marketing article. With no filters it returns the strongest claims first and no topics, plays or terms; with a `query` it matches every word in the claim, its sources and its correction note, and in a topic, play or term. Read-only; no side effects.

    Annotations the server declares

    • readOnlyHint: true
  • search_playsSearch the library of reusable marketing plays (product-agnostic patterns such as a Product Hunt campaign or a Reddit origin-story post).Reads text others writeNo findings

    Why it is in this group

    • The name "search_plays" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "search" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Search the library of reusable marketing plays (product-agnostic patterns such as a Product Hunt campaign or a Reddit origin-story post). Ranked: whole-word matches of `query`, title hits first; when no play matches every word, the plays matching most of them. Narrow with `type` (channel), `best_for` (audience), `traits` (the plan traits, mapped to audiences) and `funnel_stage`. With no query, library order (strongest first within a type). Each result: slug, title, type, summary, cost, standing, best_for and funnel_stage; open one with get_play. For "what should I do next", whats_next picks for the product’s stage. Read-only.

    Annotations the server declares

    • readOnlyHint: true
  • whoamiWhich mode this connection is in — anonymous (read-only) or a project — and what that unlocks.No findings

    Why it is in this group

    • The name "whoami" says "whoami": a word for reading.
    Description, as the server wrote it
    Which mode this connection is in — anonymous (read-only) or a project — and what that unlocks.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:42 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://marketinque.com/mcp: tools/list returned 16 tools to an anonymous client, including join_waitlist (write), define_term (write), next_steps (write), whats_next (write), do_marketing (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 3 to 6
  2. Nov 13, 2026
    • Tools that change things, listed without credentials: 2 to 3

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "do_marketing" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The description's first verb is "call": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added.+1 addedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 6.View diff
    • Tools that change things, listed without credentials: 3 to 6
  3. Tools1 added, 2 changed.+1 added~2 changedView diff
  4. Tools1 changed.~1 changedView diff
    • Changed:whats_nextChanges thingsdescriptioninputSchema
  5. Tools1 added, 2 changed.+1 added~2 changedView diff
  6. Tools1 changed.~1 changedView diff
  7. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
    • Tools that change things, listed without credentials: 2 to 3
  8. Tools4 added, 2 changed.+4 added~2 changedView diff
  9. Tools1 added.+1 addedView diff

Install

Pinned to version 64.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http launch-plan https://marketinque.com/mcp
claude mcp add --transport http launch-plan https://marketinque.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__launch-plan__whoami",
      "mcp__launch-plan__get_plan",
      "mcp__launch-plan__search_knowledge",
      "mcp__launch-plan__get_step",
      "mcp__launch-plan__get_topic",
      "mcp__launch-plan__get_play",
      "mcp__launch-plan__search_plays",
      "mcp__launch-plan__list_directories",
      "mcp__launch-plan__get_directory",
      "mcp__launch-plan__get_submission_kit"
    ],
    "ask": [
      "mcp__launch-plan__join_waitlist",
      "mcp__launch-plan__define_term",
      "mcp__launch-plan__next_steps",
      "mcp__launch-plan__whats_next",
      "mcp__launch-plan__do_marketing",
      "mcp__launch-plan__record_outcome"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as launch-plan. Review it before you use it.

Capability tags behind 6 rules
  • mcp__launch-plan__get_step untrusted-input
  • mcp__launch-plan__get_play private-data, untrusted-input
  • mcp__launch-plan__search_plays untrusted-input
  • mcp__launch-plan__list_directories private-data
  • mcp__launch-plan__get_directory private-data, untrusted-input
  • mcp__launch-plan__get_submission_kit private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.marketinque/launch-plan/verify?hash=83cfd1e8541b483ea654b497574c108bf72ddc236ecefd0b2d27640d2291703b" | jq -e '.changed == false'

Pinned hash 83cfd1e8541b, from Nov 21, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.marketinque/launch-plan/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.marketinque/launch-plan
[![Anlyon Radar](https://radar.anlyon.com/badge/com.marketinque/launch-plan.svg)](https://radar.anlyon.com/servers/com.marketinque/launch-plan)

Source: MCP Registry · repository. Synced Nov 21, 2026, 11:17 UTC.

marketinque — launch plan & backlink index MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the marketinque — launch plan & backlink index MCP server safe?

No scan can promise that. What its definitions show: 16 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the marketinque — launch plan & backlink index MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the marketinque — launch plan & backlink index MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the marketinque — launch plan & backlink index MCP server have?

16 tools: 6 write, 10 read. join_waitlist, define_term, next_steps, whats_next, do_marketing, record_outcome, whoami, get_plan and 8 more.

Does the marketinque — launch plan & backlink index MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the marketinque — launch plan & backlink index MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the marketinque — launch plan & backlink index MCP server changed its tools?

Yes, 7 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.