mcp-dbwatch@0.2.0
VERIFIED· not startedPublisher claims: "Enables on-call database diagnostics: it classifies load pressure, traces root causes with hypothesis-evidence-confidence, detects blocking and lock chains, scores health across a dimension tree, and renders deliverable incident reports. Works from symptom text alone with no database connection or history required (Tier0), escalating to snapshot-based and trend-based analysis as observations accumulate." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
"lock": "先看谁阻塞谁（analyze_lock），再决定 kill 谁。kill 前必须评估回滚耗时",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.res.warn("kill 阻塞源之前必须评估回滚耗时：大事务回滚可能比继续等待更糟")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.f"{'★ 回滚可能耗时数倍于已执行时间，kill 前务必评估' if (rows_modified or 0) > 100000 else '影响面可控，可在确认后 kill'}"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""锁等待链：谁阻塞谁。**kill 前必须评估回滚耗时**"""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.