debug-recorder-mcp

MCPattested
v1.1.3io.github.oaslanankaUnknownUpdated 2mo agonpmGitHub

Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.

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.
2mo agoLast update
Package
Authorio.github.oaslananka
LicenseUnknown
Version1.1.3
Sourcenpm+mcp-registry
npmdebug-recorder-mcp
GitHuboaslananka/debug-recorder-mcp
SBOMCycloneDX 1.6 ↓
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 · 74abd4e
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface18 tools · 3 privileged
Security scan✓ Cleanv1.1.3 · 2mo agoHow well does this scan work?
EvalsNone
IndexedJul 7, 2026

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

Tools

18 tools · 3 privileged
Statically extracted from the published packagev1.1.3 · 2mo 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.

start_debug_sessionNo description published

This tool published no description. Forge does not invent one.

add_fixNo description published

This tool published no description. Forge does not invent one.

record_commandprivilegedNo description published

This tool published no description. Forge does not invent one.

close_sessionNo description published

This tool published no description. Forge does not invent one.

search_sessionsNo description published

This tool published no description. Forge does not invent one.

save_search_presetNo description published

This tool published no description. Forge does not invent one.

list_search_presetsNo description published

This tool published no description. Forge does not invent one.

remove_search_presetprivilegedNo description published

This tool published no description. Forge does not invent one.

find_similar_errorsNo description published

This tool published no description. Forge does not invent one.

get_sessionNo description published

This tool published no description. Forge does not invent one.

update_sessionNo description published

This tool published no description. Forge does not invent one.

delete_sessionprivilegedNo description published

This tool published no description. Forge does not invent one.

list_sessionsNo description published

This tool published no description. Forge does not invent one.

get_statsNo description published

This tool published no description. Forge does not invent one.

get_diagnosticsNo description published

This tool published no description. Forge does not invent one.

export_sessionsNo description published

This tool published no description. Forge does not invent one.

import_sessionsNo description published

This tool published no description. Forge does not invent one.

get_session_contextNo description published

This tool published no description. Forge does not invent one.

0 of 18 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

Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

18 tools · 3 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.