Building MCP Servers in Production on Start AI Tools - Presented by Intent Solutions

Foundation Ship — Guidewire MCP v0.1.0

Tue, 05 May 2026 08:00:00 -0500

Source post: Guidewire MCP v0.1.0 — foundation ship

The phrase “minimum viable product” is a trap when you’re building infrastructure. MVP frames the conversation around what you can take out and still ship — which is exactly the wrong question for a server that other systems are about to depend on. Foundation is the better word: not the smallest thing that works, but the smallest thing that won’t have to be torn out and rebuilt when chapter two arrives.

Tests That Actually Catch Regressions

Tue, 05 May 2026 08:00:00 -0500

Source post: Anti-slop framework finds three bugs inside itself

A test suite that mocks the function under test is theater. It runs green, it produces coverage numbers, it makes the dashboard look healthy — and it catches nothing. The function it’s “testing” never actually executes.

The anti-slop principles are simple and they aren’t new. What’s new is treating them as a CI gate that an AI agent cannot escape:

Don’t mock the function under test. Mock its dependencies; let the function itself run.
Use exact assertions, not “is truthy.” A test that passes when the answer is 42 and also when it’s "42" is not a test.
Use asymmetric inputs. A test on add(2, 2) that passes returns 4 from a function that does a * b is a tautology.
No tautologies. assert(x == x) is not a test, even when x is a function call.

The bugs the framework found in itself

The post linked above documents three real bugs the framework caught when it was first turned loose on its own implementation. The most embarrassing one was a “happy path” test that asserted the wrong field — passed for two months before the framework’s own escape-scan flagged it.

Four Production-Deploy Gotchas

Tue, 05 May 2026 08:00:00 -0500

Source post: Four production deploy gotchas (companion: VPS-as-the-home Day 1)

Tests pass. CI is green. The merge is clean. You hit deploy and the production logs light up. Welcome to the seam where everything you tested doesn’t quite match where you’re running.

The four

Container image is built on a different libc than the host. Compiles fine, runs fine in CI, segfaults on the host because the prebuilt wheel was linked against musl and the host is glibc. Add an explicit base-image declaration to your Dockerfile and run a smoke test on the production image during CI, not just the host CI image.