Sellular

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Track where your product is listed, score its AI search visibility, and audit a domain's SEO.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Sellular": {
      "url": "https://sellular.online/api/mcp/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (20)

• get_visibility_score

  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.

  Parameters:

  • url (required) — string — A domain (example.com) or full URL to score.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• scan_domain

  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 overall discoverability in one shot.

  Parameters:

  • domain (required) — string — A domain (example.com) or full URL to scan.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• bulk_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.

  Parameters:

  • domains (required) — array — 1-10 domains or full URLs to scan.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• seo_audit_summary

  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.

  Parameters:

  • url (required) — string — A domain or full URL to audit.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• compare_visibility

  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.

  Parameters:

  • urls (required) — array — 2-5 domains or full URLs to compare.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• generate_llms_txt

  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 list before shipping. Use when a site fails the llms.txt check and the user wants one made.

  Parameters:

  • url (required) — string — A domain (example.com) or full URL to generate llms.txt for.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• generate_seo_fixes

  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: write the files, insert the snippets, replace the TODOs, deploy, then re-run seo_audit_summary to verify. Read-only on Sellular's side; the tool itself writes nothing. Run seo_audit_summary first when you only want the diagnosis.

  Parameters:

  • url (required) — string — A domain (example.com) or full URL to build fixes for.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_directory_listings

  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.

  Parameters:

  • limit — integer
  • category — string — Product category to filter by, e.g. 'saas', 'ai', 'tools'.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_public_listings

  List public community listings on Sellular, with optional category or search filter. Read-only. Use to browse products already listed in the community directory.

  Parameters:

  • limit — integer
  • search — string — Match against listing name or tagline.
  • category — string

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_tracked_sites

  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.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_product_analytics

  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 referrer from steady organic growth, so ask for the breakdown whenever the question is why traffic moved or which source is working. Read-only. Account-scoped: requires the MCP_API_KEY bearer token.

  Parameters:

  • period — string — Window for the breakdown. Ignored unless `breakdown` is true.
  • product — string — Product name or domain to look up (substring match). Optional when the account has one product.
  • breakdown — boolean — Include traffic sources, channels, campaigns, countries, devices and the daily trend. Off by default because it runs a second, heavier aggregation.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• check_submission_readiness

  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 the MCP_API_KEY bearer token. Use to answer 'what is missing' or 'where should submissions start' before doing any submission work.

  Parameters:

  • limit — integer — Max directories to check, sorted by domain authority.
  • product — string — Product id, name or domain to look up (substring match). Optional when the account has one product.
  • directory_name — string — Filter to one directory by name (substring match), e.g. 'G2'.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• generate_submission_kit

  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`/`copyText` contain ONLY pasteable values; prep instructions live in `requirements`. Read-only formatter: it does NOT submit anything anywhere. Account-scoped: requires the MCP_API_KEY bearer token. Use when preparing directory submissions without opening the dashboard.

  Parameters:

  • limit — integer — Max directories to return, sorted by domain authority.
  • product — string — Product id, name or domain to look up (substring match). Optional when the account has one product.
  • automation — string — 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 automated at all. Pass 'open' to get only the directories an agent can fill right now. Every entry also carries `automation` and a `howToFill` instruction, so the walled ones can be handed to the Sellular Chrome extension instead of being retried.
  • signed_out — array — 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 returns only what can be worked on now, so a run proceeds on the valid sessions instead of stalling on the locked ones.
  • directory_name — string — Filter to one directory by name (substring match), e.g. 'Product Hunt'.
  • remaining_only — boolean — 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 to walk submissions one at a time without re-reading the ones already done.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_listing_badge

  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 per click too: the product's featured article while a paid feature window runs, its page in the Sellular directory otherwise, where visitors read and leave reviews. The tool itself edits nothing: if you are an agent working inside the product's source repository, add the snippet to the landing page header or footer yourself, next to any other trust badges, keeping the link and alt text intact; otherwise hand it to the developer. Account-scoped: requires the MCP_API_KEY bearer token.

  Parameters:

  • product — string — Product name or domain to look up (substring match). Optional when the account has one active product.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• track_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 creating a duplicate, so it is safe to retry. Never deletes anything. Account-scoped: requires the MCP_API_KEY bearer token, and asks you to confirm before writing. Use when a product is missing from list_tracked_sites.

  Parameters:

  • name (required) — string — Product name as it should appear, e.g. "QuickPeek".
  • url (required) — string — The product website, e.g. "quickpeek.co". This is the identity: the same site twice updates one entry rather than adding two.
  • type — string — "saas" for a subscription web app, "product" for a one-off or downloadable.
  • tagline — string — One line, under ~60 chars. Used as the short field on directory forms.
  • category — string — Category used for directory matching and community filters.
  • description — string — 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.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_product

  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 card instead of adding a rival to it, and nothing is ever deleted. Only products the account already tracks can be listed, because the directory's claim is that each card belongs to whoever made the thing: run track_product first for anything missing. Account-scoped: requires the MCP_API_KEY bearer token, and asks you to confirm before writing.

  Parameters:

  • product — string — Product id, name or domain (substring match). Optional when the account tracks one product.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• record_submission

  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: recording the same directory again updates that record rather than adding another, and nothing is ever deleted. This does NOT submit anything anywhere; it only records what you did. Account-scoped: requires the MCP_API_KEY bearer token, and asks you to confirm before writing.

  Parameters:

  • directory_name (required) — string — Directory from the Sellular catalog, e.g. "Product Hunt". A unique partial name works ("hunt"); check names with list_directory_listings.
  • note — string — Anything worth remembering, e.g. why it was rejected or when to resubmit.
  • status — string — 'submitted' = done or live, 'pending' = awaiting their review, 'rejected' = turned down.
  • product — string — Product id, name or domain (substring match). Optional when the account tracks one product.
  • listing_url — string — The live listing URL on that directory, once there is one.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• attach_product_screenshots

  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 that product. IMPORTANT: this tool uploads nothing by itself and cannot. The Sellular server is remote, so it cannot read your machine; it authorises YOU to send the bytes and returns the exact curl command per file, valid for ten minutes and for this product only. It never fetches, generates, resizes or substitutes an image: only a file a human already has can enter the gallery. Directories want 3-5 images, PNG or JPG, at least 1280x720. Re-sending the same file is safe: it corrects that image rather than adding a duplicate. Nothing is ever deleted. Account-scoped: requires the MCP_API_KEY bearer token, and asks you to confirm before authorising.

  Parameters:

  • files (required) — array — 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 a wrong path simply fails at the command.
  • product — string — Product id, name or domain (substring match). Optional when the account tracks one product.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• generate_review

  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 NEVER published by this tool: it is submitted to a Sellular editor for approval (the editor is emailed) and only goes live at /reviews/[slug] once that editor approves it. Requires a paid plan (starter+) and counts against the monthly review generation quota. Authenticate with either your product API key (Dashboard -> Analytics -> API key), which names the product on its own, or the admin key plus product_id. TO WRITE THE ARTICLE YOURSELF: call once with brief_only=true to get the researched feature matrix and the full writing brief, then call again passing your article as `draft`. That skips the built-in writer entirely and is the better article, because you are already holding the comparison. The editor approval step is identical either way. TO DRAFT WITHOUT SUBMITTING: add hold_as_draft=true and the article is saved as a dashboard draft instead, with no editor involved; the owner reads it at the dashboard and submits it from there when happy.

  Parameters:

  • draft — object — 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 exactly as they otherwise would. Prose fields together should run 320 to 480 words.
  • fills — object — 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 ticks reads as a missing feature rather than a missing fact. Use the row names exactly as they come back from brief_only.
  • rivals — string — Competitors to compare against, comma separated, instead of whatever a live search turns up. You know your own market better than a listicle does.
  • research — string — 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 JSON object the prompt asked for.
  • brief_only — boolean — 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 call passing `draft`.
  • product_id — string — 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 — 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.
  • hold_as_draft — boolean — 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 benchmark applies. Still spends the generation (one review per app), so use it when a human should read the article before any editor does.
  • include_comparison — boolean — Include the head-to-head comparison table (research runs either way).

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_my_reviews

  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 rather than to one product.

  Parameters:

  • limit — integer
  • status — string — Filter by editorial status.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.