ResiliReplay
NPM · RESILIREPLAY
Run bounded, deterministic MCP reliability tests and generate executable regressions.
Available components
Last scanned (11 hours ago)
Scores higher than 96% of npm servers
Category Testing and QA
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to aliengineering-byte/resilireplay). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 61 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 321 tokens (~29/item across 11 items; 10 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 0
- Stability: pass → 0.97 functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −2
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/resilireplay@0.7.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | aliengineering-byte/resilireplay |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/aliengineering-byte/resilireplay/.github/workflows/npm-publish.yml@refs/tags/v0.7.1 |
| Rekor log index | 2705755332 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:670d72010c6816f628374b65563613d3988c01500ce16ffa0dc83d12ef46ca323d5b9e225fca45e271eaab66004fb88b9f191729fe026320cdb8e0335 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
resilireplay_capture_start Arm passive capture ~23
Explicitly arm bounded, sanitized, project-local passive capture.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resilireplay_capture_stop Stop passive capture ~18
Stop passive capture without deleting evidence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resilireplay_generate_regression Generate a regression ~42
Write an executable regression only when the caller confirms the exact evidence hash.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmedEvidenceId | string | yes | – |
| output | string | – | – |
No output schema declared.
No examples provided.
resilireplay_inspect_config Inspect an MCP configuration ~41
Return a sanitized, value-free execution plan for one project-local MCP server.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| server | string | – | – |
No output schema declared.
No examples provided.
resilireplay_last_failure Summarize last failure ~21
Return the last bounded, sanitized supported failure evidence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resilireplay_list_faults List faults ~21
List deterministic fault types without executing a target.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resilireplay_run_campaign Run a confirmed campaign ~53
Run only a campaign whose exact reviewed hash is supplied; target calls retain campaign allowlists.
| Name | Type | Req | Description |
|---|---|---|---|
| allowRemote | boolean | – | – |
| confirmedCampaignHash | string | yes | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
resilireplay_status ResiliReplay status ~19
Report the local version and passive capture state.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resilireplay_validate_campaign Validate a campaign ~32
Validate a project-local campaign and return its confirmation hash without running it.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
resilireplay_verify_evidence Verify ResiliReplay evidence ~37
Fail closed unless project-local campaign or MCP demo evidence has a valid schema and integrity hash.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
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.
npm · resilireplay
claude mcp add aliengineering-byte-resilireplay -- npx -y resilireplay
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 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 5 November 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.