← Registry

Marketing

launchator.com

Provides tools to search, inspect, and find alternatives for SaaS/AI/indie products on Launchator, list categories, and submit new product listings.

1 endpoint12 known toolsFirst detected October 22, 2026Last detected October 22, 2026

ENDPOINT 1

https://launchator.com/api/mcp

No auth detected

MCP server metadata

Name
launchator
Version
1.0.0
Capabilities
tools.listChanged
Server instructions

Launchator (https://launchator.com) is a launch directory for SaaS, AI and indie products. Anyone can search it: search_products, get_product, alternatives_to, list_categories. Founders can launch their own product with an access token from https://launchator.com/agents: 1. submit_product with the homepage URL. It drafts a listing (name, headline, description, category, tags) in about 30 seconds. 2. Show the draft to the user and apply their changes with update_listing. 3. get_badge_snippet returns the link the site must carry. Add it to the site footer (any page template that renders on the homepage), commit and deploy. 4. verify_backlink checks the live homepage and publishes the listing. If it says the founder must confirm their email, ask them to click the link we emailed, then call publish. 5. Once live, check_ai_ready scores how well AI assistants can read the site and returns fixes you can apply in the codebase. Listings are free; the link must be a normal followed link on the homepage.

Known tools 12

search_products

Search Launchator's directory of SaaS, AI and indie products by what they do (e.

Inferred read-only
get_product

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

Inferred read-only
alternatives_to

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

Inferred read-only
list_categories

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

Inferred read-only
submit_product

Start a free Launchator listing for the user's own website.

Inferred read-only
list_my_products

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

Inferred read-only
get_my_product

One of the user's own listings or drafts.

Inferred read-only
update_listing

Change the text of the user's listing.

Inferred read-only
get_badge_snippet

The HTML link the product's homepage must carry for a free listing, as a text link or a badge image.

Inferred read-only
verify_backlink

Checks the live homepage for the Launchator link and, if it's there, publishes the listing.

Inferred read-only
publish

Re-checks whether a listing with a verified link can go live, e.

Potential side effects
check_ai_ready

Free check of how well AI assistants and search engines can read and recommend the user's live product site: robots.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.launchator]
url = "https://launchator.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "launchator": {
      "type": "http",
      "url": "https://launchator.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: launchator
Remote MCP URL: https://launchator.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "launchator": {
      "url": "https://launchator.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "launchator": {
      "type": "http",
      "url": "https://launchator.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "launchator",
  "transport": "streamable-http",
  "url": "https://launchator.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.