orcareplay

MCPattested
v0.4.0io.github.Continuum-AI-CorpUnknownUpdated 14d agonpmGitHub

Read, replay and fork recorded coding-agent runs.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
259GitHub stars
64Forks
14d agoLast update
Package
Authorio.github.Continuum-AI-Corp
LicenseUnknown
Version0.4.0
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 2a1311c
Dependencies✓ 17 resolved · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv0.2.3 · 26d agoHow well does this scan work?
EvalsNone
IndexedSep 8, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagev0.2.3 · 26d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

orca_list_runsList every agent run recorded in this project, newest first, with the run it was forked

List every agent run recorded in this project, newest first, with the run it was forked

No input schema was published for this tool.

orca_show_runThe full timeline of one run: every model turn with its token counts and stop reason,

The full timeline of one run: every model turn with its token counts and stop reason,

No input schema was published for this tool.

orca_checkpointsThe points in a run a fork can start from — where the conversation prefix is complete and

The points in a run a fork can start from — where the conversation prefix is complete and

No input schema was published for this tool.

orca_graphWhat caused what in a run, as a list of edges. Each edge says which event produced which,

What caused what in a run, as a list of edges. Each edge says which event produced which,

No input schema was published for this tool.

orca_replayRe-run a recording exactly, with the network blocked and no tokens spent, and report what

Re-run a recording exactly, with the network blocked and no tokens spent, and report what

No input schema was published for this tool.

orca_compareFork one recorded run onto several models from the same checkpoint — same files, same

Fork one recorded run onto several models from the same checkpoint — same files, same

No input schema was published for this tool.

6 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Read, replay and fork recorded coding-agent runs.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-09 — observed resolution, not a publisher declaration.

17 packages resolved · 10 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.