Marketing

vibelaunched.com

An MCP server for discovering and qualifying product launch venues, providing venue search, detailed submission requirements, and fit assessment for a project.

1 endpoint3 known toolsFirst detected September 11, 2026Last detected September 11, 2026

ENDPOINT 1

https://vibelaunched.com/api/mcp

No auth detected

MCP server metadata

Name: vibelaunched
Version: 1.0.0

Capabilities

tools

Server instructions

vibelaunched maps the launch venues that will take a product. search_venues filters the registry, get_venue returns one venue's full record including field limits and the rules that get a submission rejected, and qualify_project sorts every venue into ready, fixable, and out of reach for a product you describe. Name and URL are the only required facts: anything you leave out comes back as a question, never as a rejection. These tools hand over the map and the rules for free. The scan, the per-venue copy, the images brief, and the filled-in launch kit are generated on vibelaunched.com.

Known tools 3

search_venues

Filter the launch registry by text, kind, tier, cost, or focus.

Inferred read-only

get_venue

Everything typed about one venue: submit URL, field limits, what it accepts, what gets a submission rejected, the review process, the wait, and the gotchas.

Inferred read-only

qualify_project

Sort every venue into ready, fixable, and out of reach for one product, with the rule behind each answer and a suggested run order.

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.vibelaunched]
url = "https://vibelaunched.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "vibelaunched": {
      "type": "http",
      "url": "https://vibelaunched.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: vibelaunched
Remote MCP URL: https://vibelaunched.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": {
    "vibelaunched": {
      "url": "https://vibelaunched.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "vibelaunched": {
      "type": "http",
      "url": "https://vibelaunched.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "vibelaunched",
  "transport": "streamable-http",
  "url": "https://vibelaunched.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.