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/mosesliao/postgres-mcp/postgres-mcpgit clone --depth 1 https://github.com/mosesliao/postgres-mcpGrade A, and why
postgres-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 2d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- postgres-mcp — 100% identical, 0 lines differ
- postgres-mcp — 100% identical, 0 lines differ
- postgres-mcp — 100% identical, 0 lines differ
- postgres-mcp — 100% identical, 0 lines differ
- postgres-mcp — 100% identical, 0 lines differ
- postgres-mcp — 100% identical, 0 lines differ
- postgres-mcp — 100% identical, 0 lines differ
- postgres-mcp — 100% identical, 0 lines differ
What it actually says
{ "postgres-mcp": { "command": "uvx", "args": [ "postgres-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.
- 2d ago First seen · 8 lines scan A d9248ec627e1
postgres-mcp is an MCP server published in the GitHub repository mosesliao/postgres-mcp (2 stars, last pushed 1mo 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
dryrun
PostgreSQL schema intelligence from a committed snapshot. No connection, no credentials. Runs locally from the @boringsql/dryrun npm package.
pgbot
MCP server "pgbot" as configured in pgrundev/pgbot. Launched with pgbot mcp.
postgres-mcp
MCP server "postgres-mcp" as configured in pgEdge/pgedge-postgres-mcp. Runs in Docker (ghcr.io/pgedge/postgres-mcp:latest).
seedfast
AI-powered PostgreSQL database seeding tool. Runs locally from the seedfast npm package. Needs 1 environment variable to run.
pgmcp
MCP server "pgmcp" as configured in pascalallen/pgmcp. Runs in Docker (ghcr.io/pascalallen/pgmcp:1.1.0). Needs 1 environment variable to run.
local-knowledge-rag
MCP server "local-knowledge-rag" as configured in patakuti/local-knowledge-rag-mcp. Runs /path/to/local-knowledge-rag-mcp/dist/mcp-server.js with node. Needs 3 environment variables to run.