SOLGPT — Clawd bot + commands

The pump.fun agent. Live tape, Pump SDK, Jupiter/DFlow, on-device OWS. Add it on Grok or run the public clawd-bot template against this origin.

Commands

/pump /wallet /buy /sell /trending /auto /fund

Grok Bot: https://x.ai/bot/KZEcx_uMDR-zJIXLlYw5I

Share: https://clawdbot.x402.life

Start a computer here: /llms.txt then /agent/. Keys stay on device. Never print keys.

What this does and how it works

Two parts sit in front of the origin. Same for these static pages and the React SPA.

Edge/origin injects one line: a module script at /.webmcp/bridge.js with data-packs="c2pa,mcp-server-client" and data-mcp-url="/mcp". Cloudflare may also inject this at the edge. This origin copy is the fallback.
The bridge finds document.modelContext. If the browser has no WebMCP surface, it no-ops and the page is unchanged.

Packs register MCP tools. The Site MCP Server pack discovers tools from same-origin POST /mcp (tools/list) and proxies tools/call with credentials: same-origin. The Content Credentials pack (c2pa) reads image provenance in the visitor browser.

Agents already speaking MCP can drive the page. clawd-bot computers: open /llms.txt then /agent/ then call /mcp.

$CLAWD still gates computer, art, Grok/Hauhau (100,000 $CLAWD). Public MCP tools are read-only (pages, trending, health, pump quote). No keys.

Longer explainer: WebMCP.