updated 2026-11-10 04:07 UTC

Pgedge Postgres MCP

Repository Website

pgEdge MCP Server. A PostgreSQL MCP server with a Natural Language Agent CLI and Web UI.

MCP Servers Go Listed PostgreSQL

Is Pgedge Postgres MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 5.1 / 10
Provenance None
Signed commits 79%
Last push yesterday
Compare Pgedge Postgres MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Pgedge Postgres MCP scores 54.6/100 (Grade C), ranked #862 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.1/10; 79% of recent commits are signed; last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Pgedge Postgres MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Pgedge Postgres MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/pgEdge/pgedge-postgres-mcp, PostgreSQL, last pushed 2026-11-09. 79% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.1/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:

    • Code Review6
    • Branch Protection4
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies7
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 6
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 7
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    Distributed as the container image ghcr.io/pgedge/postgres-mcp:latest; HVTracker doesn't check that registry's source link yet.

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 5.8/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Pgedge Postgres MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Pgedge Postgres MCP compares in MCP Servers

  1. #475 DexPaprika 54.7 +0.1
  2. #476 Maven Tools MCP 54.7 +0.1
  3. #477 Pgedge Postgres MCP 54.6 this agent
  4. #478 Rust MCP Sdk 54.6 ±0
  5. #479 Git MCP Server 54.6 ±0

Bars show each HVTrust score; the tick marks Pgedge Postgres MCP’s 54.6.

Where the 54.6 comes from

HVTrust dimensions vs the MCP Servers average

54.6 / 100 · 100.0% confidence

Pgedge Postgres MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.3 / 25
in line with avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
13.3 / 20
1.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
5.7 / 20
1.9 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-05
Rank Moved
Rank rose 39 spots (#901 → #862)
2026-11-05
Activity Score Changed
Activity score up 5pts (49 → 54)
2026-11-03
Rank Moved
Rank rose 12 spots (#911 → #899)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent
View MCP Servers Report missing data
54.5
Activity sub-score · out of 100
#477
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
245
Forks
24
Last Push
2026-11-09
yesterday
Commits (4 wk)
4?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
5
Rank Change
▼1
was #861

Analysis

Activity Inputs

54.5 / 100
StarsRepository reach
14.3 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
6.5 / 20

Common questions about Pgedge Postgres MCP

Public trust evidence for Pgedge Postgres MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Pgedge Postgres MCP publish package provenance?
No published build provenance is currently detected for Pgedge Postgres MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Pgedge Postgres MCP have an OpenSSF Scorecard?
Pgedge Postgres MCP has an OpenSSF Scorecard score of 5.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Pgedge Postgres MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Pgedge Postgres MCP use?
Pgedge Postgres MCP ships under PostgreSQL. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Pgedge Postgres MCP's commits signed?
79% of the last 100 commits to Pgedge Postgres MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Pgedge Postgres MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Pgedge Postgres MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Pgedge Postgres MCP?

For maintainers

HVTrust scores Pgedge Postgres MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 39HVTrust 4Grade 4Scorecard 1Delisted 1Listed 1MCP 1Surface 1Surface 1Score 1
2026-11-05
Rank Moved
Rank rose 39 spots (#901 → #862)
2026-11-05
Activity Score Changed
Activity score up 5pts (49 → 54)
2026-11-03
Rank Moved
Rank rose 12 spots (#911 → #899)
2026-11-02
Rank Moved
Rank dropped 10 spots (#901 → #911)
2026-10-29
Rank Moved
Rank rose 26 spots (#923 → #897)
2026-10-28
Rank Moved
Rank dropped 27 spots (#896 → #923)
2026-10-26
Rank Moved
Rank dropped 10 spots (#888 → #898)
2026-10-24
Rank Moved
Rank dropped 28 spots (#864 → #892)
2026-10-23
Rank Moved
Rank rose 26 spots (#890 → #864)
2026-10-22
Rank Moved
Rank rose 15 spots (#905 → #890)
2026-10-18
Rank Moved
Rank rose 26 spots (#918 → #892)
2026-10-17
Rank Moved
Rank dropped 14 spots (#904 → #918)
2026-10-16
Rank Moved
Rank dropped 29 spots (#875 → #904)
2026-10-14
Rank Moved
Rank dropped 18 spots (#849 → #867)
2026-10-13
Rank Moved
Rank dropped 14 spots (#835 → #849)
2026-10-09
Rank Moved
Rank dropped 56 spots (#760 → #816)
2026-10-06
Rank Moved
Rank rose 38 spots (#795 → #757)
2026-10-02
Rank Moved
Rank dropped 13 spots (#766 → #779)
2026-09-25
Rank Moved
Rank dropped 95 spots (#665 → #760)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 85 spots (#742 → #657)
2026-09-23
HVTrust Changed
HVTrust up 28.8pts (30.1 → 58.9)
2026-09-22
Newly Listed
First tracked at rank #742
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-14
Rank Moved
Rank rose 13 spots (#642 → #629)
2026-09-12
Rank Moved
Rank dropped 13 spots (#628 → #641)
2026-09-11
Rank Moved
Rank dropped 24 spots (#604 → #628)
2026-09-10
Rank Moved
Rank dropped 10 spots (#594 → #604)
2026-09-09
Grade Changed
Trust grade D → C
2026-09-09
Rank Moved
Rank rose 540 spots (#1134 → #594)
2026-09-09
HVTrust Changed
HVTrust up 19.5pts (40.4 → 59.9)
2026-09-08
Grade Changed
Trust grade C → D
2026-09-08
Rank Moved
Rank dropped 549 spots (#585 → #1134)
2026-09-08
HVTrust Changed
HVTrust down 19.5pts (59.9 → 40.4)
2026-09-07
Rank Moved
Rank dropped 42 spots (#543 → #585)
2026-09-06
Rank Moved
Rank dropped 22 spots (#521 → #543)
2026-09-05
Rank Moved
Rank dropped 82 spots (#439 → #521)
2026-09-03
Rank Moved
Rank rose 10 spots (#442 → #432)
2026-09-02
Rank Moved
Rank dropped 19 spots (#423 → #442)
2026-09-01
Rank Moved
Rank dropped 11 spots (#412 → #423)
2026-08-31
Rank Moved
Rank dropped 30 spots (#382 → #412)
2026-08-30
Scorecard Added
OSSF Scorecard: 5.8/10
2026-08-30
Grade Changed
Trust grade D → C
2026-08-30
Rank Moved
Rank rose 679 spots (#1061 → #382)
2026-08-30
HVTrust Changed
HVTrust up 35.0pts (24.7 → 59.7)
2026-08-29
Rank Moved
Rank dropped 49 spots (#1012 → #1061)
2026-08-28
Rank Moved
Rank dropped 37 spots (#975 → #1012)
2026-08-27
Rank Moved
Rank dropped 25 spots (#950 → #975)
2026-08-26
Rank Moved
Rank dropped 106 spots (#844 → #950)
2026-08-17
Rank Moved
Rank rose 13 spots (#850 → #837)
2026-08-16
Rank Moved
Rank dropped 20 spots (#830 → #850)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.6 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/pgedge-postgres-mcp.svg)](https://hvtracker.net/agents/pgedge-postgres-mcp)
HTML:
<a href="https://hvtracker.net/agents/pgedge-postgres-mcp"><img src="https://hvtracker.net/badge/pgedge-postgres-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON