Google Search Console integration for Model Context Protocol (MCP)
recomention is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Check whether AI engines recommend a product: public AI rankings and recomention reports.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user recomention-mcp '--' npx -y @recomention/mcp
# 2 — ask your agent for something these tools do
# recomention_rankings_list, recomention_rankings_get, recomention_suggest_prompts and 5 more
Remote: OAuth sign-in · Package: optional API key.
recomention costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user recomention-mcp '--' npx -y @recomention/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://mcp.recomention.com/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http recomention-mcp https://mcp.recomention.com/mcpNothing is required, but it can take RECOMENTION_API_KEY (API key from your recomention account (Developers). Needed for reports; public rankings and suggested questions work without it.), RECOMENTION_BASE_URL (API origin. Must be https:// (http:// only for localhost).), OPENAI_API_KEY (Optional. Your own OpenAI key, used only for reports started with funding "byok" (needs an active Agent plan).), ANTHROPIC_API_KEY (Optional. Your own Anthropic key, used only for reports started with funding "byok" (needs an active Agent plan).), PERPLEXITY_API_KEY (Optional. Your own Perplexity key, used only for reports started with funding "byok" (needs an active Agent plan).), GEMINI_API_KEY (Optional. Your own Gemini key, used only for reports started with funding "byok" (needs an active Agent plan).), XAI_API_KEY (Optional. Your own xAI (Grok) key, used only for reports started with funding "byok" (needs an active Agent plan).), DATAFORSEO_API_KEY (Optional. DataForSEO login:password for Google AI Overview, used only for reports started with funding "byok" (needs an active Agent plan).) if you want to set them. Its publisher says some of its tools need one of them, and the rest work without.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List recomention's public AI rankings: for each category, which products the AI engines name when asked its buyer questions, month by month. Free.
No parameter schema on file.
One public AI ranking by slug: every product named, how many answers named it (as n of m), and the verbatim answers. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The slug from a previous call. |
Suggest buyer-intent questions to check for a product, from fixed templates. No model call and no cost. The product's own name never appears in a question. Show them to the user to edit before starting a report.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The product's domain, e.g. example.com |
| category | string | yes | What buyers search for, e.g. meeting scheduling |
| description | string | no | One line on what the product does |
| count | integer | no | — |
Start a recomention report: the questions are asked of every engine on the plan several times each, with live web search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | — |
| description | string | yes | — |
| category | string | yes | — |
| brand | string | no | Defaults to the name in the domain |
| plan | string | no | — |
| prompts | array | no | Questions to ask; the rest are written for you. None may name the product. |
| engines | array | no | A subset of the plan's engines |
| funding | string | yes | — |
| idempotencyKey | string | no | Reuse to make a retried start land on the same report |
Where a report is: PENDING, RUNNING, COMPLETE or FAILED, with answers stored so far. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The slug from a previous call. |
A report as JSON: the overall score, each engine's runs mentioned of runs total, competitors named instead, cited sources, the fix list and every question with every answer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The slug from a previous call. |
Markdown files built from a finished report, for planning distribution: product.md, competitors.md, ai-visibility.md, where-to-get-mentioned.md (third-party pages, subreddits and videos the engines cite for a rival and not for this product) and channel-plan.md (channels ranked by those citations,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The slug from a previous call. |
The reports in the account that owns the API key, newest first. Free.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install recomention or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (8 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| recomention_rankings_list | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| recomention_rankings_get | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| recomention_suggest_prompts | no tags | |
| recomention_report_start | untrusted-inputexternal-sink | untrusted-input: keyword "web_search"; external-sink: declares readOnlyHint: false, openWorldHint: true |
| recomention_report_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| recomention_report_get | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| recomention_distribution_kit | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| recomention_reports_list | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.3. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish recomention can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.