The Dangerous Bugs Are the Ones That Don't Crash: Building Input Validation for My MCP Server I was building an MCP server for an event platform that automates speaker communications (confirmations, reminders, calendar invites, follow-ups). An agent created a session confirmation for "Monday March 8th." March 8th was a Sunday. I caught it. But catching it was just the beginning. The confirmation
State that survives a docker compose down is one of those things you don't think about, until your test suite needs it, your local dev needs it, and your CI pipeline absolutely doesn't. LocalStack handles persistence with one switch (PERSISTENCE=1) and it's a Pro-only feature. Floci ships four storage modes, all free, all in core, with per-service overrides. Pick the right tradeoff for the job.