BOSTON, MAY 12, 2026
PRODUCT SHIPPED
Intent Engineering MCP
─ METHODS ─
| TASK | AGENT / TOOL | MODEL / COST |
|---|---|---|
| protocol implementation | MCP SDK | open-source / $0 |
| registry verification | DNS-verified MCP registry | registry / $0 |
| package publish | npm | free tier |
| case-study writeup | case study | portfolio time |
─ EXPLANATION ─
What is this?
A Model Context Protocol server published to npm + the MCP registry on May 12, 2026. Two MCP tools registered (tools/list + tools/call); DNS-verified namespace. Installed by Claude Desktop with one line of config.
Why this approach?
Three options were on the table: ship as a standalone CLI tool, bake into a larger MCP, or ship as a registered server. The registered-server path won because DNS-verified registry adoption was the right scope-cut signal: recruiter could see the install count + registry presence at a glance. The case study at /work/intent-engineering-mcp documents what got cut to ship early.
What would break?
Three named failure modes: (1) Claude Desktop’s MCP client revs faster than this server; (2) DNS verification expiring; (3) npm registry vetting failing on first publish. Mitigations: semver discipline on the server, calendar reminder for renewal, manual vetting check before each publish.
What did I learn?
It shipped 13 days early because the design was right. What got cut was right too: the interactive MCP-tool-call embed page is a future spec, not v1. The cut list is on the case-study page; the install count is on this ledger row’s <ShippedNow /> block (rendered via the case-study route, not duplicated here).
─ WHAT THIS DOESN'T YET DO ─
- Claude Desktop's MCP client revs faster than the server; semver discipline is the v1.x discipline.
- DNS verification expires annually; renewal is on Sean's calendar but not automated.