Walrus Tooth

Docs FAQ GitHub Open console

Apex predator of the codebase

Walrus
Tooth

AI that writes code with tusks in. Two megafauna incisors, one terminal, zero hesitation.

{{ ctaLabel }} $ npm i -g wt

0.4s

Cold start

1.1M

Token context

-40°C

Rated to

Programs

/ what runs on WT

Program 01 · v0.4.2 · live

AMH Cloudflare Ops MCP by WT

An approval-gated Cloudflare operations suite with an optional private Agent Harness: bounded delegation, deterministic verification, OAuth-isolated MCP tools, and verified deploy checks without handing agents raw account credentials.

Open the operator console → Get the code on GitHub → github.com/pain2hustle/cloudflare-ops-mcp — clone it, connect the MCP, and your agents land right here.

What it does

/ v0.4.2

07 capabilities · approval-gated

Private Agent Harness

Jack-friendly reusable profiles plus eight automatic process skill folders for safe deploys, live checks, mail loopback, lean handoffs, security review, private MCP access, Google source research, and optional Claude second opinions.

SafeTry controls

Read-only defaults, explicit approvals, narrow adapters instead of a generic shell, tenant isolation, retention limits, and a tamper-evident audit chain.

Verified deploy gate

Checks the public target for an explicit 2xx status, rejects redirects, and optionally requires an expected release marker before reporting success.

Deterministic site health

Zero-AI HTTP checks remain useful for small valid pages and can require an expected text marker to catch a 200 response serving the wrong site.

Self-catching email loopback

Exercises the configured sending/routing path and records delivery evidence; it does not claim to prove placement in a provider's inbox tab.

Cloudflare-native connections

Optional OAuth connectors for the official Cloudflare API, Workers Builds, Bindings, Observability, and Docs MCP services, plus Wrangler-based Worker deployment and secrets.

Guarded operations

Turnstile, DNS, SPF/DMARC/BIMI, Email Routing, Pages cutovers, cache purge, scoped tokens, and account diagnostics stay dry-run or approval-gated where they write.

What it handles

12 operations · dry-run first

Cloudflare Ops MCP is focused on the Cloudflare tasks that regularly break launches, email trust, bot checks, cache freshness, brand display, and AI-agent workflows:

Agents & audit Deploy, record, replay 03

08 Audit logs for applied changes.

11 MCP endpoint deployment on Cloudflare Workers with Wrangler secrets.

12 AI-agent safety defaults: dry-run first, diff display, no token in tool args, no accidental deletes.

Edge & bots Turnstile 01

10 Turnstile widget planning/creation for bot checks.

Email trust SPF · DKIM · DMARC · BIMI · Routing 06

02 SPF detection and planning so you do not accidentally create multiple SPF records.

03 DMARC parsing and policy updates that only change the fields you asked for.

04 BIMI TXT setup with a DMARC enforcement gate.

05 DKIM discovery so the report can tell whether sender keys exist.

06 MX and Cloudflare Email Routing checks.

07 Email Routing destination/rule setup with verified-destination protection.

DNS & records Scan, diff, approve 02

01 DNS record scan, lookup, create, update, no-op detection, and guarded delete.

09 Cloudflare Pages DNS cutovers and cache purge operations.

Five ways
to run it

Version 0.4.2 works five ways:

Stage {{ activeNum }} / 05

Safety model

Dry-run by default. Scan before write. Never delete as a side effect. Token hygiene, scoped token only, BIMI precondition, and an audit log for every apply.

Run mode

01{{ title0 }}

02{{ title1 }}

03{{ title2 }}

04{{ title3 }}