Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/mewsyy/pg-context/pg-context-mcpgit clone --depth 1 https://github.com/mewsyy/pg-contextWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/mewsyy/pg-context/pg-context-mcp)<a href="https://agentmods.dev/mcp/mewsyy/pg-context/pg-context-mcp"><img src="https://agentmods.dev/badge/mcp/mewsyy/pg-context/pg-context-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
pg-context-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "pg-context-mcp": { "command": "npx", "args": [ "-y", "pg-context-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 9 lines scan A ec3b7bc9db39
pg-context-mcp is an MCP server published in the GitHub repository mewsyy/pg-context (1 stars, last pushed 19d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
dbeast
MCP server "dbeast" as configured in snss10/DBeast. Runs ${workspaceFolder}/dbeast/src/server.py with python. Needs 9 environment variables to run.
postgres
Secure read-only PostgreSQL MCP server in Rust — a maintained alternative to the deprecated @modelcontextprotocol/server-postgres. Blocks writes at the AST, not with regexes. Runs locally from the postgres-mcp-hardened npm package. Needs 2 environment variables to run.
postgres-mcp-hardened
Read-only PostgreSQL over MCP. Writes refused at the parsed SQL, plus a READ ONLY transaction. Runs locally from the postgres-mcp-hardened npm package. Needs 4 environment variables to run.
mcp
Provision Postgres databases + webhooks from AI coding agents in one HTTP call. Runs locally from the @instanode/mcp npm package. Needs 2 environment variables to run.
nexql-mcp
Standalone Postgres MCP server — schema-aware, read-only by default, installable everywhere. Runs locally from the nexql-mcp npm package. Needs 2 environment variables to run.
postgrest-mcp
MCP server for PostgREST — 10 tools for CRUD operations, filtering, resource embedding, and RPC on PostgreSQL databases via REST API. Runs locally from the @node2flow/postgrest-mcp npm package.