For AI buildersUp is not the same as right.
An AI product fails quietly. The page loads, the API says 200, and the agent gives a wrong answer, the MCP server lost a tool, or the gateway fell back to another model. OpenPing checks those parts directly, from outside, the way your users meet them.
Agents and their answers
Real questions on a schedule and after every deploy. Rules check the answer (contains, leaves out, matches a schema, no personal data, no refusal), then an AI judge reads it against your rubric. You see the pass rate over time and hear when it drops.
Agent tests
MCP servers
The handshake on new and older protocol versions, the sign-in, the tool, resource and prompt lists, any change to a tool, and a safe read-only test call. Destructive tools are never called.
Next: the protocol’s own ping, and checks that a server refuses what it should, such as a call without a token. Coming
MCP monitors
Model gateways
Every model your app uses, asked with the settings your app really sends: the system prompt shape, tools, reasoning settings, headers. Time to first token, and which model actually answered. A setting a new model refuses fails here before it fails for your users.
Gateway monitors
Hidden instructions for AI
Everything a check reads is also read for text written to steer an AI: in pages, API answers, MCP tool lists, agent cards and agent answers. Invisible characters and hidden HTML included. On by default, on every plan.
Break-it tests Coming
Most teams test that their app works. Few test what it does when what reaches it is hostile or broken, and that is where AI apps fail. On paid plans, for apps you’ve shown are yours, OpenPing will test on a schedule that:
- Poisoned files are refused by your upload path, using standard harmless test files, and clean ones still go in and come back intact.
- Poisoned prompts don’t move your AI: it keeps to the asker’s own data, treats pasted and fetched text as data, and asks before it acts.
- Malformed JSON gets a clear error, never a crash or a hang, and your AI’s structured answers still match their schema.
- Your MCP server refuses calls it should refuse.
Every test signs in as a test account that sees only made-up data, never as a person. You get a grade and plain fixes, and an alert only when something that passed starts failing. On the free plan the report lists each test it didn’t run, so you can see what you’d get.
Agents can use it too
An MCP server, a REST API and plain-Markdown docs (llms.txt), so your coding agent can add the checks for you.
Seen on a real app
How TaskOS is checked: its chat, its MCP server, its uploads and scanners, its jobs and mail.