Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.marcelo-ochoa/postgres

NPM · @MARCELO-OCHOA/SERVER-POSTGRES · SCANNED AUG 3

MCP server for interacting with PostgreSQL databases

Available components

npm · @marcelo-ochoa/server-postgres 49
+17 this week 49 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security37
  • Malware scan not yet available for this package.Unverified
  • Only part of the dependency tree could be resolved (109 of 113), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (109 of 113), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability54
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (poor).Fail
  • 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 Management23
  • Stability observed for 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @marcelo-ochoa/server-postgres

# add to Claude Code
claude mcp add marcelo-ochoa-postgres -- npx -y @marcelo-ochoa/server-postgres
# add to Codex CLI
codex mcp add marcelo-ochoa-postgres -- npx -y @marcelo-ochoa/server-postgres
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marcelo-ochoa-postgres": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@marcelo-ochoa/server-postgres"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add marcelo-ochoa-postgres --command npx --arg -y --arg @marcelo-ochoa/server-postgres
# ~/.hermes/config.yaml
mcp_servers:
  marcelo-ochoa-postgres:
    command: "npx"
    args: ["-y", "@marcelo-ochoa/server-postgres"]
// mcp.json
{
  "mcpServers": {
    "marcelo-ochoa-postgres": {
      "command": "npx",
      "args": [
        "-y",
        "@marcelo-ochoa/server-postgres"
      ]
    }
  }
}
Changelog

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.

  • 2 Aug 26 +25
    • Provenance: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • Schema quality: unverified → poor ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • Stability: unverified → 0.20 ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • License: unverified → pass ▲ functional
    • Licence: MIT functional
  • 1 Aug 26 +19
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
  • 31 Jul 26 −27
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +24
    • Dependency health: partial → unverified ▼ functional
    • Schema quality: unverified → 100 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 28 Jul 26 −24
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Dependency health: unverified → partial ▲ functional
  • 27 Jul 26 32

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@marcelo-ochoa/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 109 packages

109 packages in the resolved dependency tree · 109 deprecated · 33 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~1,273 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
mcp_clientstring—Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...)
modelstring—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.

NameTypeReqDescription
connectionStringstringyesThe PostgreSQL connection string (e.g. postgresql://host:port/dbname or host:port/dbname)
mcp_clientstring—Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...)
modelstring—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...)
passwordstringyesThe PostgreSQL password
userstringyesThe 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.

NameTypeReqDescription
mcp_clientstringyesSpecify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...)
modelstringyesThe 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...)
sqlstringyesThe 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

NameTypeReqDescription
mcp_clientstringyesSpecify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...)
modelstringyesThe 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...)
sqlstringyesThe 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.

NameTypeReqDescription
mcp_clientstring—Specify the name and version of the MCP client implementation being used (e.g. Copilot, Claude, Cline...)
modelstring—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...)
namestringyesThe name of the table to get statistics for

No output schema declared.

No examples provided.