# ResiliReplay (npm · resilireplay)

Run bounded, deterministic MCP reliability tests and generate executable regressions.

- Trust score: 87/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `resilireplay`: 87/100 (this document), [markdown](https://verifymcp.io/servers/aliengineering-byte-resilireplay/resilireplay.md), [page](https://verifymcp.io/servers/aliengineering-byte-resilireplay/resilireplay)

## Channel facts

- Registry: `npm`
- Package: `resilireplay`
- Version: `0.7.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to aliengineering-byte/resilireplay).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 16 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 321 tokens (~29/item across 11 items; 10 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ResiliReplay MCP server?

ResiliReplay runs locally as an npm package, launched with npx -y resilireplay. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add aliengineering-byte-resilireplay -- npx -y resilireplay
```

### Cursor

```json
{
  "mcpServers": {
    "aliengineering-byte-resilireplay": {
      "command": "npx",
      "args": [
        "-y",
        "resilireplay"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "aliengineering-byte-resilireplay": {
      "command": "npx",
      "args": [
        "-y",
        "resilireplay"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add aliengineering-byte-resilireplay -- npx -y resilireplay
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aliengineering-byte-resilireplay": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "resilireplay"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aliengineering-byte-resilireplay --command npx --arg -y --arg resilireplay
```

### Hermes

```yaml
mcp_servers:
  aliengineering-byte-resilireplay:
    command: "npx"
    args: ["-y", "resilireplay"]
```

### Netclaw

```json
{
  "McpServers": {
    "aliengineering-byte-resilireplay": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "resilireplay"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add aliengineering-byte-resilireplay -t stdio -c npx -a -y resilireplay
```

### Other

```json
{
  "mcpServers": {
    "aliengineering-byte-resilireplay": {
      "command": "npx",
      "args": [
        "-y",
        "resilireplay"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 83, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-05 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-04 (score 64)

First indexed and scored.

## MCP tools (10)

### `resilireplay_status` (~19 tokens)

ResiliReplay status

Report the local version and passive capture state.

### `resilireplay_list_faults` (~21 tokens)

List faults

List deterministic fault types without executing a target.

### `resilireplay_inspect_config` (~41 tokens)

Inspect an MCP configuration

Return a sanitized, value-free execution plan for one project-local MCP server.

Input parameters:

- `path` (string, required)
- `server` (string)

### `resilireplay_validate_campaign` (~32 tokens)

Validate a campaign

Validate a project-local campaign and return its confirmation hash without running it.

Input parameters:

- `path` (string, required)

### `resilireplay_verify_evidence` (~37 tokens)

Verify ResiliReplay evidence

Fail closed unless project-local campaign or MCP demo evidence has a valid schema and integrity hash.

Input parameters:

- `path` (string, required)

### `resilireplay_capture_start` (~23 tokens)

Arm passive capture

Explicitly arm bounded, sanitized, project-local passive capture.

### `resilireplay_capture_stop` (~18 tokens)

Stop passive capture

Stop passive capture without deleting evidence.

### `resilireplay_last_failure` (~21 tokens)

Summarize last failure

Return the last bounded, sanitized supported failure evidence.

### `resilireplay_generate_regression` (~42 tokens)

Generate a regression

Write an executable regression only when the caller confirms the exact evidence hash.

Input parameters:

- `confirmedEvidenceId` (string, required)
- `output` (string)

### `resilireplay_run_campaign` (~53 tokens)

Run a confirmed campaign

Run only a campaign whose exact reviewed hash is supplied; target calls retain campaign allowlists.

Input parameters:

- `allowRemote` (boolean)
- `confirmedCampaignHash` (string, required)
- `path` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/aliengineering-byte-resilireplay/resilireplay#diagnostics

## Score history

- 2026-09-21: 87
- 2026-09-20: 87
- 2026-09-19: 86
- 2026-09-18: 86
- 2026-09-17: 85
- 2026-09-16: 85
- 2026-09-15: 85
- 2026-09-14: 84
- 2026-09-13: 84
- 2026-09-12: 83
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 79
- 2026-09-08: 79
- 2026-09-07: 79
- 2026-09-06: 79
- 2026-09-05: 79
- 2026-09-04: 64

## Common questions

### What is the ResiliReplay MCP server?

ResiliReplay is an MCP server listed in the public MCP registry as io.github.aliengineering-byte/resilireplay. Run bounded, deterministic MCP reliability tests and generate executable regressions. This page covers its npm package (resilireplay).

### Is the ResiliReplay MCP server safe to use?

ResiliReplay scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ResiliReplay MCP server expose?

ResiliReplay exposes 10 tools: resilireplay_status, resilireplay_list_faults, resilireplay_inspect_config, resilireplay_validate_campaign, resilireplay_verify_evidence, and 5 more. Their descriptions and schemas cost roughly 307 tokens of context every time the server is loaded.

### Is the ResiliReplay MCP server still maintained?

ResiliReplay is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the ResiliReplay MCP server under?

ResiliReplay declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/resilireplay
- Socket report: https://socket.dev/npm/package/resilireplay
- Repository: https://github.com/aliengineering-byte/resilireplay
- Website: https://aliengineering-byte.github.io/resilireplay/
- Changelog RSS feed: https://verifymcp.io/servers/aliengineering-byte-resilireplay/resilireplay.xml
- Changelog JSON feed: https://verifymcp.io/servers/aliengineering-byte-resilireplay/resilireplay.json
- HTML version of this page: https://verifymcp.io/servers/aliengineering-byte-resilireplay/resilireplay