io.github.marcelo-ochoa/postgres
NPM · @MARCELO-OCHOA/SERVER-POSTGRES · SCANNED SEP 20
MCP server for interacting with PostgreSQL databases
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 Security31
- Malware scan not yet available for this package.Unverified
- CVE check failed: a known high-severity CVE affects @toon-format/toon 1.4.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 35 of 110 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 192 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1273 tokens (~254/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.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
How do I install the io.github.marcelo-ochoa/postgres MCP server?
io.github.marcelo-ochoa/postgres runs locally as an npm package, launched with npx -y @marcelo-ochoa/server-postgres. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @marcelo-ochoa/server-postgres
claude mcp add marcelo-ochoa-postgres -- npx -y @marcelo-ochoa/server-postgres
{
"mcpServers": {
"marcelo-ochoa-postgres": {
"command": "npx",
"args": [
"-y",
"@marcelo-ochoa/server-postgres"
]
}
}
} {
"servers": {
"marcelo-ochoa-postgres": {
"command": "npx",
"args": [
"-y",
"@marcelo-ochoa/server-postgres"
]
}
}
} codex mcp add marcelo-ochoa-postgres -- npx -y @marcelo-ochoa/server-postgres
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"marcelo-ochoa-postgres": {
"type": "local",
"command": [
"npx",
"-y",
"@marcelo-ochoa/server-postgres"
],
"enabled": true
}
}
} openclaw mcp add marcelo-ochoa-postgres --command npx --arg -y --arg @marcelo-ochoa/server-postgres
mcp_servers:
marcelo-ochoa-postgres:
command: "npx"
args: ["-y", "@marcelo-ochoa/server-postgres"] {
"McpServers": {
"marcelo-ochoa-postgres": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@marcelo-ochoa/server-postgres"
]
}
}
} assistant mcp add marcelo-ochoa-postgres -t stdio -c npx -a -y @marcelo-ochoa/server-postgres
{
"mcpServers": {
"marcelo-ochoa-postgres": {
"command": "npx",
"args": [
"-y",
"@marcelo-ochoa/server-postgres"
]
}
}
} 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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/@marcelo-ochoa/server-postgres@1.0.8
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-p95v-992w-h6c3 | CVE-2026-82404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 110 packages
| Packages resolved | 110 |
|---|---|
| Stale | 35 |
| 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 →
pg-awr ~124
Generate a PostgreSQL performance report similar to Oracle AWR. Includes database statistics, top queries (requires pg_stat_statements extension), table/index statistics, connection info, and optimization recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_client | string | – | Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...) |
| model | string | – | The name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...) |
No output schema declared.
No examples provided.
pg-connect ~323
Provides an interface to connect to a specified PostgreSQL database. If a database connection is already active, the tool will close the existing connection before establishing a new one. This tool accepts three required parameters: connectionString: The PostgreSQL connection string without embedded credentials (e.g., postgresql://host:port/dbname or host:port/dbname). To enable encryption (SSL), append ?sslmode=require to the connection string. user: The PostgreSQL username password: The PostgreSQL password The credentials are stored in environment variables PG_USER and PG_PASSWORD for the session. The `model` argument should only be used to specify the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionString | string | yes | The PostgreSQL connection string (e.g. postgresql://host:port/dbname or host:port/dbname) |
| mcp_client | string | – | Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...) |
| model | string | – | The name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...) |
| password | string | yes | The PostgreSQL password |
| user | string | yes | The PostgreSQL user (e.g. postgres) |
No output schema declared.
No examples provided.
pg-explain ~242
Generate and display the execution plan for a given SQL query using PostgreSQL's EXPLAIN command. This tool helps you understand how PostgreSQL will execute your query, including information about table scans, joins, indexes used, and estimated costs. Args: sql: The SQL query to explain. The `model` argument should specify only the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information. Returns: Detailed execution plan showing how PostgreSQL will process the query, including costs, row estimates, and access methods.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_client | string | yes | Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...) |
| model | string | yes | The name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...) |
| sql | string | yes | The SQL query to explain |
No output schema declared.
No examples provided.
pg-query ~346
This tool executes SQL queries in a READ ONLY session connected to a PostgreSQL database. If no active connection exists, it uses MCP server registration argument and environment variables PG_USER and PG_PASSWORD. You should: Execute the provided SQL query. Return the results in Toon format. Args: sql: The SQL query to execute. The `model` argument should specify only the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information. Returns: Json-formatted query results. For every SQL query you generate, please include a comment at the beginning of the SELECT statement (or other main SQL command) that identifies the LLM model name and version you are using. Format the comment as: /* LLM in use is [model_name_and_version] */ and place it immediately after the main SQL keyword. For example: SELECT /* LLM in use is claude-sonnet-4 */ column1, column2 FROM table_name; Please apply this format consistently to all SQL queries you generate, using your actual model name and version in the comment
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_client | string | yes | Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...) |
| model | string | yes | The name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...) |
| sql | string | yes | The SQL query to execute |
No output schema declared.
No examples provided.
pg-stats ~238
Get comprehensive statistics for a specific PostgreSQL table. This tool retrieves detailed information including row counts, table size, index information, column statistics, and other metadata that can help optimize queries and understand data distribution. Args: name: The name of the table to get statistics for. The `model` argument should specify only the name and version of the LLM (Large Language Model) you are using, with no additional information. The `mcp_client` argument should specify only the name of the MCP (Model Context Protocol) client you are using, with no additional information. Returns: Json-formatted table statistics including row counts, size information, indexes, and column details.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_client | string | – | Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...) |
| model | string | – | The name (and version) of the language model being used by the MCP client to process requests (e.g. gpt-4.1, claude-sonnet-4, llama4...) |
| name | string | yes | The name of the table to get statistics for |
No output schema declared.
No examples provided.
What is the io.github.marcelo-ochoa/postgres MCP server?
io.github.marcelo-ochoa/postgres is an MCP server listed in the public MCP registry as io.github.marcelo-ochoa/postgres. MCP server for interacting with PostgreSQL databases. This page covers its npm package (@marcelo-ochoa/server-postgres).
Is the io.github.marcelo-ochoa/postgres MCP server safe to use?
io.github.marcelo-ochoa/postgres scores 63 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 io.github.marcelo-ochoa/postgres MCP server expose?
io.github.marcelo-ochoa/postgres exposes 5 tools: pg-query, pg-stats, pg-explain, pg-connect, pg-awr. Their descriptions and schemas cost roughly 1,273 tokens of context every time the server is loaded.
Is the io.github.marcelo-ochoa/postgres MCP server still maintained?
io.github.marcelo-ochoa/postgres 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 io.github.marcelo-ochoa/postgres MCP server under?
io.github.marcelo-ochoa/postgres declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.