add clawnch plugin

[clawnchdev]

Summary

Adds a Clawnch skill plugin to skills/base-mcp/plugins/clawnch.md and lists it in the SKILL.md native-plugins table.

Clawnch is a launchpad + token discovery surface on Base. It indexes ~140k tokens deployed via Clanker — through Clawnch directly and through integrated platforms (Moltbook, 4claw, Clawtomaton, and the clawmes Hermes Agent plugin) — and exposes two public read endpoints for discovery:

• GET /api/launches — recent launches, newest first, filterable by source and agent. Supports single-address lookup via ?address=....
• GET /api/tokens?sort=volume&prices=1 — top tokens by 24h trading volume with live price / market cap / volume / 24h change.

Buys route through Base MCP's own swap tool — no Clawnch MCP server is required. The plugin is read-only against the public API.

Differentiation vs. existing plugins

This is the closest sibling to the existing Bankr plugin (both are launch-discovery surfaces). What Clawnch adds on top:

• Top by 24h volume — Bankr's plugin is recency-only. Clawnch's /api/tokens endpoint exposes live price / mcap / volume / 24h change so the agent can answer "what's hot on Base right now?", not just "what just launched?"
• Source filtering — ?source=clawmes|moltbook|4claw|clawtomaton|moltx so users can scope to a specific integration ("show me clawmes launches from the last hour")
• 140k+ token index vs. Bankr's ~50-entry rolling window

API readiness

• Public read endpoints, no auth required
• 10-minute edge cache (Vercel s-maxage=600) on both /api/launches and /api/tokens
• 120 req/min/IP read throttle (recently bumped from 15 to accommodate agent-gateway fan-out from small egress IP pools)
• CORS configured for browser allowlist; agent server-side fetch is unconstrained

Example flows in the plugin spec

• "show me the latest token launches on Clawnch"
• "what's the top token on Base by volume right now?"
• "buy 0.001 ETH worth of the top volume token on Clawnch"
• "show me clawmes launches in the last hour"
• "what is this token? 0x32F6…8ba3" (paste-from-elsewhere flow)

Disclosure

I work on the Clawnch launchpad (clawnchdev is the project's bot account). Submitting under the same name so the plugin can be maintained alongside the underlying API.

Files

• New: skills/base-mcp/plugins/clawnch.md (382 lines, follows the published custom-plugins template + matches the structure of the existing Bankr plugin)
• Updated: skills/base-mcp/SKILL.md (one line — appends Clawnch to the native-plugins table after Bankr)

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 1 Sum 2

[clawnchdev]

Update: pushed a 114-line addition to the plugin spec for the non-custodial launch flow.

What changed: added a "Launch flow (non-custodial)" section after the existing discovery + buy content. It documents GET /api/prepare/deploy — a new endpoint we shipped to production today that returns unsigned Clanker factory calldata so Base MCP users can launch tokens through their own Base Account instead of through Clawnch's custodial deployer. Same 20% platform fee preserved in the rewards array, same Clanker vault curve via optional burnTxHash param.

Why ship the upstream update now: the endpoint is already live at https://www.clawn.ch/api/prepare/deploy (smoke-tested against the Clanker factory). Landing this content with the initial plugin merge means agents get the full feature set from day one — discovery, buy, AND deploy — without a follow-up PR.

No changes to the existing discovery + buy content. The new section is purely additive at the bottom of the plugin.

Happy to split this into two PRs if you'd prefer to ship discovery-only first and the launch flow as a follow-up — let me know.

[Suki9988]

Connect