Servidor MCP de Sellular

• Nome no registroonline.sellular/sellularverificado no registro MCP

O nome no registro fica sob sellular.online. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-26
• Ferramentas22
• O servidor se chamasellular
• Versão do servidor1.0.0
• Versão do protocolo2025-06-18

Em 2026-10-26 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 211 ms.

• As ferramentas fazem todos os casos de uso verificados: generate llms.txt, robots.txt and sitemap files; run SEO audits and check site visibility scores.
• Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 2 até agora
• O que um agente consegue fazer com ele2 de 2 casos de uso
• Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta282 ms
• Espaço no contexto do agente≈ 6.924 tokensas definições de todas as ferramentas (22), que o agente carrega a cada turno
• Definições das ferramentasA · 98 de 100
• Resultados tipados0 de 22 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 3 de 22

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• 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…

• scan_domain

  One-call visibility audit for a public website: Sellular visibility score (0-100, A-F) and whether llms.txt exists (root or .well-known). For a domain we already list, also the tracked directories in its category with no known listing…

• 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…

• 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…

• answer_engine_gap

  For the queries a buyer actually types, which pages currently answer them, and is this site one of them? Every other tool here reads the site's own bytes; this reads the market around it, which is the gap a clean site can still have. PASS…

• answer_page_targets

  Who could publish a page that names this site. Runs answer_engine_gap, then keeps only the slot-holders whose TITLE reads like a third-party roundup ("17 Best X Tools", "X alternatives") rather than a vendor's own landing page, collapses…

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

• generate_llms_txt

  Generate an llms.txt file body for a public website from its fetched metadata: site name, description and key pages. Returns the text to serve at the site root as /llms.txt; an agent in the site's repo should write it to public/llms.txt…

• 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…

• 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…

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

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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>…

• 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…

• 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…

• 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)…

• 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…