Pgedge Postgres MCP

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? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.7 / 10
Provenance None
Signed commits 66%
Last push 2d ago
Compare Pgedge Postgres MCP
Suggest a correction

In detail: Pgedge Postgres MCP scores 55.7/100 (Grade C), ranked #760 of 1325 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.7/10; 66% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How Pgedge Postgres MCP compares in MCP Servers

  1. #419 Git MCP Server 56.1 +0.4
  2. #420 Awesome Copilot MCP Server 55.8 +0.1
  3. #421 Pgedge Postgres MCP 55.7 this agent
  4. #422 Vibe Check MCP Server 55.7 ±0
  5. #423 Wc26 MCP 55.5 −0.2

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

Where the 55.7 comes from

HVTrust dimensions vs the MCP Servers average

55.7 / 100 · 100.0% confidence

Pgedge Postgres MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.4 / 25
in line with avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.1 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
13.8 / 20
1.7 above avg 12.1
AdoptionLog-scaled stars · package downloads
5.7 / 20
1.5 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.7/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.
57.3
Activity sub-score · out of 100
#421

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-09-26 06:32 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
230
Forks
22
Last Push
2026-09-24
2 days ago
Commits (4 wk)
8?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
4
Rank Change
=
was #760

Analysis

Activity Inputs

57.3 / 100
StarsRepository reach
14.2 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
6.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.7 / 10
OpenSSF Scorecard · scanned Sep 25, 2026
Signed Commits
66%
of last 100 commits verified
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 9

Common questions about Pgedge Postgres MCP

Pgedge Postgres MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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.7/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 2 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?
66% 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.

Reputation Timeline

Signal history
Rank 24HVTrust 4Grade 4Listed 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
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)
2026-08-12
Rank Moved
Rank rose 10 spots (#832 → #822)
2026-08-10
Rank Moved
Rank dropped 42 spots (#791 → #833)
2026-08-08
Newly Listed
First tracked at rank #788

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 55.7 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.3 · Raw JSON