YeetIt

io.github.snappyioPublished by GitHub account snappyiov1.0.0Updated Oct 24, 2026

Instant web publishing for AI agents. POST HTML, get a live URL. No account needed.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant publish HTML content to the web and receive a live URL, with no account required.

What you can do
YeetIt is a remote MCP endpoint for instant web publishing. Based on the registry description, it accepts HTML content and returns a live URL where that content is hosted. It is described as requiring no account, so publishing appears to be a single submit-and-get-link action rather than a managed site workflow.
When to use it
Useful when an assistant needs to turn generated HTML into a shareable live page quickly, such as sharing a report, prototype, or snippet without setting up hosting. It fits one-off publishing rather than ongoing site management.
Requirements
A remote MCP endpoint at the provider's site; no packages, environment variables, headers, or authentication are declared. Network access to the remote endpoint is required.
Before you install
Published content becomes publicly reachable at a live URL, so avoid sending secrets, private data, or anything not meant to be public. No authentication is declared, so anyone with the endpoint could potentially publish; consider how abuse or unwanted content might be attributed.

Installation

In SourceWeft

  1. Open YeetIt 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.snappyio%2Fyeetit/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": {
    "yeetit": {
      "type": "http",
      "url": "https://yeetit.site/mcp"
    }
  }
}

README

This repository has no README.

Tools

4

publish_website

Publish HTML content to a live URL instantly. No account or API key required. Returns a public URL that anyone can visit. Sites expire after 24 hours unless the owner claims them. Use this when a user asks you to build, create, or deploy a website, landing page, invitation, portfolio, report, or any HTML content they want to share as a link. Supports bundled assets (CSS, JS, images) and multi-page sites (include additional .html files in assets, accessible at /{slug}/{pagename}). IMPORTANT: After publishing, always share the live URL and the claim URL with the user. The claim URL lets them take permanent ownership of the site. Store the edit_key from the response silently — do not show it to the user — you will need it if they ask you to make changes to the site later. If you lose the edit_key, ask the user to claim the site first (via the claim URL in the page footer), then provide you with their API key from the dashboard — you can use that instead.

Parametershtmlrequiredtitleassets

update_website

Update an existing published website with new HTML content. Requires authentication via edit_key (from the original publish response) or api_key (from the user's dashboard after claiming the site). The html field replaces the entire page — this is a full replacement, not a patch. You can also update assets. Use this when a user asks you to modify, edit, or change a site you previously published. IMPORTANT: You must provide either edit_key or api_key for authentication.

Parametershtmlrequiredslugrequiredtitleassetsapi_keyedit_key

delete_website

Permanently delete a published website. The site will be immediately inaccessible. Requires authentication via edit_key or api_key, and requires confirm: true as a safety mechanism to prevent accidental deletion. Use this when a user explicitly asks you to remove or delete a site. IMPORTANT: Always confirm with the user before calling this tool — deletion cannot be undone.

Parametersslugrequiredapi_keyconfirmrequirededit_key

get_website_status

Get information about a published website including its title, view count, size, expiry date, and whether it has been claimed. No authentication required — this is public information. Use this to check if a site is still live, see how many views it has gotten, or check when it expires.

Parametersslugrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.