# Noonlaunch (remote · noonlaunch.com)

Launch a product on Noonlaunch, search its directory and weekly winners, and find 333 launch sites.

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

## Components

- remote · `noonlaunch.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-noonlaunch-mcp/noonlaunch.md), [page](https://verifymcp.io/servers/com-noonlaunch-mcp/noonlaunch)

## Channel facts

- Endpoint: `https://noonlaunch.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.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-11-06.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1624 tokens (~162/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 Noonlaunch MCP server?

Noonlaunch is a hosted endpoint at https://noonlaunch.com/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 com-noonlaunch-mcp 'https://noonlaunch.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-noonlaunch-mcp": {
      "url": "https://noonlaunch.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-noonlaunch-mcp": {
      "type": "http",
      "url": "https://noonlaunch.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-noonlaunch-mcp]
url = "https://noonlaunch.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-noonlaunch-mcp --url 'https://noonlaunch.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-noonlaunch-mcp:
    url: "https://noonlaunch.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-noonlaunch-mcp": {
      "Transport": "http",
      "Url": "https://noonlaunch.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-noonlaunch-mcp -t streamable-http -u 'https://noonlaunch.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-noonlaunch-mcp": {
      "type": "http",
      "url": "https://noonlaunch.com/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-11-06 (score 74, 0)

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

### 2026-11-05 (score 74, +1)

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

### 2026-11-03 (score 73, +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-10-31 (score 72, +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.

### 2026-10-30 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 71)

First indexed and scored.

## MCP tools (10)

### `search-directory` (~88 tokens)

Search Directory

Search the Noonlaunch product directory. Returns approved products matching the query, ordered by community votes, with links to their Noonlaunch product pages.

Input parameters:

- `category` (string): Optional category slug or name to narrow results.
- `limit` (integer): Max results to return (1-25, default 10).
- `query` (string): Search term matched against product names, taglines and descriptions.

### `get-product` (~58 tokens)

Get Product

Get full public details of one Noonlaunch product by its slug (the last part of its noonlaunch.com/product/... URL).

Input parameters:

- `slug` (string): The product slug, e.g. "my-product" for noonlaunch.com/product/my-product.

### `get-weekly-winners` (~93 tokens)

Get Weekly Winners

Get the Noonlaunch launch board for a week: the top-voted free launches, with the top 3 marked as winners. weeks_ago 0 is the current (still running) week, 1 is the last completed week.

Input parameters:

- `weeks_ago` (integer): How many weeks back (0 = current running week, 1 = last completed week, default 1, max 52).

### `list-launch-directories` (~115 tokens)

List Launch Directories

Browse Noonlaunch's curated list of 333 startup launch directories and communities where founders can submit a product. Filterable by category, cost and minimum domain authority.

Input parameters:

- `category` (string): Filter by directory category, e.g. "AI", "SaaS", "General".
- `free_only` (boolean): Only directories that are free to submit to.
- `limit` (integer): Max results (1-100, default 50).
- `min_da` (integer): Minimum domain authority (0-100).

### `get-plans` (~68 tokens)

Get Plans

What it costs to launch on Noonlaunch, and what each plan includes. Use this to answer a pricing question on its own. To actually submit a product, call check_product instead: which plans apply depends on the site, because relaunching one that is already listed needs a paid plan.

### `check-product` (~84 tokens)

Check Product

Check whether a product can be submitted to Noonlaunch, and get the plans, categories and launch weeks available for it. Always call this first, and always ask the person for their live public website URL rather than guessing it from their code.

Input parameters:

- `website_url` (string): The live public URL of the product, as given by the person. Never a localhost or development address.

### `submit-product` (~239 tokens)

Submit Product

Submit a product to Noonlaunch. Nothing is published by this call. It returns a claim link to give the person straight away, and for free launches the badge snippet to install. Call check_product first.

Input parameters:

- `category` (string): Category id or slug from check_product.
- `description` (string): What the product does, 30-600 characters. Longer text is rejected, not trimmed.
- `launch_week` (string): Optional launch week as a Monday date (YYYY-MM-DD) from check_product. Defaults to the next open week.
- `logo_url` (string): Optional public URL of the product logo image, which we download.
- `name` (string): Product name, 2-100 characters.
- `plan` (string): One of: free, bundle_featured, bundle_spotlight. Ask the person which they want.
- `tagline` (string): One line shown on the board, 10-70 characters.
- `twitter_handle` (string): Optional X handle, with or without the @.
- `website_url` (string): The live public URL the person confirmed. Never guess this from the codebase.

### `verify-badge` (~74 tokens)

Verify Badge

Check that the Noonlaunch badge is installed on the product site and publish the listing if it is. Only for free launches, and only after the person has deployed the change. Paid listings are published by payment instead, so use check_status for those.

Input parameters:

- `submission_token` (string): The submission_token returned by submit_product.

### `check-status` (~61 tokens)

Check Status

Where a submission stands: whether it has been claimed, paid for, verified and published. This is the only way to find out whether a payment has landed. Poll it rather than assuming.

Input parameters:

- `submission_token` (string): The submission_token returned by submit_product.

### `report-badge-problem` (~114 tokens)

Report Badge Problem

Report that the badge check is wrong: the badge is installed and visible but we cannot find it. Only use this after verify_badge has failed twice and you have confirmed the badge really is live on the page. A person reviews it within 24 hours.

Input parameters:

- `message` (string): Where the badge is on the page and what you have already checked, so a human can resolve it without asking. 20-1500 characters.
- `submission_token` (string): The submission_token returned by submit_product.

## Diagnostics

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

## Score history

- 2026-11-06: 74
- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 71
- 2026-10-29: 71

## Common questions

### What is the Noonlaunch MCP server?

Noonlaunch is an MCP server listed in the public MCP registry as com.noonlaunch/mcp. Launch a product on Noonlaunch, search its directory and weekly winners, and find 333 launch sites. This page covers its hosted endpoint (https://noonlaunch.com/mcp).

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

Noonlaunch scores 74 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 Noonlaunch MCP server expose?

Noonlaunch exposes 10 tools: search-directory, get-product, get-weekly-winners, list-launch-directories, get-plans, and 5 more. Their descriptions and schemas cost roughly 994 tokens of context every time the server is loaded.

### Does the Noonlaunch MCP server require authentication?

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

### Is the Noonlaunch MCP server still maintained?

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

### What did VerifyMCP test on the Noonlaunch MCP server?

VerifyMCP ran 13 checks on Noonlaunch, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://noonlaunch.com/mcp
- Repository: https://github.com/mukund1158/noonlaunch-mcp
- Website: https://noonlaunch.com/launch-with-ai
- Changelog RSS feed: https://verifymcp.io/servers/com-noonlaunch-mcp/noonlaunch.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-noonlaunch-mcp/noonlaunch/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-noonlaunch-mcp/noonlaunch.json
- HTML version of this page: https://verifymcp.io/servers/com-noonlaunch-mcp/noonlaunch