Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Turnback

NPM · TURNBACK · SCANNED OCT 2

Undo a coding agent turn, including shell commands and untracked files.

Available components

npm · turnback 81
81 Trust /100
Trust breakdown (7 categories)

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 MFaizR77/turnback). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 880 tokens (~67/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 61% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Turnback MCP server?

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

npm · turnback

# add to Claude Code
claude mcp add mfaizr77-turnback -- npx -y turnback
// .cursor/mcp.json
{
  "mcpServers": {
    "mfaizr77-turnback": {
      "command": "npx",
      "args": [
        "-y",
        "turnback"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mfaizr77-turnback": {
      "command": "npx",
      "args": [
        "-y",
        "turnback"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mfaizr77-turnback -- npx -y turnback
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mfaizr77-turnback": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "turnback"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mfaizr77-turnback --command npx --arg -y --arg turnback
# ~/.hermes/config.yaml
mcp_servers:
  mfaizr77-turnback:
    command: "npx"
    args: ["-y", "turnback"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mfaizr77-turnback": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "turnback"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mfaizr77-turnback -t stdio -c npx -a -y turnback
// mcp.json
{
  "mcpServers": {
    "mfaizr77-turnback": {
      "command": "npx",
      "args": [
        "-y",
        "turnback"
      ]
    }
  }
}
Changelog

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.

  • 2 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 1 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.8.0 → 0.9.0 functional
  • 30 Sept 26 +12
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: MFaizR77/turnback security
    • Schema quality: 53 → 65 ▼ functional
    • Schema quality: 53 → 60 ▼ functional
    • Dependency health: 1.00 → unverified ▼ functional
    • Tool coverage: 50% → 61% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Security disclosure: fail → pass ▲ functional
    • Dependency health: 1.00 → pass functional
    • Package version: 0.1.0 → 0.8.0 functional
    • Package version: 0.1.0 → 0.7.0 functional
    • Package version: 0.1.0 → 0.6.0 functional
    • Package version: 0.1.0 → 0.5.0 functional
    • Package version: 0.1.0 → 0.4.0 functional
  • 29 Sept 26 53

    First indexed and scored.

Diagnostics

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 2 Oct 2026 · Analysed npm/turnback@0.9.0

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 MFaizR77/turnback
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/MFaizR77/turnback/.github/workflows/publish.yml@refs/tags/v0.9.0
Rekor log index 3036235770
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:94b9ffd6bb05b949eff00df76545b139174c302ef2a5dd18f8bed974211eff504b4b1356d7b149e47cbc6950470fb7dd33c76151a9c2864fd3982bbe4

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~880 tokens

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 →

Tool Tokens
blame_file ~101

For each line of a text file: the turn that last wrote it (agent, time, prompt), "before" Turnback started recording, or "outside" a turn (changed between turns)

NameTypeReqDescription
endinteger–Last line to include
pathstringyesFile, relative to the workspace or absolute
startinteger–First line to include
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

compare_turns ~68

Compare the results of two turns: files changed only by one, by both with different or identical results, and the diff from A to B

NameTypeReqDescription
astringyes–
bstringyes–
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

diff_range ~105

Show what changed from a turn start, mark, or snapshot ref to another point or to the current files (default). Use it to review your own work before saying a task is done.

NameTypeReqDescription
fromstringyesTurn ID (its start), mark label, or snapshot ref
patchboolean––
tostring–Same forms as from; defaults to the current files
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

diff_turn ~45

Show changes made during a turn

NameTypeReqDescription
patchboolean––
turnstringyes–
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

file_history ~54

List the turns that changed a file or folder, newest first

NameTypeReqDescription
pathstringyesFile or folder, relative to the workspace or absolute
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

list_turns ~40

List recorded agent turns, newest first

NameTypeReqDescription
limitinteger––
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

recover_file ~109

Find the newest snapshot holding a version of one file or folder that differs from disk (for a deleted file, the last one that had it). For a folder, paths lists only its files that are missing or different; files added since are left alone. Nothing is written: pass the returned target and paths to restore to bring it back.

NameTypeReqDescription
pathstringyesFile or folder, relative to the workspace or absolute
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

redo ~73

Preview or undo the last restore. Call once for a plan, then again with confirm_token as token.

NameTypeReqDescription
pathsarray––
targetstring–Turn id or snapshot ref (restore only)
tokenstring––
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

restore ~89

Preview or restore workspace files to a turn baseline or a snapshot ref (for example a step ref from turn_steps). Call once for a plan, then again with confirm_token as token.

NameTypeReqDescription
pathsarray––
targetstring–Turn id or snapshot ref (restore only)
tokenstring––
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

search_turns ~54

Find turns whose prompt, shell commands, or edited paths contain the text

NameTypeReqDescription
limitinteger––
querystringyes–
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

session_report ~55

Markdown report of one agent session: each turn's prompt, commands, and changed files. Defaults to the latest session.

NameTypeReqDescription
sessionstring––
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

status ~31

Show Turnback storage and protection status

NameTypeReqDescription
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

turn_steps ~56

List the edit and shell steps of a turn. Pass a step ref as restore target to return to just before that step.

NameTypeReqDescription
turnstringyes–
workspacestring–Workspace folder; defaults to the server working directory

No output schema declared.

No examples provided.

Common questions

What is the Turnback MCP server?

Turnback is an MCP server listed in the public MCP registry as io.github.MFaizR77/turnback. Undo a coding agent turn, including shell commands and untracked files. This page covers its npm package (turnback).

Is the Turnback MCP server safe to use?

Turnback scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 2 October 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 Turnback MCP server expose?

Turnback exposes 13 tools: list_turns, diff_turn, turn_steps, file_history, blame_file, and 8 more. Their descriptions and schemas cost roughly 880 tokens of context every time the server is loaded.

Is the Turnback MCP server still maintained?

Turnback is still listed as active in the MCP registry. We last reached this channel on 2 October 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 Turnback MCP server under?

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