Sellular

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

Takes no parameters.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.