mcp-postgres-server

MCPcommunity
v0.3.1io.github.antonorlovUnknownUpdated 21d agonpmGitHub

MCP server for PostgreSQL: local, Docker, RDS, Neon, Supabase, or behind an SSH bastion.

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
19GitHub stars
9Forks
21d agoLast update
Reads these credentials
  • DATABASE_URLAPI keyoptional

    Full connection string (preferred). Supports sslmode in the URL.

  • PG_PASSWORDAPI keyoptional

    Database password.

  • PG_SSH_PRIVATE_KEYAPI keyoptional

    Path to a private key file. If unset, auth falls back like ssh: a running agent (SSH_AUTH_SOCK), then a default key (~/.ssh/id_ed25519, id_rsa, id_ecdsa).

  • PG_SSH_PASSPHRASEAPI keyoptional

    Passphrase for the private key, if encrypted.

  • PG_SSH_PASSWORDAPI keyoptional

    SSH login password. Opt-in; a key or agent takes precedence. Prefer keys, a bastion often disables password auth.

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.

Package
Authorio.github.antonorlov
LicenseUnknown
Version0.3.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—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)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv0.3.1 · 20d agoHow well does this scan work?
EvalsNone
IndexedSep 15, 2026

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

Tools

6 tools · none privileged
Statically extracted from the published packagev0.3.1 · 20d 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.

queryNo description published

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

executeNo description published

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

list_schemasList every schema in the connected database. Start here when exploring an unfamiliar database, then call list_tables for the schema you care about.

List every schema in the connected database. Start here when exploring an unfamiliar database, then call list_tables for the schema you care about.

No input schema was published for this tool.

list_tablesList all tables in a schema (default: 'public'). Use this before querying tables you have not seen yet, then call describe_table for column details.

List all tables in a schema (default: 'public'). Use this before querying tables you have not seen yet, then call describe_table for column details.

No input schema was published for this tool.

describe_tableShow the structure of one table: column names, data types, nullability, defaults, and primary-key membership. Call this before writing non-trivial queries against a table.

Show the structure of one table: column names, data types, nullability, defaults, and primary-key membership. Call this before writing non-trivial queries against a table.

No input schema was published for this tool.

connect_dbSwitch the server to a different PostgreSQL database at runtime, replacing the current connection.

Switch the server to a different PostgreSQL database at runtime, replacing the current connection.

No input schema was published for this tool.

4 of 6 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

MCP server for PostgreSQL: local, Docker, RDS, Neon, Supabase, or behind an SSH bastion.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-15 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

69 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+57 more not listed. The counts by reason above cover all of them.

Not followed: optionalDependencies, peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in databases