Waitlist Kit

io.github.therealMrFunGuyPublished by GitHub account therealMrFunGuyv1.0.0Updated Oct 24, 2026

Viral waitlists with referral tracking, leaderboards, analytics, and built-in themes.

VerifiedSSEWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

A remote MCP server for building viral waitlists with referral tracking, leaderboards, analytics, and built-in themes.

What you can do
Waitlist Kit is a hosted MCP endpoint that lets an assistant work with viral waitlist campaigns. According to its description, it covers referral tracking, leaderboards, analytics, and built-in themes. No individual tools are listed in the available material, so the exact operations an assistant can call are not documented here.
When to use it
Consider it when you want an assistant to help run or inspect a waitlist campaign that uses referral tracking, leaderboards, or campaign analytics, and you are comfortable with a hosted third-party service.
Requirements
A remote MCP connection over SSE to the provider's endpoint. An API key is sent in the X-API-Key header, obtained from the provider's dashboard. No packages, environment variables, or other credentials are declared.
Before you install
The server is hosted by a third party and requires an X-API-Key credential, so campaign data and the key are shared with that provider. The description mentions referral tracking and analytics, which implies collection of participant and referral data. No tool list is published, so what the assistant can read or change is unclear; verify scope before connecting.

Installation

In SourceWeft

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

Web executable via SSE. 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.therealMrFunGuy%2Fwaitlist-kit/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": {
    "waitlist-kit": {
      "type": "sse",
      "url": "https://waitlist.rjctdlabs.xyz/sse"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 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.