marketinque MCP server

• Registry namecom.marketinque/launch-planverified in the MCP registry

The registry name sits under marketinque.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-19
• Tools8
• Server calls itselfmarketinque
• Server version46.0.0
• Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 195 ms.

• Its tools do none of the product's use cases we checked: Draft blog articles and LinkedIn posts from one pillar piece; Write a five-email welcome sequence for new signups.
• Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
• What an agent can do with it0 of 2 use cases
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer505 ms
• Space in an agent's context≈ 1,914 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsA · 98 of 100
• Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 1 of 8

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• whoami

  Which mode this connection is in — anonymous (read-only) or a project — and what that unlocks.

• join_waitlist

  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…

• get_plan

  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…

• get_step

  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…

• next_steps

  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.

• list_directories

  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…

• get_directory

  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)…

• get_submission_kit

  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.