ResiliReplay runs on your own machine — the client starts it, so there is no endpoint to ping. 23 installs a week from npm. Last commit 4 Sep 2026.
Run bounded, deterministic MCP reliability tests and generate executable regressions.
We read the source, 5 d 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.
const execution = spawnSync(process.execPath, ["--test", regression.testPath], {
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
/(?:bearer\s+[a-z0-9._~+/=-]+|basic\s+[a-z0-9+/=]+|(?:gh[pousr]|sk)(?:-|%2d)[a-z0-9_-]{12,}|AKIA[A-Z0-9]{16}|base64:[a-z0-9+/]{20,}={0,2}|(?:api[-_]?key|token|secret|password|authorization)\s*[=:]\s*(?:bearer\s+|basic\s+)?[^\s,;]+)/giu;
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.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add resilireplay -- npx -y resilireplay
{
"mcpServers": {
"resilireplay": {
"command": "npx",
"args": [
"-y",
"resilireplay"
]
}
}
}
[mcp_servers.resilireplay]
command = "npx"
args = ["-y", "resilireplay"]
{
"mcpServers": {
"resilireplay": {
"command": "npx",
"args": [
"-y",
"resilireplay"
]
}
}
}
{
"servers": {
"resilireplay": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"resilireplay"
]
}
}
}
Test, explain, and generate regular expressions
3rd Generation Testing (3TG) — generate deterministic test suites from Markdown spec tables via MCP.
Deterministic eligibility decisions and test-driven rule authoring via the Aethis developer API.
Deterministic HTTP/WebSocket testing and policy-gated API execution for AI agents.
Deterministic fault-injection server for testing how MCP clients handle failures and recover.
Moderated usability testing: read sessions, notes, transcripts, reports, and draft test scenarios.
Local, deterministic review of Git changes: weakened tests and CI gates, risky flows, blast radius.
Complete Resend email MCP: full API coverage + debug layer (deliverability, DNS, bounces).
Answers built from our own checks of this server.