# PostgreSQL (hardened, read-only) (oci · ghcr.io/eszetael/postgres-mcp-hardened:0.1.10)

Read-only PostgreSQL over MCP. Writes refused at the parsed SQL, plus a READ ONLY transaction.

- Trust score: 10/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `postgres-mcp-hardened`: 48/100, [markdown](https://verifymcp.io/servers/eszetael-postgres-mcp-hardened/postgres-mcp-hardened.md), [page](https://verifymcp.io/servers/eszetael-postgres-mcp-hardened/postgres-mcp-hardened)
- oci · `ghcr.io/eszetael/postgres-mcp-hardened:0.1.10`: 10/100 (this document), [markdown](https://verifymcp.io/servers/eszetael-postgres-mcp-hardened/ghcr-io-eszetael-postgres-mcp-hardened-0-1-10.md), [page](https://verifymcp.io/servers/eszetael-postgres-mcp-hardened/ghcr-io-eszetael-postgres-mcp-hardened-0-1-10)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/eszetael/postgres-mcp-hardened:0.1.10`
- Transport: `streamable-http`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 61 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

```bash
docker pull ghcr.io/eszetael/postgres-mcp-hardened:0.1.10
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-05 (score 0)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/eszetael-postgres-mcp-hardened/ghcr-io-eszetael-postgres-mcp-hardened-0-1-10#diagnostics

## Score history

- 2026-11-05: 10
- 2026-11-04: 10
- 2026-11-03: 10
- 2026-11-02: 10
- 2026-11-01: 10
- 2026-10-31: 10
- 2026-10-30: 10
- 2026-10-29: 10
- 2026-10-28: 10
- 2026-10-27: 10
- 2026-10-26: 10
- 2026-10-25: 10
- 2026-10-24: 10
- 2026-10-23: 10
- 2026-10-22: 10
- 2026-10-21: 10
- 2026-10-20: 10
- 2026-10-19: 10
- 2026-10-18: 10
- 2026-10-17: 10
- 2026-10-16: 10
- 2026-10-15: 10
- 2026-10-14: 10
- 2026-10-13: 10
- 2026-10-12: 10
- 2026-10-10: 10
- 2026-10-07: 10
- 2026-10-06: 10
- 2026-10-04: 10
- 2026-10-03: 10

## Common questions

### What is the PostgreSQL (hardened, read-only) MCP server?

PostgreSQL (hardened, read-only) is an MCP server listed in the public MCP registry as io.github.Eszetael/postgres-mcp-hardened. Read-only PostgreSQL over MCP. Writes refused at the parsed SQL, plus a READ ONLY transaction. This page covers its container image (ghcr.io/eszetael/postgres-mcp-hardened:0.1.10).

### Is the PostgreSQL (hardened, read-only) MCP server safe to use?

PostgreSQL (hardened, read-only) scores 10 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### Is the PostgreSQL (hardened, read-only) MCP server still maintained?

PostgreSQL (hardened, read-only) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the PostgreSQL (hardened, read-only) MCP server under?

PostgreSQL (hardened, read-only) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the PostgreSQL (hardened, read-only) MCP server?

VerifyMCP ran 5 checks on PostgreSQL (hardened, read-only), covering Source repository, Provenance, License, Maintenance and 1 more. 9 items could not be completed, a gap on our side rather than a finding about PostgreSQL (hardened, read-only): Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/eszetael/postgres-mcp-hardened
- Repository: https://github.com/Eszetael/postgres-mcp-hardened
- Changelog RSS feed: https://verifymcp.io/servers/eszetael-postgres-mcp-hardened/ghcr-io-eszetael-postgres-mcp-hardened-0-1-10.xml
- Changelog JSON feed: https://verifymcp.io/servers/eszetael-postgres-mcp-hardened/ghcr-io-eszetael-postgres-mcp-hardened-0-1-10/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/eszetael-postgres-mcp-hardened/ghcr-io-eszetael-postgres-mcp-hardened-0-1-10.json
- HTML version of this page: https://verifymcp.io/servers/eszetael-postgres-mcp-hardened/ghcr-io-eszetael-postgres-mcp-hardened-0-1-10