Is PostgreSQL MCP Server safe to use?

PostgreSQL MCP Server has an HVTrust score of 59.3/100 (Grade C), ranked #652 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for PostgreSQL MCP Server?

PostgreSQL MCP Server scores 59.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 12 GitHub stars and is categorized under MCP Servers.

PostgreSQL MCP Server

neverinfamous/postgres-mcp

Secure PostgreSQL Administration & Observability with Code Mode— True V8 Isolate Sandbox Replacing 278 Specialized Tools for up to 90% Token Savings. Includes Tool Filtering, Payload Optimization, HTTP/SSE, OAuth 2.1, Audit & Token Logging, Deterministic Error Handling, Support for 12 Extensions…

MCP Servers TypeScript Listed MIT

Is PostgreSQL MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.6 / 10

Provenance None

Signed commits 85%

Last push 5d ago

Compare PostgreSQL MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: PostgreSQL MCP Server scores 59.3/100 (Grade C), ranked #652 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.6/10; 85% of recent commits are signed; last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How PostgreSQL MCP Server compares in MCP Servers

#360 Buildkite MCP Server 59.5 +0.2
#361 Laravel MCP Companion 59.4 +0.1
#362 PostgreSQL MCP Server 59.3 this agent
#363 Autotask 59.3 ±0
#364 Drawio MCP 59.2 −0.1

Bars show each HVTrust score; the tick marks PostgreSQL MCP Server’s 59.3.

Where the 59.3 comes from

HVTrust dimensions vs the MCP Servers average

59.3 / 100 · 100.0% confidence

PostgreSQL MCP Server MCP Servers average (775 agents)

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

12.5 / 25

2.2 above 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

14.1 / 17

1.9 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.1 / 20

1.0 above avg 12.1

AdoptionLog-scaled stars · package downloads

8.7 / 20

1.5 above 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 rose 181 spots (#832 → #651)

2026-09-25

HVTrust Changed

HVTrust up 5.9pts (53.4 → 59.3)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.6/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 PostgreSQL MCP Server View MCP Servers Report missing data

42.6

Activity sub-score · out of 100

#362

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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-21

5 days ago

Commits (4 wk)

Downloads (7d)

31,012

docker

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #651

Analysis

Activity Inputs

42.6 / 100

StarsRepository reach

6.7 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

8.7 / 25

CommunityFork signal

2.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.6 / 10

OpenSSF Scorecard · scanned Sep 16, 2026

Signed Commits

85%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review -1

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 8

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about PostgreSQL MCP Server

PostgreSQL MCP Server 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 PostgreSQL MCP Server publish package provenance?

No published build provenance is currently detected for PostgreSQL MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does PostgreSQL MCP Server have an OpenSSF Scorecard?

PostgreSQL MCP Server has an OpenSSF Scorecard score of 6.6/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 PostgreSQL MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 5 day(s).

What license does PostgreSQL MCP Server use?

PostgreSQL MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are PostgreSQL MCP Server's commits signed?

85% of the last 100 commits to PostgreSQL MCP Server 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

PostgreSQL MCP Server 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.

Postgres

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Extensions

Extension based plugin/integration surface detected.

database

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 PostgreSQL MCP Server'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 → extension-based

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain PostgreSQL MCP Server?

For maintainers

HVTrust scores PostgreSQL MCP Server 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-25

Rank Moved

Rank rose 181 spots (#832 → #651)

2026-09-25

HVTrust Changed

HVTrust up 5.9pts (53.4 → 59.3)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

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

HVTrust Changed

HVTrust up 25.3pts (28.2 → 53.5)

2026-09-22

Newly Listed

First tracked at rank #833

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Grade Changed

Trust grade D → C

2026-09-19

Rank Moved

Rank rose 396 spots (#1232 → #836)

2026-09-19

HVTrust Changed

HVTrust up 17.7pts (35.5 → 53.2)

2026-09-18

Grade Changed

Trust grade C → D

2026-09-18

Rank Moved

Rank dropped 403 spots (#829 → #1232)

2026-09-18

HVTrust Changed

HVTrust down 17.8pts (53.3 → 35.5)

2026-09-14

Rank Moved

Rank rose 18 spots (#835 → #817)

2026-09-12

Rank Moved

Rank rose 24 spots (#856 → #832)

2026-09-11

Rank Moved

Rank dropped 13 spots (#843 → #856)

2026-09-09

Rank Moved

Rank dropped 21 spots (#820 → #841)

2026-09-07

Grade Changed

Trust grade D → C

2026-09-07

Rank Moved

Rank rose 388 spots (#1201 → #813)

2026-09-07

HVTrust Changed

HVTrust up 17.9pts (34.7 → 52.6)

2026-09-06

Scorecard Added

OSSF Scorecard: 6.1/10

2026-09-06

Rank Moved

Rank rose 101 spots (#1302 → #1201)

2026-09-06

HVTrust Changed

HVTrust up 15.0pts (19.7 → 34.7)

2026-09-03

Rank Moved

Rank dropped 11 spots (#1277 → #1288)

2026-09-02

Rank Moved

Rank dropped 24 spots (#1253 → #1277)

2026-09-01

Rank Moved

Rank dropped 19 spots (#1234 → #1253)

2026-08-31

Rank Moved

Rank dropped 10 spots (#1224 → #1234)

2026-08-30

Rank Moved

Rank dropped 17 spots (#1207 → #1224)

2026-08-29

Rank Moved

Rank dropped 21 spots (#1186 → #1207)

2026-08-28

Rank Moved

Rank dropped 22 spots (#1164 → #1186)

2026-08-27

Rank Moved

Rank dropped 13 spots (#1151 → #1164)

2026-08-26

Rank Moved

Rank dropped 57 spots (#1094 → #1151)

2026-08-19

Rank Moved

Rank dropped 10 spots (#1087 → #1097)

2026-08-17

Rank Moved

Rank rose 28 spots (#1110 → #1082)

2026-08-16

Rank Moved

Rank dropped 28 spots (#1082 → #1110)

2026-08-10

Rank Moved

Rank dropped 41 spots (#1031 → #1072)

2026-08-08

Newly Listed

First tracked at rank #1021

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/postgresql-mcp-server.svg)](https://hvtracker.net/agents/postgresql-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/postgresql-mcp-server"><img src="https://hvtracker.net/badge/postgresql-mcp-server.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