Is Pgedge Postgres MCP safe to use?

Pgedge Postgres MCP has an HVTrust score of 58.9/100 (Grade C), ranked #637 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Pgedge Postgres MCP?

Pgedge Postgres MCP scores 58.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 225 GitHub stars and is categorized under MCP Servers.

Pgedge Postgres MCP

pgEdge/pgedge-postgres-mcp

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

MCP Servers Go Grade C Listed PostgreSQL

58.9/100

Rank #637 of 1328

Compare Pgedge Postgres MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-10 · 3d ago

Recent change

Rank +10

Is Pgedge Postgres MCP safe? Pgedge Postgres MCP scores 58.9/100 (Grade C), ranked #637 of 1328 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; 65% of recent commits are signed; last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#351 MaverickMCP — 58.9 (C) → #352 Autotask — 58.9 (C) → #354 Apple Books — 58.8 (C) → #355 AgentPhone — 58.6 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

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)

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.

Compare with another agent Get email alerts for Pgedge Postgres MCP View MCP Servers Report missing data

61.5

Activity sub-score · out of 100

#353

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 →

Rank Trend

2026-08-11 2026-09-13

Activity & Reach

Stars

225

Forks

Last Push

2026-09-10

3 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲4

was #641

Analysis

HVTrust Dimensions vs MCP Servers

58.9 / 100 · 100.0% confidence

Pgedge Postgres MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

10.4 / 25

in line with avg 10.1

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.2 above avg 12.1

Maintenance60% last-push freshness · 40% commit activity

17.1 / 20

5.0 above avg 12.1

AdoptionLog-scaled stars · package downloads

5.6 / 20

1.4 below avg 7.0

Activity Inputs

61.5 / 100

StarsRepository reach

14.1 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

16.5 / 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 9, 2026

Signed Commits

65%

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

Is Pgedge Postgres MCP safe?

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 3 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?

65% 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.

Anthropic

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

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

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

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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