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/forest6511/claude-code-recipes-v2Wrote 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/forest6511/claude-code-recipes-v2/postgres)<a href="https://agentmods.dev/mcp/forest6511/claude-code-recipes-v2/postgres"><img src="https://agentmods.dev/badge/mcp/forest6511/claude-code-recipes-v2/postgres/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/forest6511/claude-code-recipes-v2/postgres"><img src="https://agentmods.dev/badge/mcp/forest6511/claude-code-recipes-v2/postgres.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
postgres 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 1mo 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
{
"postgres": {
"command": "npx",
"args": [
"-y",
"@bytebase/dbhub",
"--dsn",
"postgresql://postgres:devpass@localhost:5432/postgres"
]
}
}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.
- 1mo ago First seen · 11 lines scan A cc7d624fef5a
postgres is an MCP server published in the GitHub repository forest6511/claude-code-recipes-v2 (6 stars, last pushed 5mo 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
neon
Neon's hosted MCP server: lets the agent create and manage Neon Postgres projects, branches and databases and run SQL. Remote server at mcp.neon.tech.
AWSPostgres
MCP server "AWSPostgres" as configured in spacehendrix/clauder. Runs locally from the awslabs.postgres-mcp-server@latest Python package. Needs 3 environment variables to run.
postgresql
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
schemabrain
The trust and intelligence layer between AI agents and your database. Runs locally from the schemabrain Python package. Needs 1 environment variable to run.
semantic-rails
Agent-first semantic layer for governed analytics over DuckDB, Snowflake, Postgres, BigQuery, Databricks, Athena, ClickHouse, MotherDuck, and DuckLake. Runs locally from the semantic-rails Python package.
dbeast
MCP server "dbeast" as configured in snss10/DBeast. Runs ${workspaceFolder}/dbeast/src/server.py with python. Needs 9 environment variables to run.