psql-mcp@0.1.0
CAUTION· static onlyPublisher claims: "Hardened, read-only Postgres MCP server with credential isolation" Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
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
- nothing has run yet
- What we could not test
- everything: the server has not run yet
Run it before you trust it. Nothing has run yet: the code was read, the server was not. `vet-skills try` runs this exact version in the honeypot in about a minute.
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 analysed it statically (a sandbox run is pending) on 2026-11-15 and scored it 62/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
# set -a; . "$(dirname "$0")/../../.env.development.local"; set +aFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# A cap-kill or early psql exit closes the pipe mid-write; thatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# A non-zero code from our own cap-kill is expected noise; only surface realFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.kill reaches ``psql`` itself, not just a wrapping ``bash``. Output from bothFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."SELECT pg_read_file('/etc/passwd')",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.r"SELECT 1; \! cat /etc/passwd", # meta-command mid-lineFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for psql-mcp@0.1.0 as of 22 min ago. This is the package itself, not its dependencies.
What would make this Verified
18 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim maxswjeon: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.