Loading…
Read-only PostgreSQL over MCP. Writes refused at the parsed SQL, plus a READ ONLY transaction.
PostgreSQL (hardened, read-only) is an MCP server entry in ChatHome Skills, sourced from Official MCP Registry and scored 73/100. As a Model Context Protocol server, it exposes tools that MCP-compatible LLM clients such as Claude, Cursor, and Copilot can call directly, extending an agent's reach beyond its built-in capabilities. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding PostgreSQL (hardened, read-only) to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
npx -y postgres-mcp-hardened@0.1.10Review the upstream source before running this command.
{
"_meta": {
"io.modelcontextprotocol.registry/official": {
"status": "active",
"isLatest": true,
"updatedAt": "2026-09-04T23:18:25.068686Z",
"publishedAt": "2026-09-04T23:18:25.068686Z",
"statusChangedAt": "2026-09-04T23:18:25.068686Z"
}
},
"server": {
"name": "io.github.Eszetael/postgres-mcp-hardened",
"title": "PostgreSQL (hardened, read-only)",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"version": "0.1.10",
"packages": [
{
"version": "0.1.10",
"transport": {
"type": "stdio"
},
"identifier": "postgres-mcp-hardened",
"runtimeHint": "npx",
"registryType": "npm",
"runtimeArguments": [
{
"type": "positional",
"value": "--stdio",
"isRequired": true
}
],
"environmentVariables": [
{
"name": "DATABASE_URL",
"isSecret": true,
"isRequired": true,
"description": "Connection string for the role the server connects as. Use a role that cannot write — the server refuses writes twice, but a read-only role is the layer that does not depend on us being correct. `--print-setup-sql` prints the SQL that creates one."
},
{
"name": "MCP_STATEMENT_TIMEOUT",
"description": "Server-side statement timeout, e.g. `5s`. A question that would pin the database is cancelled by PostgreSQL, not by hope."
},
{
"name": "MCP_ALLOW_TABLES",
"description": "Comma-separated allowlist. A table off the list is refused by name, and hiding it inside a CTE, a view or a join does not help."
},
{
"name": "MCP_AUDIT_LOG",
"description": "Path to the tamper-evident audit log. Entries are chained by hash and survive a restart; `--verify-audit` checks the chain against an off-host anchor."
}
]
},
{
"transport": {
"url": "http://localhost:8080/mcp",
"type": "streamable-http"
},
"identifier": "ghcr.io/eszetael/postgres-mcp-hardened:0.1.10",
"registryType": "oci",
"environmentVariables": [
{
"name": "DATABASE_URL",
"isSecret": true,
"isRequired": true,
"description": "Connection string for a role that cannot write."
},
{
"name": "MCP_ADDR",
"description": "Address to bind, default 127.0.0.1:8080."
}
]
}
],
"repository": {
"url": "https://github.com/Eszetael/postgres-mcp-hardened",
"source": "github"
},
"websiteUrl": "https://github.com/Eszetael/postgres-mcp-hardened",
"description": "Read-only PostgreSQL over MCP. Writes refused at the parsed SQL, plus a READ ONLY transaction."
}
}