Head to head
PostgreSQL (hardened, read-only) vs pgtriage
Same numbers we show everywhere else, lined up. Ratings come from users, the grade comes from our scanner, adoption comes from public registries.
PostgreSQL (hardened, read-only)
Cio.github.Eszetael/postgres-mcp-hardenedNo reviews yet
Read-only PostgreSQL over MCP. Writes refused at the parsed SQL, plus a READ ONLY transaction.
Full listingpgtriage
Cio.github.pgtriage/pgtriageNo reviews yet
MCP server for PostgreSQL performance auditing with actionable SQL fixes.
Full listingThe short version
Neither has been reviewed yet, so the comparison rests on the scan and the public usage numbers. Both score close on the safety scan (68 and 65 out of 100). PostgreSQL (hardened, read-only) has noticeably more public adoption.
| PostgreSQL (hardened, read-only) | pgtriage | |
|---|---|---|
| User rating | No reviews yet | No reviews yet |
| Safety grade | C68/100 | C65/100 |
| Adoption | Growing | — |
| GitHub stars | 3 | – |
| Downloads / week | 91 | – |
| Runs where | Your machine (local) | Your machine (local) |
| Gateway-ready | No | No |
| Tools | — | 5 |
| Write actions | — | 1 |
| Price per call | Free | Free |
| Licence | MIT | MIT |
| Last release | 2026-09-20 | — |
| Category | Databases | Databases |