Reelier
NPM · REELIER
Snapshot tests and CI for agent workflows: record a run, replay it at 0 tokens, diff for drift.
Available components
Last scanned (4 hours ago)
Scores higher than 65% 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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 70 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1095 tokens (~219/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 5 Nov 26 −3
- Stability: pass → 0.77 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 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.
- 12 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.
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/reelier@0.24.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
reelier_diff ~228
Compare two runs of the same skill and report SAME or DRIFTED — the drift-detector for a recorded baseline replayed on a schedule. Compares per-step outcomes, structure, and heal-level from .reelier/runs/<skill>.jsonl (defaults to the last two runs); data values that legitimately change run-to-run are NOT drift. Drifted steps carry why (the failing assertion). To check a MODEL upgrade: re-record the workflow with the new model, then diff against your frozen baseline — replaying a pinned skill can't reveal model changes (replay never calls a model). Honest when there aren't two runs yet.
| Name | Type | Req | Description |
|---|---|---|---|
| baselineIndex | number | – | 0-based index of the baseline run (default: second-to-last). |
| candidateIndex | number | – | 0-based index of the candidate run (default: the last run). |
| cwd | string | – | Working directory where .reelier/ lives (default: process cwd). |
| skill | string | yes | Skill name (the .reelier/runs/<skill>.jsonl stem) whose runs to compare. |
No output schema declared.
No examples provided.
reelier_from_session ~223
Compile a SKILL.md from a session transcript. USE WHEN: the work ALREADY happened (this session or by hand) — recording can't be retroactive. NOT for work that hasn't happened yet (record that live via the reelier mcp proxy). Get the transcriptPath from reelier_scan first. Returns the written skill's path, stats, and open questions — or, honestly, that nothing in the transcript was replayable. If the workflow used a relative time window ("this week"), bind it to a date variable (e.g. {{today-7d}}) so later replays pull the CURRENT window, not a frozen one — the openQuestions output flags this.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Overwrite an existing file at the output path. |
| name | string | – | Skill name (also the default output filename stem). |
| out | string | – | Output path for the compiled SKILL.md (default: <cwd>/<name>.skill.md). |
| transcriptPath | string | yes | Path to a session transcript (.jsonl) to compile. |
No output schema declared.
No examples provided.
reelier_push ~201
Push a skill's local run records (and, on first push, the skill file) to your receipt ledger, where each receipt gets a shareable permalink + verified-replay badge. Requires an apiKey — from `reelier login` (or REELIER_CLOUD_KEY in env) — reports skipped-no-key honestly when absent; the cloud URL always resolves on its own. USE WHEN: a run's receipt should be durable or shareable.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Ignore/reset the cursor — reconsider every record from the start. |
| cwd | string | – | Working directory to resolve .reelier/ state under (default: process cwd). |
| dryRun | boolean | – | Report what would push; make no network calls, touch no state. |
| skillPath | string | yes | Path to a .skill.md file whose run records should be pushed. |
| withSkill | boolean | – | Upload the skill file even if it was already uploaded before. |
No output schema declared.
No examples provided.
reelier_replay ~336
Run a skill file at Level 0 (deterministic replay, zero LLM calls) and return the real run record: per-step outcomes, timing, totals, and — when a step drifted — why (the failing assertion). Never fabricates a pass. Reproduces the recorded TOOL CALLS (MCP/HTTP) only — no LLM reasoning or prose step re-runs. It does NOT schedule itself: pair with cron/CI for recurring runs. Pass vars to fill {{templated}} inputs (e.g. a computed date window) so a replay pulls current data. READ-ONLY by default: 'idempotent-write' steps are held back (reported as a refused/failed step) unless you pass allowWrites — so replaying never re-fires a write.
| Name | Type | Req | Description |
|---|---|---|---|
| allowDestructive | boolean | – | Allow steps whose effect is 'destructive' to run. |
| allowWrites | boolean | – | Allow 'idempotent-write' steps to execute. Default false — replay is READ-ONLY, so re-running never re-fires writes. |
| cwd | string | – | Working directory the run record is written under (default: process cwd). |
| skillPath | string | yes | Path to a .skill.md file to run. |
| vars | object | – | Template variable bindings ({{name}} -> value) — e.g. a computed date window so a relative-date skill replays against the current period, not a frozen one. |
| wrap | array | – | Downstream MCP server command line(s) to connect for MCP-tool steps (same shape as the CLI's --wrap). |
No output schema declared.
No examples provided.
reelier_scan ~107
Discover replayable workflows in an agent's session history (defaults to ~/.claude/projects). Returns each session's transcript path — feed one to reelier_from_session. Only MCP/HTTP tool-call sequences are replayable; native file/shell actions are reported as skipped, never fabricated into a fake result. USE WHEN: deciding which past work is worth compiling into a replayable skill.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Directory to scan for agent session transcripts (default: ~/.claude/projects). |
No output schema declared.
No examples provided.
How do I install the Reelier MCP server?
Reelier runs locally as an npm package, launched with npx -y reelier. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · reelier
claude mcp add seldonframe-reelier -- npx -y reelier
What is the Reelier MCP server?
Reelier is an MCP server listed in the public MCP registry as io.github.seldonframe/reelier. Snapshot tests and CI for agent workflows: record a run, replay it at 0 tokens, diff for drift. This page covers its npm package (reelier).
Is the Reelier MCP server safe to use?
Reelier scores 80 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. 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 Reelier MCP server expose?
Reelier exposes 5 tools: reelier_scan, reelier_from_session, reelier_replay, reelier_push, reelier_diff. Their descriptions and schemas cost roughly 1,095 tokens of context every time the server is loaded.
Is the Reelier MCP server still maintained?
Reelier 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 Reelier MCP server under?
Reelier declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.