Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

YeetIt

REMOTE · YEETIT.SITE · SCANNED AUG 3

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

Available components

remote · yeetit.site 58
+2 this week 58 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1075 tokens (~268/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · yeetit.site

# add to Claude Code
claude mcp add --transport http snappyio-yeetit https://yeetit.site/mcp
# ~/.codex/config.toml
[mcp_servers.snappyio-yeetit]
url = "https://yeetit.site/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "snappyio-yeetit": {
      "type": "remote",
      "url": "https://yeetit.site/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add snappyio-yeetit --url https://yeetit.site/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  snappyio-yeetit:
    url: "https://yeetit.site/mcp"
// mcp.json
{
  "mcpServers": {
    "snappyio-yeetit": {
      "type": "http",
      "url": "https://yeetit.site/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 −2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 55

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://yeetit.site/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=yeetit.site CN=WE1,O=Google Trust Services,C=US 25 Jun 2026 23 Sept 2026 ECDSA 256 ECDSA-SHA256 92c4d43ae0302ac60e34423ec256ca04
SANs: yeetit.site
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of yeetit.site. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
site. present 31826 13 Verified
yeetit.site. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://yeetit.site/mcp Verified 200
http (plaintext) http://yeetit.site/mcp Served over HTTP 200
MCP tools — 4 exposed · ~1,075 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
delete_website ~185

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.

NameTypeReqDescription
api_keystring—The user's API key (e.g. "yt_abc123...").
confirmbooleanyesMust be set to true to confirm deletion. This is a safety mechanism — the tool will refuse to delete without explicit confirmation.
edit_keystring—The edit key for this site (e.g. "ek_9c4d2e7f...").
slugstringyesThe slug of the site to delete (e.g. "hello-world-k3m").

No output schema declared.

No examples provided.

get_website_status ~93

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.

NameTypeReqDescription
slugstringyesThe slug of the site to check (e.g. "hello-world-k3m").

No output schema declared.

No examples provided.

publish_website ~511

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.

NameTypeReqDescription
assetsobject—Optional map of filename to content for bundled assets. Keys are filenames (e.g. "style.css", "logo.png", "app.js"). Values are either plain text strings (for CSS, JS, SVG, HTML) or data URIs for bin…
htmlstringyesComplete HTML document to publish. Must be a valid, self-contained page. Inline CSS and JS are supported. External resources (images, fonts, scripts) must use absolute URLs OR be included in the asse…
titlestring—Human-readable title for the published page. Used in social sharing previews and the claim page. Optional.

No output schema declared.

No examples provided.

update_website ~286

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.

NameTypeReqDescription
api_keystring—The user's API key from their dashboard (e.g. "yt_abc123..."). Use this if the user has claimed the site and provided their API key.
assetsobject—Optional map of filename to content. If provided, replaces ALL existing assets. Omit to keep existing assets unchanged.
edit_keystring—The edit key returned when the site was originally published (e.g. "ek_9c4d2e7f..."). Use this if you still have it from the publish response.
htmlstringyesComplete HTML document to replace the existing page with. Must be a valid, self-contained page. This replaces the entire page content.
slugstringyesThe slug of the site to update (e.g. "hello-world-k3m").
titlestring—Optional new title for the page.

No output schema declared.

No examples provided.