Mockserver runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 3 Nov 2026.
Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
We read the source, 5 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
system(juice_cmd)
<button id="button_chaos_connection_drop" class="accordion">drop ~50% of connections without a response</button>
tarProcess.Start();
result = subprocess.run(
var partialPath = path.join(directory, entry);
ProcessBuilder processBuilder = new ProcessBuilder(command);
Object readObject = pemParser.readObject();
$process = proc_open(
--privileged \
"base64Bytes": "iVBORw0KGgoAAAANSUhEUgAAAqwAAAApCAIAAAB/QuwlAAAK+GlDQ1BJQ0MgUHJvZmlsZQAASA2tl3dcU8kWx+fe9EYLICAl9CZIr9JrAAXpYCMkgYQSYgoCVpTFFVwLKiKgrugiiIJrAWQtiAULoljAvkEWFXVdLIiKypvAEvfzPm//e5PP3Pne35w598zcmXzOBYBGZQmFWagKANkCiSg6xJ+RmJTMIDwGWKAF8EAf2LHYYqFfVFQE+Nfy…
# run MockServer as root USER root # -XX:MaxRAMPercentage=45.0 caps the JVM heap at 45% of the container memory limit so the in-memory # request/expectation rings size off a bounded heap. The rest is not slack: under load ZGC grows # to its full heap in memory the kernel cannot…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Zero-dependency verifiable-claims MCP: validate safely, verify with allow_execution, self-test.
Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.
Debug and develop MCP servers with hot-swapping, session recording, and playback testing
Webhook, email, WebSocket and tunnel testing for AI agents: capture, wait, verify, replay.
Read-only lookup of tested agent tools and MCP servers: scores, test evidence, deprecation.
Record how any CLI behaves and check that a rewrite behaves the same (golden tests).
MCP server for regex testing, matching, replacing, and validation
Debugging experiments for coding agents: reproduce failures and verify fixes with test evidence.
Answers built from our own checks of this server.