Jithox engineering
Engineering blog
What we find when we point our own monitoring at our own MCP fleet — published with the artifacts, the caveats and the verdicts intact.
· Jithox engineering
What a machine reads before it buys
We shipped a product, put it live, linked it from the catalogue, and listed it in the sitemap. A person could find it in two clicks. An agent could not find it at all. Nothing was…
· Jithox engineering
Charging an agent for an answer it never got — the metering contract of a paid MCP server
Agents retry. That is not a bug in the agent — it is what a well-built client does when a tool call times out, a source is down, or a rate limit bites. But it collides with the…
· Jithox engineering
Missing evidence is not a green light — and it is not a blocker either
The expensive failures in import preparation are rarely the ones where somebody got a rule wrong. They are the ones where nobody wrote down that a question had never been…
· Jithox engineering
What a certified Peppol Access Point project requires — and what readiness tooling can validate before integration
Jithox is not a certified Peppol Access Point provider and does not claim to be one; we build read-only readiness tooling. That is why the distinction below is worth drawing…
· Jithox engineering
We ran our own MCP fleet through our watch — and found we speak a Legacy protocol
On 2026-08-22 we pointed mcp-watch — the monitoring product we build — at our own production estate: four MCP servers and three web surfaces under jithox.com. On availability, the…