Is PostgreSQL MCP Server safe to use?

PostgreSQL MCP Server has an HVTrust score of 19.8/100 (Grade D), ranked #1081 of 1283 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 19.8/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

MCP Servers TypeScript Grade D Listed MIT

19.8/100

Rank #1081 of 1283

Compare PostgreSQL MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade D · 1/5 signals

Last push

2026-08-10 · 2d ago

Recent change

Rank +1

Is PostgreSQL MCP Server safe? PostgreSQL MCP Server scores 19.8/100 (Grade D), ranked #1081 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 78% of recent commits are signed; last pushed 2026-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#596 Switzerland MCP 🇨🇭 — 19.9 (D) → #597 Hermes Atlas MCP — 19.9 (D) → #599 ConnectWise Manage — 19.8 (D) → #600 Context+ — 19.8 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 41 spots (#1031 → #1072)

2026-08-08

Newly Listed

First tracked at rank #1021

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

44.1

Activity sub-score · out of 100

#598

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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

Forks

Last Push

2026-08-10

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #1083

Analysis

HVTrust Dimensions vs MCP Servers

19.8 / 100 · 50.0% confidence

PostgreSQL MCP Server MCP Servers average (761 agents)

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

3.9 / 25

1.1 below avg 5.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

13.4 / 20

1.0 above avg 12.4

AdoptionLog-scaled stars · package downloads

2.7 / 20

3.1 below avg 5.8

Activity Inputs

44.1 / 100

StarsRepository reach

6.7 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

9.7 / 25

CommunityFork signal

2.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

78%

of last 100 commits verified

Is PostgreSQL MCP Server safe?

Public trust evidence for PostgreSQL MCP Server 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 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?

No OpenSSF Scorecard data is currently published for PostgreSQL MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is PostgreSQL MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 2 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?

78% 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

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-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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON