PostgreSQL
NPM · MCP-POSTGRES-SERVER · SCANNED SEP 20
MCP server for PostgreSQL: local, Docker, RDS, Neon, Supabase, or behind an SSH bastion.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 39 of 117 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 483 tokens (~96/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
How do I install the PostgreSQL MCP server?
PostgreSQL runs locally as an npm package, launched with npx -y mcp-postgres-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-postgres-server
claude mcp add antonorlov-mcp-postgres-server -- npx -y mcp-postgres-server
{
"mcpServers": {
"antonorlov-mcp-postgres-server": {
"command": "npx",
"args": [
"-y",
"mcp-postgres-server"
]
}
}
} {
"servers": {
"antonorlov-mcp-postgres-server": {
"command": "npx",
"args": [
"-y",
"mcp-postgres-server"
]
}
}
} codex mcp add antonorlov-mcp-postgres-server -- npx -y mcp-postgres-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"antonorlov-mcp-postgres-server": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-postgres-server"
],
"enabled": true
}
}
} openclaw mcp add antonorlov-mcp-postgres-server --command npx --arg -y --arg mcp-postgres-server
mcp_servers:
antonorlov-mcp-postgres-server:
command: "npx"
args: ["-y", "mcp-postgres-server"] {
"McpServers": {
"antonorlov-mcp-postgres-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-postgres-server"
]
}
}
} assistant mcp add antonorlov-mcp-postgres-server -t stdio -c npx -a -y mcp-postgres-server
{
"mcpServers": {
"antonorlov-mcp-postgres-server": {
"command": "npx",
"args": [
"-y",
"mcp-postgres-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Sept 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 14 Sept 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/mcp-postgres-server@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 117 packages
| Packages resolved | 117 |
|---|---|
| Stale | 39 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe_table Describe a table ~86
Show the structure of one table: column names, data types, nullability, defaults, and primary-key membership. Call this before writing non-trivial queries against a table. Returns {columns: [{column, type, nullable, default, is_primary_key}, ...]}.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | string | – | Schema name (default: 'public') |
| table | string | yes | Table name |
No output schema declared.
No examples provided.
execute Run a write statement (disabled) ~108
Run a data-modifying SQL statement (INSERT/UPDATE/DELETE or DDL). Currently DISABLED: the server is read-only, so this returns an error and changes nothing. To enable writes, the operator must start the server with PG_ALLOW_WRITE=true.
| Name | Type | Req | Description |
|---|---|---|---|
| params | array | – | Positional parameter values bound to $1, $2, ... placeholders. |
| sql | string | yes | One INSERT / UPDATE / DELETE / DDL statement. Use $1, $2, ... for parameters. |
No output schema declared.
No examples provided.
list_schemas List schemas ~46
List every schema in the connected database. Start here when exploring an unfamiliar database, then call list_tables for the schema you care about. Returns {schemas: [name, ...]}.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tables List tables ~63
List all tables in a schema (default: 'public'). Use this before querying tables you have not seen yet, then call describe_table for column details. Returns {tables: [name, ...]}.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | string | – | Schema name (default: 'public') |
No output schema declared.
No examples provided.
query Run read-only SQL ~180
Run one read-only SQL statement against the connected PostgreSQL database and get rows back as JSON. Send exactly one statement per call (SELECT, WITH, EXPLAIN, or SHOW). It runs inside an engine-enforced read-only transaction, so any write is refused by the database. Use this tool for all data reading, aggregation, and query planning. Returns {rows, rowCount, returnedRows, truncated}, plus hint when truncated is true. Prefer $1, $2 placeholders with the params array over interpolating values. Results are capped at ~32768 bytes; truncated:true means rows were dropped - add LIMIT/WHERE or select fewer columns.
| Name | Type | Req | Description |
|---|---|---|---|
| params | array | – | Positional parameter values bound to $1, $2, ... placeholders. |
| sql | string | yes | One SQL statement. Use $1, $2, ... for parameters. |
No output schema declared.
No examples provided.
What is the PostgreSQL MCP server?
PostgreSQL is an MCP server listed in the public MCP registry as io.github.antonorlov/mcp-postgres-server. MCP server for PostgreSQL: local, Docker, RDS, Neon, Supabase, or behind an SSH bastion. This page covers its npm package (mcp-postgres-server).
Is the PostgreSQL MCP server safe to use?
PostgreSQL scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.
What tools does the PostgreSQL MCP server expose?
PostgreSQL exposes 5 tools: query, execute, list_schemas, list_tables, describe_table. Their descriptions and schemas cost roughly 483 tokens of context every time the server is loaded.
Is the PostgreSQL MCP server still maintained?
PostgreSQL is still listed as active in the MCP registry. We last reached this channel on 20 September 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 MCP server under?
PostgreSQL declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.