Website Launch

io.github.jgaethle10Published by GitHub account jgaethle10v1.0.2Updated Oct 24, 2026

Business website planning and launch assistance with human-confirmed next steps.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint that helps an assistant plan a business website launch and confirm next steps with a human.

What you can do
Website Launch is a remote MCP server reached over streamable HTTP at a hosted endpoint. According to its registry description, it assists with business website planning and launch, and it keeps a human in the loop by requiring confirmation of next steps. No tool list is published, so the exact operations it exposes are not documented in the available material.
When to use it
Consider it when you want an assistant to help draft or organize a business website launch plan and to pause for human confirmation before proceeding. It is less useful if you need a documented, specific set of tools, since none are listed.
Requirements
A remote MCP client that supports streamable HTTP, plus network access to the hosted endpoint. No authentication, environment variables, headers, or local packages are declared.
Before you install
The server is hosted by a third party, so any planning details you share are sent to that endpoint. No authentication is declared, which means the endpoint is not gated by credentials. No tool list is published, so what it can read or change is unclear; confirm behavior before relying on it.

Installation

In SourceWeft

  1. Open Website Launch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.jgaethle10%2Fwebsite-launch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "website-launch": {
      "type": "http",
      "url": "https://instant-website-builder-usa-6feac193.base44.app/functions/websiteServiceMcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.0.2LatestSep 25, 2026
  2. v1.0.0Sep 24, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.