# Sellular (remote · sellular.online)

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

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `sellular.online`: 71/100 (this document), [markdown](https://verifymcp.io/servers/online-sellular-sellular/api-mcp-mcp.md), [page](https://verifymcp.io/servers/online-sellular-sellular/api-mcp-mcp)

## Channel facts

- Endpoint: `https://sellular.online/api/mcp/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4026 tokens (~201/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Sellular MCP server?

Sellular is a hosted endpoint at https://sellular.online/api/mcp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http online-sellular-sellular 'https://sellular.online/api/mcp/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "online-sellular-sellular": {
      "url": "https://sellular.online/api/mcp/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "online-sellular-sellular": {
      "type": "http",
      "url": "https://sellular.online/api/mcp/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.online-sellular-sellular]
url = "https://sellular.online/api/mcp/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "online-sellular-sellular": {
      "type": "remote",
      "url": "https://sellular.online/api/mcp/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add online-sellular-sellular --url 'https://sellular.online/api/mcp/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  online-sellular-sellular:
    url: "https://sellular.online/api/mcp/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "online-sellular-sellular": {
      "Transport": "http",
      "Url": "https://sellular.online/api/mcp/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add online-sellular-sellular -t streamable-http -u 'https://sellular.online/api/mcp/mcp'
```

### Other

```json
{
  "mcpServers": {
    "online-sellular-sellular": {
      "type": "http",
      "url": "https://sellular.online/api/mcp/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 71, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 70, +1)

- [functional] New tool “attach_product_screenshots”

### 2026-09-25 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 67, 0)

- [functional] New tool “list_product”

### 2026-09-19 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (20)

### `get_visibility_score` (~87 tokens)

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.

Input parameters:

- `url` (string, required): A domain (example.com) or full URL to score.

### `scan_domain` (~118 tokens)

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.

Input parameters:

- `domain` (string, required): A domain (example.com) or full URL to scan.

### `bulk_scan` (~105 tokens)

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.

Input parameters:

- `domains` (array, required): 1-10 domains or full URLs to scan.

### `seo_audit_summary` (~78 tokens)

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.

Input parameters:

- `url` (string, required): A domain or full URL to audit.

### `compare_visibility` (~69 tokens)

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.

Input parameters:

- `urls` (array, required): 2-5 domains or full URLs to compare.

### `generate_llms_txt` (~142 tokens)

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.

Input parameters:

- `url` (string, required): A domain (example.com) or full URL to generate llms.txt for.

### `generate_seo_fixes` (~168 tokens)

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.

Input parameters:

- `url` (string, required): A domain (example.com) or full URL to build fixes for.

### `list_directory_listings` (~102 tokens)

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.

Input parameters:

- `category` (string): Product category to filter by, e.g. 'saas', 'ai', 'tools'.
- `limit` (integer)

### `list_public_listings` (~66 tokens)

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

Input parameters:

- `category` (string)
- `limit` (integer)
- `search` (string): Match against listing name or tagline.

### `list_tracked_sites` (~63 tokens)

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.

### `get_product_analytics` (~217 tokens)

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.

Input parameters:

- `breakdown` (boolean): Include traffic sources, channels, campaigns, countries, devices and the daily trend. Off by default because it runs a second, heavier aggregation.
- `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.

### `check_submission_readiness` (~188 tokens)

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.

Input parameters:

- `directory_name` (string): Filter to one directory by name (substring match), e.g. 'G2'.
- `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.

### `generate_submission_kit` (~454 tokens)

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.

Input parameters:

- `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 au…
- `directory_name` (string): Filter to one directory by name (substring match), e.g. 'Product Hunt'.
- `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.
- `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 i…
- `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 retur…

### `get_listing_badge` (~222 tokens)

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.

Input parameters:

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

### `track_product` (~292 tokens)

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.

Input parameters:

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

### `list_product` (~182 tokens)

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.

Input parameters:

- `product` (string): Product id, name or domain (substring match). Optional when the account tracks one product.

### `record_submission` (~281 tokens)

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.

Input parameters:

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

### `attach_product_screenshots` (~324 tokens)

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.

Input parameters:

- `files` (array, required): 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, s…
- `product` (string): Product id, name or domain (substring match). Optional when the account tracks one product.

### `generate_review` (~757 tokens)

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.

Input parameters:

- `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 secon…
- `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 exact…
- `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 t…
- `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 benchma…
- `include_comparison` (boolean): Include the head-to-head comparison table (research runs either way).
- `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.
- `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…
- `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.

### `list_my_reviews` (~111 tokens)

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.

Input parameters:

- `limit` (integer)
- `status` (string): Filter by editorial status.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/online-sellular-sellular/api-mcp-mcp#diagnostics

## Score history

- 2026-09-28: 71
- 2026-09-27: 70
- 2026-09-26: 70
- 2026-09-25: 69
- 2026-09-24: 69
- 2026-09-23: 68
- 2026-09-22: 68
- 2026-09-21: 68
- 2026-09-20: 67
- 2026-09-19: 67
- 2026-09-18: 66
- 2026-09-17: 66
- 2026-09-16: 65

## Common questions

### What is the Sellular MCP server?

Sellular is an MCP server listed in the public MCP registry as online.sellular/sellular. Track where your product is listed, score its AI search visibility, and audit a domain's SEO. This page covers its hosted endpoint (https://sellular.online/api/mcp/mcp).

### Is the Sellular MCP server safe to use?

Sellular scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Sellular MCP server expose?

Sellular exposes 20 tools: get_visibility_score, scan_domain, bulk_scan, seo_audit_summary, compare_visibility, and 15 more. Their descriptions and schemas cost roughly 4,026 tokens of context every time the server is loaded.

### Does the Sellular MCP server require authentication?

No. We connected to Sellular without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Sellular MCP server still maintained?

Sellular is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://sellular.online/api/mcp/mcp
- Website: https://sellular.online/
- Changelog RSS feed: https://verifymcp.io/servers/online-sellular-sellular/api-mcp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/online-sellular-sellular/api-mcp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/online-sellular-sellular/api-mcp-mcp