Safe, audited PostgreSQL operations for AI agents: queries, migrations, EXPLAIN, containers
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.
PGOPS_DSNAPI keyrequiredPostgreSQL connection string for the database to operate on.
PGOPS_READONLY_DSNAPI keyoptionalOptional separate DSN for the read-only pool. Use a role with no write grants to enforce read-only at the database rather than only in the server.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball 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”.
Safe, audited PostgreSQL operations for AI agents: queries, migrations, EXPLAIN, containers
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.