io.github.pgEdge/postgres-mcp

Name: io.github.pgEdge/postgres-mcp
Rating: 60 (1 reviews)
Author: io.github.pgEdge

MCPcommunity

v1.0.0io.github.pgEdgeUnknownUpdated 5mo agoGitHub

Enterprise PostgreSQL MCP server with NL queries, hybrid search (pgvector+BM25), and web UI

About the pgEdge Postgres MCP Server pgEdge Postgres MCP Server Choosing the Right Solution Best Practices - Querying the Server Installing the MCP Server Quickstart Demo with Northwind Deploying from Source Testing the MCP Server Deployment Configuring the MCP Server Specifying Configuration Preferences Using Environment Variables to Specify Options Including Provider Embeddings in a…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

5mo agoLast update

Package

Authorio.github.pgEdge

LicenseUnknown

Version1.0.0

Sourcemcp-registry

GitHubpgEdge/pgedge-postgres-mcp

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ 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>" }

—CVE scan · not run+0/30

→ Not yet scanned — package must be on npm

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface—

Security scan✓ CleanvHEAD · 19d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp