From a first check to a tracked trend, to querying it all from Claude. If you want the method behind the numbers rather than how to drive the tool, that is How it works.
A check asks an AI assistant five buyer questions about your category and counts how many of the answers name you. You need a free account first — every check spends real API budget, so there is no anonymous path.
You get a score out of five, the sentence that named you, and — when nothing named you — which brands got named instead. Every result has a share link at /r/<id> you can send to someone.
The category is the whole experiment. A category so broad that no answer could name any specific business will score zero for everyone, and that is a fact about the question rather than about you. Ask what a buyer would type.
A one-off check is a snapshot. Tracking turns it into a trend: a brand and a category whose five questions are written once, at creation, and then re-asked verbatim on every later run.
That freezing is the point. Most tools regenerate their prompts each run, which means part of every movement in their charts is the prompt changing rather than your visibility. Here, a line that moves means one thing.
You do not have to write any of it yourself. Start from your domain and Claude drafts the brand, the category, the rivals and the five questions; you then correct them on a review screen, and nothing is stored until you press the button. You can also name the competitors you already know — knowing them changes the questions, because “best alternatives to X” is a question buyers really type and it can only be written by someone who knows X is your rival.
The draft is a draft, and the screen says so. Claude does not browse: it answers from what it already knows, so for a company it has never heard of it says so plainly and leaves the category to you rather than inventing one. A made-up category would be a claim about your business that nobody checked, and it would be frozen into five questions for as long as the keyword exists. If you already know your category, the form on the Keywords screen skips the draft entirely.
Tracked keywords run weekly on our key. A keyword can run daily only when your account holds its own API key for every model that keyword asks — because a daily run spends your key, not ours. Remove the key later and the keyword reverts to weekly rather than quietly moving seven runs a week onto our bill.
Three figures, and none of them is redundant:
The one rule that makes everything else readable: a dash is not a zero. Where a figure could not be measured you get an em dash and a sentence, never a flattering zero. “Nobody named you” and “nothing has run yet” are different findings, and this product never prints one as the other. The same rule holds in the API and in the MCP tools, where the value is null rather than 0.
Your account is one page with a rail down the left. Each item loads only its own data, so a screen is a smaller page rather than a longer one.
Filters for brand and topic, and the 4W/8W/12W window, all live in the URL — so any view you are looking at can be bookmarked, reloaded or sent to someone. There is also a CSV export of one row per keyword per run, filtered exactly as the screen is.
Only a model that searches the web before answering has sources to report. Today that is Perplexity, and only on a key you have saved. Every other model answers from what it already knows, fetches nothing, and therefore has no sources — so the screen shows none rather than guessing where the answer came from. It names which of three situations you are in: nothing has run, nothing that ran reports sources, or something that does report them returned none.
Under Settings you can save a key for ChatGPT, Gemini, DeepSeek, Llama 3.3 (Groq) or Perplexity. Saving one lets you re-ask a keyword’s frozen questions on that model whenever you like, set that keyword to daily, and — for Perplexity — fill in the Sources screen.
Keys are encrypted before they are written down, with a secret that is not in the database. Be clear about the limit of that: it protects you against our database leaking, not against us. A key pasted into a one-off check on the home page is used for that request and never written down at all.
Gemini and Groq both have genuinely free API tiers, so trying a second model does not have to cost anything.
Keywords, runs and saved keys belong to a workspace rather than to you personally. On your own that distinction never surfaces — you get one workspace and it behaves exactly as an account did. It starts to matter when you invite someone.
From Team you can create additional workspaces and invite people to them. There are two roles: an owner, who can invite and remove people, and a member, who can see and use everything the workspace tracks. An invite is a link, and it is a credential — anyone holding it can join, so send it the way you would send a password, and revoke it from the same screen if it goes astray.
The query allowance is per owner, counted across every workspace you own. Making a second workspace does not give you a second allowance. But a workspace you were invited to is billed to whoever owns it, so joining a busy team never eats into your own — and if you leave, your allowance is exactly what it was before you joined.
Billing shows the plan you are on, when it renews, and every payment ever charged to your account — date, what it was for, amount, status, and a receipt you can open or download.
That list is read live from Stripe rather than from a copy we keep. A refund, a retried payment or a failed card shows here as soon as it happens, because there is no snapshot of ours to go stale. The trade is that if Stripe is unreachable the page says so rather than showing an empty table — “no payments” and “we could not ask” are different answers and you should not have to guess which one you are looking at.
Changing card, cancelling or switching plan happens on Stripe’s own billing portal, reached from the same page. Cancelling there does not cut you off on the spot: you keep the plan until the period you already paid for runs out, and this page tells you the date that happens.
Upgrading and downgrading between paid plans can also be done in one click from Settings. Stripe prorates both directions — an upgrade is charged only for the rest of the current period, and a switch down credits what you have not used.
Security holds two things. You can change your password — passwords are stored with argon2id, and an older one is re-hashed to it the next time you log in, so you do not have to do anything to benefit from that.
You can also turn on two-factor authentication with any TOTP app (1Password, Authy, Google Authenticator). Scan the QR code, confirm one code to prove it works, and you are enrolled — the confirmation step exists so a mis-scanned code locks you out of the setup screen rather than out of your account.
Enrolling gives you recovery codes. Save them somewhere that is not the phone running the authenticator, because that is the exact thing they exist to survive. Each one works once. You can regenerate the set from the same screen, which invalidates the old ones.
An MCP token is not covered by two-factor. It is a bearer credential and it authenticates on its own — that is what makes it usable from a client that cannot show you a prompt. Turning 2FA on protects the dashboard login; it does not retroactively protect a token you already minted. If you want a token to stop working, revoke it.
Connecting an app is covered by two-factor, because approving one goes through the ordinary login. The approve screen has no password field at all: if you are signed out it hands you to the normal form, second factor included, and only asks you to approve once you are back.
Mentioned runs a Model Context Protocol server, so you can ask your own data questions in plain language from an AI client instead of reading screens.
claude mcp add --transport http mentioned https://mentioned.at/mcp --header "Authorization: Bearer mnt_YOUR_TOKEN"Then ask things like:
How did our visibility move over the last eight weeks, and which keyword moved most?
Which frozen prompt are we losing worst, and what do the actual answers say?
Which assistant has never heard of us?
Ten tools are available — overview, keywords, trend, prompts, competitors, models, sources, sentiment, answers and actions. They read through the same code the dashboard renders from, so an answer in Claude cannot disagree with the screen it came from.
Every tool is read-only. None of them runs a check, changes what you track, saves a key or spends API budget. That is deliberate: the caller is a model, and a tool that spends money is the wrong thing to put behind a retry loop.
A token is a password to your data. It does not expire; revoke it from the same card when you are done with it. Revoking a token does not sign you out of the dashboard, and logging out does not break a connector.
The custom connector dialog in claude.ai and Claude Desktop does not take a pasted token at all — it signs in with OAuth instead. That now works here, and it is the easier path of the two: there is no token to copy and none to lose.
https://mentioned.at/mcp as the URL. Leave the optional client ID and secret blank — Claude registers itself.The connection stays signed in on its own and renews itself in the background. It is read-only, exactly like a token: the same ten tools, and none of them can run a check or change what you track. It has no access to your password or your stored API keys.
Connected apps are listed under Connect Claude in Settings, with a Disconnect button. Disconnecting stops that app immediately; it can ask for your approval again whenever you like.
If you would rather use the token you just made than the connector dialog — on a machine where you do not want to sign in, say — there is a way, through a small local bridge: mcp-remote, which Claude Desktop launches as an ordinary local server and which forwards to us over HTTPS with your header attached. The connector above is simpler and needs no Node; this is here for the case where it is not what you want.
Open Settings → Developer → Edit Config (that button creates the file if it does not exist; on a Mac it is ~/Library/Application Support/Claude/claude_desktop_config.json) and add:
{
"mcpServers": {
"mentioned": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://mentioned.at/mcp",
"--header", "Authorization:${AUTH_HEADER}",
"--transport", "http-only"
],
"env": { "AUTH_HEADER": "Bearer mnt_YOUR_TOKEN" }
}
}
}Then quit Claude Desktop completely and reopen it — closing the window is not enough; it reads this file only at launch.
Three details in that config are deliberate, and each one is a bug you would otherwise hit:
Authorization:${AUTH_HEADER} has no space after the colon, with the word Bearer living in env instead. Several clients mangle spaces inside args, and the symptom is a 401 that looks like a bad token rather than a bad config.--transport http-only because this server speaks Streamable HTTP and opens no SSE stream. Without it the bridge probes for one first and answers its own 405.-y so npx never stops to ask about installing the bridge — a launched-by-GUI process has nobody to answer the prompt, and it simply hangs.It needs Node installed, and your token ends up in that config file in plain text — which is how every MCP client stores credentials, but worth knowing before you put it on a shared machine. Revoke it from Settings if that machine stops being yours.
claude.ai and Claude Desktop through the connector dialog, with no token at all. Claude Code directly, with the command above. Claude Desktop with a token through mcp-remote, if you prefer that. And any other MCP client that can either send an Authorization header or speak OAuth 2.1 — the server publishes the standard discovery documents at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server, registers clients dynamically, and requires PKCE.
The two ways in are independent. A token keeps working if you disconnect an app, and disconnecting an app does not touch your tokens.
Starter is $39/month, Pro is $129/month and Agency is $399/month, billed monthly by card and cancellable at any time. Free stays free, with no card required.
https://mentioned.at/mcp with no trailing slash. If the approve page loads but sends you back with an error, the message on that page says which part of the request Claude sent was wrong.Checks, their answers, and your tracked keywords. IP addresses are stored hashed, never in the clear. API keys are encrypted; MCP tokens are stored only as a hash. The full detail is on the privacy page.
Three things, all of them triggered by something you did, and nothing else:
We do not email results, weekly digests, score alerts or marketing. If you saved your address next to a check result, that is what it is for — a way to reach you if those ever ship — and nothing goes out today.
If a reset or verification mail has not arrived, check your spam folder. It comes from no-reply@send.mentioned.at. Links are single-use and expire, so if one has gone stale just request another.