MySQL change tracking with instant row-level recovery and forensic attribution for compliance.
Point-in-time recovery for MySQL — no locks, no schema changes, no waiting for a restore. — against production MySQL. That's the experience dbtrail makes possible. dbtrail tails the MySQL binary log and keeps every row change with full before/after images in a searchable index: See every change — what changed and when, for every row, with before → after diffs Undo precisely — generate exact…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 2 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Point-in-time recovery for MySQL — no locks, no schema changes, no waiting for a restore. — against production MySQL. That's the experience dbtrail makes possible. dbtrail tails the MySQL binary log and keeps every row change with full before/after images in a searchable index: See every change — what changed and when, for every row, with before → after diffs Undo precisely — generate exact reversal SQL for just the damaged rows Time-travel — query any row (or table) as it was at any moment…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.