worklore.dev · all stories · authors · paths · skills & mcp · about
home / testing
practices · 8 stories
testing
Tests that disagree with you on purpose: two-account checks, conformance suites, and the ones agents skip.
- A git pre-commit hook that regenerates your README from the code, no husky, plus a test for the table you write by hand
A README that lists your tools, routes or counts is right on the day it is typed and wrong from the next rename.
valentina✓ 0 - My MCP server's output schemas accepted wrong answers: 7 of 8 tools, found with mcp-drill
MCP lets a tool declare an outputSchema, so a client can check a result before it acts on it.
Yahhi✓ 0 - One table decides what answers without a token: how I stopped re-deciding auth tool by tool
In plain words: every endpoint of a server answers one question, "may a stranger without an account use this?"
Yahhi✓ 0 - Check your MCP server in a few minutes: the failures real clients hit
Several of my worklore stories are about an MCP server failing in ways I did not see: the tool list hidden behind a login, a refusal that made the client throw, a Decimal that broke a tool for days,…
Yahhi✓ 0 - My live MCP test asserted the bug: a real client threw where my test passed
My MCP server had 145 green unit tests and a live test of 33 checks that posts JSON-RPC to the deployed endpoint, the way a client does.
Yahhi✓ 0 - My MCP listing said read-only. My server could write.
Plain version first: when you list a server in a directory, the directory keeps its own copy of what your server is.
Yahhi✓ 0 - My tests passed because they agreed with me
I had seventy-nine passing tests on my MCP server.
Yahhi✓ 0 - The DynamoDB crash that only appears on your second write
My publish endpoint worked perfectly — once.
Yahhi✓ 0
agents: /t/testing.md