Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Sellular 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.
20
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Track where your product is listed, score its AI search visibility, and audit a domain's SEO.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http sellular-mcp https://sellular.online/api/mcp/mcp
# 2 — ask your agent for something these tools do
# get_visibility_score, scan_domain, bulk_scan and 17 more
Sellular costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SEAll 1 server
sellular1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http sellular-mcp https://sellular.online/api/mcp/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
20 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.
Get the Sellular visibility score (0-100, graded A-F) for a public website by domain or URL. Measures SEO and AI-discoverability signals (meta tags, sitemap, llms.txt, structured data, etc.). Use when asked how discoverable or SEO-ready a site is.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | A domain (example.com) or full URL to score. |
One-call visibility audit for a public website: Sellular visibility score (0-100, A-F), whether llms.txt exists (root or .well-known), tracked directories with no known listing for the domain (submission opportunities, not verified absences), and a better-scoring same-category competitor when one is known. Read-only; results cached 24h per domain. Use when asked to audit or size up a site's overal
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | A domain (example.com) or full URL to scan. |
Scan up to 10 public domains in one call: for each domain, the Sellular visibility score (0-100, A-F) and whether llms.txt exists, plus directory opportunities. Returns partial results with a per-domain error instead of failing the whole batch. Debits the rate limiter once per domain (results cache 24h per domain). Use for outreach research across a prospect list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domains | array | yes | 1-10 domains or full URLs to scan. |
Run a read-only SEO / AI-discoverability audit on a public URL. Returns the passing and failing checks, with failures sorted by impact (biggest score wins first) so you can recommend what to fix. Use after get_visibility_score to explain a low score.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | A domain or full URL to audit. |
Score 2-5 public websites and rank them by visibility score, side by side, each with grade and its top strengths/weaknesses. Use to benchmark a site against competitors and explain who wins and why.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urls | array | yes | 2-5 domains or full URLs to compare. |
Generate a ready-to-use llms.txt file body (the AI-discoverability manifest) for a public website, built from its fetched metadata: site name, description and key pages. Returns the text to serve at the site root as /llms.txt. If you are an agent working inside the site's source repository, write the file there yourself (public/llms.txt in Next.js, the web root otherwise) and review the Key Pages
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | A domain (example.com) or full URL to generate llms.txt for. |
Turn a public site's failing SEO / AI-discoverability checks into ready-to-apply fixes: complete file bodies (robots.txt, sitemap.xml, llms.txt, security.txt, manifest.json) and HTML head snippets (meta description, Open Graph, Twitter card, canonical, JSON-LD), each with where it belongs in the source tree (Next.js locations named). Built for coding agents working inside the site's own repository
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | A domain (example.com) or full URL to build fixes for. |
List curated directories a product can submit to, sorted by domain authority. Optionally filter by product category (e.g. 'saas', 'ai', 'tools', 'dev'). Reference data only, read-only: this does NOT submit anything. Use to suggest where a product should get listed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Product category to filter by, e.g. 'saas', 'ai', 'tools'. |
| limit | integer | no | — |
List public community listings on Sellular, with optional category or search filter. Read-only. Use to browse products already listed in the community directory.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | — |
| search | string | no | Match against listing name or tagline. |
| limit | integer | no | — |
List the sites/products tracked on the connected Sellular account (products and listings), including type, category, status and whether the Sellular badge is verified. Read-only. Account-scoped: requires the MCP_API_KEY bearer token and MCP_ACCOUNT_EMAIL to be configured.
No parameter schema on file.
Get visitor analytics for one of the connected account's products: views and unique visitors for the last 7 days, 30 days and all time, plus published/draft review counts. Set breakdown to also get WHERE the traffic came from: referring hosts, channels (search, social, referral, direct), campaigns, countries, devices, and a per-day visitor trend. Counters alone cannot tell a spike caused by one
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | Product name or domain to look up (substring match). Optional when the account has one product. |
| breakdown | boolean | no | Include traffic sources, channels, campaigns, countries, devices and the daily trend. Off by default because it runs a second, heavier aggregation. |
| period | string | no | Window for the breakdown. Ignored unless breakdown is true. |
Check what is missing before one of the connected account's products can be submitted to directories, WITHOUT generating a full kit: per directory, every required field is reported as present, derived (with its source, e.g. site favicon or og:image), or missing (with the fix), plus one deduped list of blockers and the recorded done/pending/remaining progress. Read-only. Account-scoped: requires th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | Product id, name or domain to look up (substring match). Optional when the account has one product. |
| directory_name | string | no | Filter to one directory by name (substring match), e.g. 'G2'. |
| limit | integer | no | Max directories to check, sorted by domain authority. |
Build ready-to-paste directory submission copy for one of the connected account's products: name, tagline, length-appropriate descriptions, category and pricing mapped to each directory's own field names and char limits, plus per-directory prep requirements (screenshots, video), resolved assets with provenance, blockers (e.g. missing logo) and recorded done/pending/remaining progress. fields/`co
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | Product id, name or domain to look up (substring match). Optional when the account has one product. |
| directory_name | string | no | Filter to one directory by name (substring match), e.g. 'Product Hunt'. |
| limit | integer | no | Max directories to return, sorted by domain authority. |
| remaining_only | boolean | no | Return only directories with no recorded submission yet, i.e. the outstanding to-do list. Applied before limit, so limit: 1 with this set yields the single highest-DA directory still to do. Use it |
| signed_out | array | no | Directory names the session sweep found signed out, dropped from the result and echoed back in skippedSignedOut. Probe first with browserControl.sessionProbe, then pass what failed: the kit return |
| automation | string | no | Filter by how the form can be driven, measured by loading it in a real browser: 'open' fills with no account, 'login' needs the owner signed in first, 'walled' serves a bot challenge and cannot be aut |
Get the ready-to-paste Sellular badge embed for one of the connected account's products, as HTML (also valid JSX as-is) and as Markdown. One embed per product: the image auto-upgrades to whichever tier the product currently holds (listed, editor's pick, top rated, or the paid featured slot while it runs), so it is pasted once and never replaced; never pin a width on it. The badge's link resolves p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | Product name or domain to look up (substring match). Optional when the account has one active product. |
Start tracking one of your products on the connected Sellular account, so the account-scoped tools can work on it: check_submission_readiness, generate_submission_kit, get_product_analytics and record_submission all refuse to run for a product that is not tracked. Idempotent by website: calling it again for a site already tracked UPDATES that entry (name, category, tagline, description) instead of
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Product name as it should appear, e.g. "QuickPeek". |
| url | string | yes | The product website, e.g. "quickpeek.co". This is the identity: the same site twice updates one entry rather than adding two. |
| type | string | no | "saas" for a subscription web app, "product" for a one-off or downloadable. |
| category | string | no | Category used for directory matching and community filters. |
| tagline | string | no | One line, under ~60 chars. Used as the short field on directory forms. |
| description | string | no | A sentence or two on what it does and who it is for. Directory submission copy is built from this, so a thin one produces thin listings. |
Put one of your tracked products in the Sellular community directory, or refresh the card it already has from the product's current name, tagline, description and category. The card is a public page at sellular.online/community/<domain> where people can read about the product and leave reviews, and it is what the Sellular badge links to. Idempotent per domain: calling it again updates that one car
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | Product id, name or domain (substring match). Optional when the account tracks one product. |
Record that one of your tracked products has been submitted to a directory, so check_submission_readiness and generate_submission_kit stop listing it as remaining and you never re-submit the same place twice. Status is 'submitted' (done or live), 'pending' (waiting on their review) or 'rejected' (turned down). Optionally store the live listing URL and a note. Idempotent per product+directory: reco
| Parameter | Type | Required | Notes |
|---|---|---|---|
| directory_name | string | yes | Directory from the Sellular catalog, e.g. "Product Hunt". A unique partial name works ("hunt"); check names with list_directory_listings. |
| product | string | no | Product id, name or domain (substring match). Optional when the account tracks one product. |
| status | string | no | 'submitted' = done or live, 'pending' = awaiting their review, 'rejected' = turned down. |
| listing_url | string | no | The live listing URL on that directory, once there is one. |
| note | string | no | Anything worth remembering, e.g. why it was rejected or when to resubmit. |
Attach real product screenshots you already have on disk to one of your tracked products, so check_submission_readiness and generate_submission_kit stop reporting screenshots as missing. This is the one asset that blocks the five highest-authority directories in the catalogue (G2, Product Hunt, Capterra, SourceForge and TrustRadius all require a gallery), so filling it once unblocks all five for t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| files | array | yes | Local paths of the screenshots you hold, best first (the order becomes the gallery order), e.g. ["/home/you/shots/01-home.png"]. Only pass paths you have verified exist: a ticket cannot check them, so |
| product | string | no | Product id, name or domain (substring match). Optional when the account tracks one product. |
Generate a competitor review article for one of your apps, named by its website (product_url, e.g. "sparkmobile.dev") or its id. Asks you to confirm the website and optionally name its rivals, then runs live competitor research (Tavily), writes the article and (optionally) builds a head-to-head comparison table. Returns a preview link and the name of the editor it is waiting on. The article is NEV
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_comparison | boolean | no | Include the head-to-head comparison table (research runs either way). |
| product_id | string | no | Which product to review, by id. Ignored with a product API key. Prefer product_url, which is how people name their own app. |
| product_url | string | no | Which product to review, by website, e.g. "sparkmobile.dev". Matched by domain against the products on the account, ignoring www and the scheme. Ignored with a product API key. |
| brief_only | boolean | no | Research only: return the competitors, the verified feature matrix and the full writing brief, and write nothing. Nothing is saved, no quota is spent and no editor is involved. Follow it with a second |
| rivals | string | no | Competitors to compare against, comma separated, instead of whatever a live search turns up. You know your own market better than a listicle does. |
| fills | object | no | Answers for rows the research could not confirm from your site, as {"Feature name": "value"}, e.g. {"MCP tools": "Yes"}. Authoritative: you know whether you ship the thing, and a dash next to three ti |
| research | string | no | The extracted research JSON, when a previous call handed you the extraction prompt instead of running it. This server never calls an AI model on your behalf: you are the model. Pass back exactly the J |
| draft | object | no | Your article, written from a brief_only call. Supplying it skips the built-in writer: the comparison table, the strengths and weaknesses cards, the quality score and the editor hand-off all run exactl |
| hold_as_draft | boolean | no | Save the article as a dashboard draft and stop: no editor is picked, nobody is notified. The owner reviews it at the dashboard (Reviews view) and submits it from there, where the same publish benchmar |
List the review articles across every product you own, newest first, with their editorial status (draft, pending_review, published, rejected), editor notes and public URL once live. Use to check what happened to a generated review. Authenticate with either your product API key (Dashboard -> Analytics -> API key) or the admin key; both list the whole account, since a review belongs to the owner rat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by editorial status. |
| limit | integer | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Sellular or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Sellular can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.