← Registry

Developer Tools

yeetit.site

Publishes and manages static websites by instantly deploying HTML content to live URLs.

1 endpoint4 known toolsFirst detected May 10, 2026Last detected August 29, 2026

ENDPOINT 1

https://yeetit.site/mcp

No auth detected

MCP server metadata

Name
yeetit
Version
1.0.0
Capabilities
tools

Known tools 4

publish_website

Publish HTML content to a live URL instantly.

Potential side effects
update_website

Update an existing published website with new HTML content.

Potential side effects
delete_website

Permanently delete a published website.

Potential side effects
get_website_status

Get information about a published website including its title, view count, size, expiry date, and whether it has been claimed.

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.yeetit]
url = "https://yeetit.site/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "yeetit": {
      "type": "http",
      "url": "https://yeetit.site/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: yeetit
Remote MCP URL: https://yeetit.site/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": {
    "yeetit": {
      "url": "https://yeetit.site/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "yeetit": {
      "type": "http",
      "url": "https://yeetit.site/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

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