updated 2026-10-16 16:07 UTC

PostgreSQL MCP Server

Repository Website by neverinfamous

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.4 / 10
Provenance None
Signed commits 85%
Last push 18d 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 57.7/100 (Grade C), ranked #740 of 1378 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.4/10; 85% of recent commits are signed; last pushed 2026-09-28. Every point is earned from checkable signals — never paid placement. How scoring works →

How PostgreSQL MCP Server 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 PostgreSQL MCP Server 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 Signed

    github.com/neverinfamous/postgres-mcp, MIT, last pushed 2026-09-28. 85% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Reviewn/a
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies8
    All 18 Scorecard checks
    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 8
    Packaging 10
    Pinned-Dependencies 8
    SAST 10
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

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

Changes to this chain

  • 2026-09-06 OSSF Scorecard: 6.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues PostgreSQL MCP Server’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 PostgreSQL MCP Server compares in MCP Servers

  1. #395 Orcaslicer MCP 58.0 +0.3
  2. #396 MeiGen AI Design MCP 57.8 +0.1
  3. #397 PostgreSQL MCP Server 57.7 this agent
  4. #398 Localstack MCP Server 57.6 −0.1
  5. #399 DevSpace 57.6 −0.1

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

Where the 57.7 comes from

HVTrust dimensions vs the MCP Servers average

57.7 / 100 · 100.0% confidence

PostgreSQL MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.2 / 25
1.7 above avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.9 / 17
1.6 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
12.0 / 20
in line with avg 12.3
AdoptionLog-scaled stars · package downloads
8.7 / 20
1.3 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Rank Moved
Rank dropped 23 spots (#714 → #737)
2026-10-14
Rank Moved
Rank dropped 22 spots (#692 → #714)
2026-10-09
Rank Moved
Rank dropped 10 spots (#667 → #677)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.4/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
35.8
Activity sub-score · out of 100
#397
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 →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed 18 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
12
Forks
3
Last Push
2026-09-28
18 days ago
Commits (4 wk)
1
Downloads (7d)
32,212
docker
HN mentions (30d)
—
Open Issues
1
Rank Change
▼3
was #737

Analysis

Activity Inputs

35.8 / 100
StarsRepository reach
6.7 / 30
FreshnessLast push recency
22.5 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
2.8 / 20

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.4/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?
Maintained. Last push was 18 days ago.
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.
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
Rank 28HVTrust 6Grade 4Listed 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
2026-10-15
Rank Moved
Rank dropped 23 spots (#714 → #737)
2026-10-14
Rank Moved
Rank dropped 22 spots (#692 → #714)
2026-10-09
Rank Moved
Rank dropped 10 spots (#667 → #677)
2026-10-07
Rank Moved
Rank dropped 14 spots (#648 → #662)
2026-10-06
Rank Moved
Rank rose 30 spots (#678 → #648)
2026-09-28
Rank Moved
Rank rose 11 spots (#654 → #643)
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 → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 57.7 Grade C
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.4 · Raw JSON