Is PostgreSQL performance Tuner MCP Server safe to use?

PostgreSQL performance Tuner MCP Server has an HVTrust score of 41.4/100 (Grade D), ranked #1138 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 performance Tuner MCP Server?

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

PostgreSQL performance Tuner MCP Server

isdaniel/pgtuner_mcp

provides AI-powered PostgreSQL performance tuning capabilities.

MCP Servers Python Listed Apache-2.0

Is PostgreSQL performance Tuner MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.1 / 10

Provenance None

Signed commits 5%

Last push 116d ago

Compare PostgreSQL performance Tuner MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: PostgreSQL performance Tuner MCP Server scores 41.4/100 (Grade D), ranked #1138 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 3.1/10; 5% of recent commits are signed; last pushed 2026-06-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How PostgreSQL performance Tuner MCP Server compares in MCP Servers

#670 Zenmoney MCP 41.6 +0.2
#671 Just MCP Server 41.5 +0.1
#672 PostgreSQL performance Tuner MCP Server 41.4 this agent
#673 XcodeMCP 41.2 −0.2
#674 Dash MCP Server 41.2 −0.2

Bars show each HVTrust score; the tick marks PostgreSQL performance Tuner MCP Server’s 41.4.

Where the 41.4 comes from

HVTrust dimensions vs the MCP Servers average

41.4 / 100 · 100.0% confidence

PostgreSQL performance Tuner MCP Server MCP Servers average (775 agents)

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

4.1 / 25

6.2 below 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

11.1 / 17

1.1 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

4.3 / 20

7.8 below avg 12.1

AdoptionLog-scaled stars · package downloads

5.4 / 20

1.8 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-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

Rank Moved

Rank rose 98 spots (#1231 → #1133)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.1/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 116 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for PostgreSQL performance Tuner MCP Server View MCP Servers Report missing data

21.5

Activity sub-score · out of 100

#672

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 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-06-02

116 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

was #1138

Analysis

Activity Inputs

21.5 / 100

StarsRepository reach

8.9 / 30

FreshnessLast push recency

8.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

3.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.1 / 10

OpenSSF Scorecard · scanned Sep 22, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 0

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Common questions about PostgreSQL performance Tuner MCP Server

Public trust evidence for PostgreSQL performance Tuner 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 performance Tuner MCP Server publish package provenance?

No published build provenance is currently detected for PostgreSQL performance Tuner 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 performance Tuner MCP Server have an OpenSSF Scorecard?

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

Slowing down. Last push was 116 days ago — keep an eye on whether activity resumes.

What license does PostgreSQL performance Tuner MCP Server use?

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

Are PostgreSQL performance Tuner MCP Server's commits signed?

4% of the last 100 commits to PostgreSQL performance Tuner 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

medium confidence

Implemented

PostgreSQL performance Tuner 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: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

database

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

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 performance Tuner 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

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-08-31

Activity Went Stale

No commits for 90 days

Maintain PostgreSQL performance Tuner MCP Server?

For maintainers

HVTrust scores PostgreSQL performance Tuner 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-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

Rank Moved

Rank rose 98 spots (#1231 → #1133)

2026-09-23

HVTrust Changed

HVTrust up 24.7pts (17.0 → 41.7)

2026-09-22

Newly Listed

First tracked at rank #1231

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 10 spots (#1076 → #1086)

2026-09-11

Rank Moved

Rank dropped 14 spots (#1062 → #1076)

2026-09-10

Rank Moved

Rank rose 10 spots (#1072 → #1062)

2026-09-09

Rank Moved

Rank dropped 19 spots (#1053 → #1072)

2026-09-08

Rank Moved

Rank dropped 10 spots (#1043 → #1053)

2026-09-07

Rank Moved

Rank dropped 38 spots (#1005 → #1043)

2026-09-06

Rank Moved

Rank rose 13 spots (#1018 → #1005)

2026-09-05

Rank Moved

Rank dropped 42 spots (#976 → #1018)

2026-09-04

Rank Moved

Rank dropped 29 spots (#947 → #976)

2026-09-03

Rank Moved

Rank dropped 58 spots (#889 → #947)

2026-09-02

Rank Moved

Rank dropped 44 spots (#845 → #889)

2026-09-01

Rank Moved

Rank dropped 32 spots (#813 → #845)

2026-08-31

Activity Went Stale

No commits for 90 days

2026-08-31

Rank Moved

Rank dropped 38 spots (#775 → #813)

2026-08-30

Rank Moved

Rank dropped 24 spots (#751 → #775)

2026-08-29

Rank Moved

Rank dropped 51 spots (#700 → #751)

2026-08-28

Scorecard Added

OSSF Scorecard: 3.2/10

2026-08-28

Rank Moved

Rank rose 258 spots (#958 → #700)

2026-08-28

HVTrust Changed

HVTrust up 17.1pts (26.7 → 43.8)

2026-08-27

Rank Moved

Rank dropped 27 spots (#931 → #958)

2026-08-26

Rank Moved

Rank dropped 113 spots (#818 → #931)

2026-08-16

Rank Moved

Rank dropped 17 spots (#798 → #815)

2026-08-13

Rank Moved

Rank dropped 12 spots (#786 → #798)

2026-08-10

Rank Moved

Rank dropped 44 spots (#748 → #792)

2026-08-08

Newly Listed

First tracked at rank #745

GitHub → PyPI: pgtuner-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/postgresql-performance-tuner-mcp-server.svg)](https://hvtracker.net/agents/postgresql-performance-tuner-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/postgresql-performance-tuner-mcp-server"><img src="https://hvtracker.net/badge/postgresql-performance-tuner-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON