Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Launchator

REMOTE · LAUNCHATOR.COM

Search a launch directory of new products, and submit and publish your own listing.

Available components

+3 this week 70 Trust /100

Last scanned (1 hour ago)

Scores higher than 55% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 976 tokens (~81/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 76% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 30 Oct 26 +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.

  • 28 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

  • 23 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 22 Oct 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://launchator.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=launchator.com CN=WR3,O=Google Trust Services,C=US 15 Oct 2026 13 Jan 2027 RSA 2048 SHA256-RSA d2dc1eed366d74690af403b53fc5dadb
SANs: launchator.com, *.launchator.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of launchator.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
launchator.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://launchator.com/api/mcp Verified 200
http (plaintext) http://launchator.com/api/mcp HTTPS enforced 301 https://launchator.com:443/api/mcp
MCP tools · 12 exposed · ~733 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
alternatives_to ~31

Products on Launchator similar to a given listed product (same category or tags).

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

check_ai_ready ~100

Free check of how well AI assistants and search engines can read and recommend the user's live product site: robots.txt rules for AI crawlers, server-rendered content, structured data, llms.txt, meta tags and more, with a score, the top fixes and copy-ready code. Up to 3 runs per listing per day. Needs an access token.

NameTypeReqDescription
productIdstringyesThe productId returned by submit_product or list_my_products

No output schema declared.

No examples provided.

get_badge_snippet ~65

The HTML link the product's homepage must carry for a free listing, as a text link or a badge image. Add one to the site footer. Needs an access token.

NameTypeReqDescription
productIdstringyesThe productId returned by submit_product or list_my_products

No output schema declared.

No examples provided.

get_my_product ~42

One of the user's own listings or drafts. Needs an access token.

NameTypeReqDescription
productIdstringyesThe productId returned by submit_product or list_my_products

No output schema declared.

No examples provided.

get_product ~53

Full details of one product listed on Launchator: description, website, category, tags and upvotes.

NameTypeReqDescription
slugstringyesThe product's slug, from search results or its URL launchator.com/p/{slug}

No output schema declared.

No examples provided.

list_categories ~20

Launchator's product categories with how many products each has.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_my_products ~30

The user's own Launchator listings and drafts, with their status and next step. Needs an access token.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

publish ~55

Re-checks whether a listing with a verified link can go live, e.g. after the founder confirmed their email. Needs an access token.

NameTypeReqDescription
productIdstringyesThe productId returned by submit_product or list_my_products

No output schema declared.

No examples provided.

search_products ~86

Search Launchator's directory of SaaS, AI and indie products by what they do (e.g. 'invoicing for freelancers', 'screen recorder'). Returns the best matches with links.

NameTypeReqDescription
categorystring–Limit to one category slug (see list_categories)
limitinteger–Default 10
querystringyesWhat the user is looking for

No output schema declared.

No examples provided.

submit_product ~70

Start a free Launchator listing for the user's own website. Loads the homepage, screens it, and drafts the listing (takes about 30 seconds). Returns the draft and the next step. Needs an access token.

NameTypeReqDescription
urlstringyesThe product's homepage, e.g. https://example.com

No output schema declared.

No examples provided.

update_listing ~119

Change the text of the user's listing. Only pass the fields to change. Logos and screenshots are changed in the browser (editInBrowser link). Needs an access token.

NameTypeReqDescription
categorystring––
descriptionstring–50 to 2,500 characters, plain text with line breaks
namestring––
productIdstringyesThe productId returned by submit_product or list_my_products
taglinestring–One-line headline, up to 80 characters
tagsarray––

No output schema declared.

No examples provided.

verify_backlink ~62

Checks the live homepage for the Launchator link and, if it's there, publishes the listing. Call after the site with the link is deployed. Needs an access token.

NameTypeReqDescription
productIdstringyesThe productId returned by submit_product or list_my_products

No output schema declared.

No examples provided.

Install

How do I install the Launchator MCP server?

Launchator is a hosted endpoint at https://launchator.com/api/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.

remote · launchator.com

# add to Claude Code
claude mcp add --transport http com-launchator-launchator 'https://launchator.com/api/mcp'
Common questions

What is the Launchator MCP server?

Launchator is an MCP server listed in the public MCP registry as com.launchator/launchator. Search a launch directory of new products, and submit and publish your own listing. This page covers its hosted endpoint (https://launchator.com/api/mcp).

Is the Launchator MCP server safe to use?

Launchator scores 70 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 Launchator MCP server expose?

Launchator exposes 12 tools: search_products, get_product, alternatives_to, list_categories, submit_product, and 7 more. Their descriptions and schemas cost roughly 733 tokens of context every time the server is loaded.

Does the Launchator MCP server require authentication?

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

Is the Launchator MCP server still maintained?

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