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.
git clone --depth 1 https://github.com/igoraguiar/bun-pg-mcpWrote 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/igoraguiar/bun-pg-mcp/pg-mcp)<a href="https://agentmods.dev/mcp/igoraguiar/bun-pg-mcp/pg-mcp"><img src="https://agentmods.dev/badge/mcp/igoraguiar/bun-pg-mcp/pg-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/igoraguiar/bun-pg-mcp/pg-mcp"><img src="https://agentmods.dev/badge/mcp/igoraguiar/bun-pg-mcp/pg-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pg-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 8d 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-mcp": { "command": "npx", "args": [ "-y", "pg-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.
- 8d ago First seen · 9 lines scan A 7471375e4dc6
pg-mcp is an MCP server published in the GitHub repository igoraguiar/bun-pg-mcp (1 stars, last pushed 27d 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
mcpbridge
MCP server "mcpbridge" as configured in manulthanura/MCPBridge. Runs /absolute/path/to/mcpbridge/dist/main.js with node. Needs 3 environment variables to run.
virtual-fs
PostgreSQL-backed virtual filesystem for agents: session isolation, shared stores, POSIX ops, RLS. Runs locally from the mcp-virtual-fs npm package. Needs 4 environment variables to run.
supabase
Supabase's hosted MCP server: lets the agent manage projects, tables, SQL and migrations. Remote server at mcp.supabase.com.
dryrun
PostgreSQL schema intelligence from a committed snapshot. No connection, no credentials. Runs locally from the @boringsql/dryrun npm package.
dbconvert-streams
Read-only SQL across PostgreSQL, MySQL, S3 buckets and local data files — one query can join across all of them. MCP server. Runs locally from the @dbconvert/stream-mcp npm package. Needs 1 environment variable to run.
pgbot
MCP server "pgbot" as configured in pgrundev/pgbot. Launched with pgbot mcp.