Buyer questions, CLIs and MCP servers
The questions that decide which server an agent installs.
Four kinds of question decide what gets installed, and three of them never carry a brand name. Here they are asked by a developer, and increasingly by an agent acting for one, which is why the same sentence has to satisfy two readers. Everything here is runnable without us.
One rung in four carries a brand name. The other three decide the category without one, which is why a branded search report reads clean while the category is being lost.
91.5%
of AI citations point off-site
901 citations, 60 answers, 82 hosts. Our own measurement.
9.9pp
minimum lift the instrument can detect
At 40 queries by 40 samples. Anything smaller is unproven.
7 of 12
queries flipped outcome across identical repeats
One model, five repeats each. A single read is a coin flip.
The short version
One definition, in a paragraph a model can quote.
Definition first, under sixty words, no pronoun pointing at anything outside itself. It is the same shape we build for clients, on our own page, which is the only honest way to sell it.
Short answer
What are the money queries for a CLI or an MCP server?
A money query is an install-intent question asked by a developer or by an agent acting for one. Money queries for command-line tools and MCP servers fall into four kinds: the category question, the head to head, the constraint question, and the task question. Registries, lists and threads decide all four.
bestIntent { your category }Category for productionConstraint no brandBrand
Everything a buyer needed to decide is in the string, and none of it is your name. The answer supplies the missing part, which is the part you are selling.
The four rungs
Four kinds of question, and three of them never say your name.
Sorted by how much of the install decision each one carries. This is the one vertical where the same question is asked by a human choosing a tool and by an agent choosing whether to call it, so one list serves both.
The category question
No brand name
- best mcp server for postgres
- mcp servers for github issues
- which mcp server should i install
- What decides it
- Registries, awesome-lists and roundups. The canonical index a model consults before it recommends anything installable, plus whichever list has gone deepest on your specific thing.
- Who holds it today
- Whoever the registry and the lists agree on. Being present in a registry makes you findable rather than cited, which is the distinction this rung turns on.
The head to head
Carries a brand name
- yourcli.example alternatives
- yourcli.example vs incumbent.example
- which postgres mcp server is safer for production
- What decides it
- Comparison posts, threads and the write-ups of somebody who has run both. In this vertical the deepest comparison is often a personal blog with a small readership and a citation on every engine.
- Who holds it today
- Whoever the question names, plus whoever the comparisons set opposite them. Being the named alternative is a real position and it is the most winnable rung here.
The constraint question
No brand name
- read only mcp server for production
- mcp server that needs no api key
- cli for tailing kubernetes logs
- What decides it
- Your README and your tool manifest, read as facts. A constraint question is answered by whichever description states the permission model, the auth requirement or the install command plainly enough to be quoted.
- Who holds it today
- Frequently nobody in particular, and this is the rung where the manifest pass pays for itself, because the text an agent reads at selection time is the text that answers it.
The task question
No brand name
- how do i add an mcp server to my client
- why does my mcp server not appear in the tool list
- install a cli without a package manager
- What decides it
- Community threads, issue trackers and the install block at the top of a README.
- Who holds it today
- Usually unclaimed. It carries the most volume and the least brand intent, and it is where a server gets recommended inside an answer to a question that was never about servers.
Only the second rung carries a brand name, and on your category it is usually somebody else's. The other three settle what gets installed without your name being typed once.
One query, all the way through
The answer is written before your buyer reaches your site.
One question from the first rung, taken end to end. The query, the answer it produces, and the pages the answer was assembled from.
Your buyer asks
The answer they get
For read-only Postgres access, most people install Incumbent Server1. It exposes schema introspection and parameterised queries.2
Where the citations resolve
reddit.com38%
g2.com26%
news.ycombinator.com21%- The query
- One question from the first rung, with no brand name in it
- The answer
- Names one server, and gives the reader no second option
- The hosts
- Three third-party pages carried the citations behind it
- Your domain
- Present in the run, cited by none of them
Run it yourself
Five minutes settles whether any of this is worth paying for.
Five minutes, no tooling, and it settles whether there is anything here worth paying for. Run it before you talk to us, and run it before you talk to anybody else in this category.
- 01
Pick the rung
Take one category question from the first rung above. No brand name in it, yours or anybody else's.
- 02
Ask it five times
Same wording, same engine, five separate sessions. Repeats are the method rather than a detail, because a single read flips.
- 03
Change engine
Repeat the five on a second assistant. Answers assembled from different retrieval sets disagree, and the disagreement is information.
- 04
Count the mentions
Write down how many of the ten runs named you at all, and which names came back instead.
Named in all ten
Yours is the server the category is described with. The category question and the head to head already return it, so there is nothing here to buy. Keep your money.
Named in some
You are in the answer set and not reliably. This is the position the work is built for, because the gap is real and it is measurable.
Named in none
Discovery is happening without you in the room. A registry entry makes you findable, and being findable is the floor rather than the outcome.
one category question, same model, same day
Nothing was altered between calls. A single reading of where you stand is a coin flip wearing the clothes of a metric, which is why the method counts repeats instead.
A perfectly on-vertical category definer is a bad engagement for both sides. A slightly off-vertical challenger is a good one.
The method, given away
How to build the list without hiring anyone.
The list is the deliverable, and building one is not proprietary. This is the same sequence we run, written out so you can run it yourself.
26 of 1,240 survive. The 1,214 that do not are what a keyword export is, and running the month against them is the ordinary way this budget gets spent.
- 01
Disambiguate
Write each question the way a person types it, not the way a keyword tool reports it. One question per line, no operators, no truncation.
- 02
Strip the brand
Remove your own name from every line you can. A question carrying your name is one you already win, and it only fires for somebody who has heard of you somewhere else.
- 03
Ask for the budget
Keep a line only if somebody asking it could reasonably buy something within the week. That single test removes most of a keyword export.
- 04
Repeat five times
Ask each surviving question five times on the same engine and write down every answer. We ran twelve queries five times each and seven flipped outcome, so one read decides nothing.
- 05
Count, do not score
Record how many of the five runs named you rather than a single number. The count is what a control group can later be compared against; a score is not.
What counts
Most of a keyword export is not a money query.
Most of what a keyword export returns does not belong on this list. The cuts are what make the remaining twenty or thirty questions mean something.
yourcli.example alternatives
yourcli.example1 is the lighter of the two and covers the same core case.
Named, and you already win this
best mcp server for postgres
Three options come up most often: the incumbent1, a second name, and an open source project.2
yourcli.example does not appear
Same company, same day. The left panel is the one a branded report shows you, and the right panel is the one the budget is decided on.
Keep it if
- A category question with no brand name, where an answer returns something installable.
- A head to head that names another server rather than yours.
- A constraint question whose answer is a permission, an auth requirement or a command.
- A task question your tool genuinely resolves, asked by somebody mid-setup.
Cut it if
- Your own tool name. You already win it, and it only fires after somebody has heard of you somewhere else.
- A head term from a keyword tool. Volume without install intent produces a list that moves and sells nothing.
- Anything your README answers faster than an assistant does.
- A question with no install behind it, however often it is asked.
What the list becomes
A validated list is a baseline, not a report.
A finished list is a baseline rather than a report. Once the questions are validated, the set splits, gets written down, and becomes the thing a later claim is measured against.
- Validated
- 5 identical repeats before one query counts
- Split
- A treated arm and a held-out control arm
- Registered
- Both written down before any work starts
- Depth
- 40 queries by 40 samples, 9.9pp floor
- Readout
- Difference-in-differences at day 90
Stamped on the divide
The list is worth nothing until something is committed to against it. Two of these three are done before any work starts, and the third is the only one that can surprise anybody.
Citation sets churn, so a level reading taken twice tells you almost nothing. Ahrefs measured across 43,000 keywords that AI Overviews persist 2.15 days and 45.5 percent of citations change between consecutive observations, while the answer stays 95 percent semantically identical. A held-out control is what survives that.
Start here, free
We build the list for you: 12 queries, 5 repeats each, 3 engines.
Delivered in five working days, and walked through live rather than emailed as a PDF. You get your questions built and disambiguated, your failure mode named, the hosts cited on those questions ranked by citation depth, and a pre-registered baseline you can hold anyone to afterwards, including us.
The rest of the cluster
One play, run in one niche, all the way down.
One method, three ways in
Questions
The five we get asked about building the list.
Not covered here? The Gap Report costs nothing and answers most of the rest with your own data.
How many install-intent queries should we track?
Twenty to thirty across one cluster is the working set for a single integration surface, which is what the entry engagement covers. Sixty to ninety across three clusters is the depth at which the instrument reads reliably, because the minimum detectable lift at 40 queries by 40 samples is 9.9 percentage points.
We are already in the main registry. Why build a question list?
A registry entry makes you findable rather than cited. Across 901 citations we counted, 91.5 percent pointed off-site across 82 distinct hosts, so an answer about what to install is assembled from lists, threads and comparisons rather than from one index. The question list is what tells you which of those pages to go and reach.
Does an agent ask these questions the same way a developer does?
Close enough that one list serves both, and the difference matters at the constraint rung. A developer asks in prose and reads a page; an agent reads your tool name and description at selection time and needs them unambiguous against neighbouring tools. Same question, second reader, and the manifest is what the second reader gets.
The answers change every time we ask. Is this measurable at all?
The level is not measurable reliably. We ran twelve queries five times each on one model and seven flipped outcome. The difference between a treated arm and a matched control still measures cleanly, because unbiased noise cancels: across 20,000 random splits with no work applied, the null difference centred on zero.
What is in the free Gap Report?
Twelve money queries, five repeats each, across three engines, delivered in five working days. It names which of the nine failure modes you are in, ranks the hosts cited on your queries by citation depth, and sets a pre-registered baseline. It is walked through on a call rather than emailed as a PDF.
Free gap report
When the model answers,
be the one it names
Tell us your category and the questions your buyers ask. We run them against live AI answers and walk you through what came back. If you are already winning, we will tell you that too.
12 queries · 5 repeats each · 3 engines · 5 working days
Free · Walked through live · Five working days
Queries we run
Cited instead of you
reddit.com38%
g2.com26%
news.ycombinator.com21%91.5% of citations point off-site