Noonlaunch
REMOTE · NOONLAUNCH.COM
Launch a product on Noonlaunch, search its directory and weekly winners, and find 333 launch sites.
Available components
Last scanned (11 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 31 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.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 71
First indexed and scored.
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://noonlaunch.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noonlaunch.com | CN=YE2,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5f2fa30d97fa40b96a41ad636087ecd96d7 |
| SANs: noonlaunch.com, www.noonlaunch.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of noonlaunch.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| noonlaunch.com. | No DS | 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 |
|---|---|
| content-security-policy | upgrade-insecure-requests |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://noonlaunch.com/mcp | Verified | 200 | |
| http (plaintext) | http://noonlaunch.com/mcp | HTTPS enforced | 301 | https://noonlaunch.com/mcp |
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 →
check-product Check Product ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| website_url | string | – | The live public URL of the product, as given by the person. Never a localhost or development address. |
No output schema declared.
No examples provided.
check-status Check Status ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| submission_token | string | – | The submission_token returned by submit_product. |
No output schema declared.
No examples provided.
get-plans Get Plans ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-product Get Product ~58
Get full public details of one Noonlaunch product by its slug (the last part of its noonlaunch.com/product/... URL).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | The product slug, e.g. "my-product" for noonlaunch.com/product/my-product. |
No output schema declared.
No examples provided.
get-weekly-winners Get Weekly Winners ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| weeks_ago | integer | – | How many weeks back (0 = current running week, 1 = last completed week, default 1, max 52). |
No output schema declared.
No examples provided.
list-launch-directories List Launch Directories ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
report-badge-problem Report Badge Problem ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
search-directory Search Directory ~88
Search the Noonlaunch product directory. Returns approved products matching the query, ordered by community votes, with links to their Noonlaunch product pages.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
submit-product Submit Product ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
verify-badge Verify Badge ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| submission_token | string | – | The submission_token returned by submit_product. |
No output schema declared.
No examples provided.
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.
remote · noonlaunch.com
claude mcp add --transport http com-noonlaunch-mcp 'https://noonlaunch.com/mcp'
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 5 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.