# Microlaunch (remote · mcp.microlaunch.net)

Find tools and apps by indie makers: top launches, categories, product details and deals.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://mcp.microlaunch.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-05.

- **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**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 425 tokens (~85/item across 5 items; 4 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Microlaunch MCP server?

Microlaunch is a hosted endpoint at https://mcp.microlaunch.net/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 greyzor-microlaunch-mcp 'https://mcp.microlaunch.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "greyzor-microlaunch-mcp": {
      "url": "https://mcp.microlaunch.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "greyzor-microlaunch-mcp": {
      "type": "http",
      "url": "https://mcp.microlaunch.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.greyzor-microlaunch-mcp]
url = "https://mcp.microlaunch.net/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add greyzor-microlaunch-mcp --url 'https://mcp.microlaunch.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  greyzor-microlaunch-mcp:
    url: "https://mcp.microlaunch.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "greyzor-microlaunch-mcp": {
      "Transport": "http",
      "Url": "https://mcp.microlaunch.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add greyzor-microlaunch-mcp -t streamable-http -u 'https://mcp.microlaunch.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "greyzor-microlaunch-mcp": {
      "type": "http",
      "url": "https://mcp.microlaunch.net/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-05 (score 74, +1)

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

### 2026-11-03 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 72)

First indexed and scored.

## MCP tools (4)

### `browse_category` (~85 tokens)

Best tools in a category

List the best-ranked products on Microlaunch in a category (e.g. 'AI', 'marketing', 'dev tools', 'productivity', 'SEO', 'no-code'). Use for 'best X tools' or 'what tools exist for Y' questions. If the category is unknown, the result lists valid categories.

Input parameters:

- `category` (string, required): Category name or slug

### `top_launches` (~101 tokens)

Top launches on Microlaunch

Get the current Microlaunch leaderboard: top-ranked launches from today, the last 7 days or the last 30 days, optionally filtered by category slug (e.g. ai, marketing, dev-tools, productivity, seo). Use for 'what's new/trending in indie products' questions.

Input parameters:

- `category` (string): Category name or slug, e.g. ai, marketing, dev tools
- `scope` (string): Defaults to this_week

### `get_product` (~59 tokens)

Microlaunch product details

Get details for one Microlaunch product by its slug (from browse_category or top_launches results): description, category, stage, votes, reviews count and awards.

Input parameters:

- `slug` (string, required): Product slug, e.g. 'tagparrot'

### `list_deals` (~57 tokens)

Maker deals on Microlaunch

List active discounts and lifetime deals from indie makers on Microlaunch, optionally by category slug. Codes are revealed on Microlaunch, not here.

Input parameters:

- `category` (string): Category name or slug, e.g. ai, marketing

## Diagnostics

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

## Score history

- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72

## Common questions

### What is the Microlaunch MCP server?

Microlaunch is an MCP server listed in the public MCP registry as io.github.greyzor/microlaunch-mcp. Find tools and apps by indie makers: top launches, categories, product details and deals. This page covers its hosted endpoint (https://mcp.microlaunch.net/mcp).

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

Microlaunch 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 Microlaunch MCP server expose?

Microlaunch exposes 4 tools: browse_category, top_launches, get_product, list_deals. Their descriptions and schemas cost roughly 302 tokens of context every time the server is loaded.

### Does the Microlaunch MCP server require authentication?

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

### Is the Microlaunch MCP server still maintained?

Microlaunch 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 Microlaunch MCP server?

VerifyMCP ran 14 checks on Microlaunch, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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://mcp.microlaunch.net/mcp
- Repository: https://github.com/greyzor/microlaunch-mcp
- Website: https://microlaunch.net/
- Changelog RSS feed: https://verifymcp.io/servers/greyzor-microlaunch-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/greyzor-microlaunch-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/greyzor-microlaunch-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/greyzor-microlaunch-mcp/mcp