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/saaspegasus/django-boilerplate/postgresgit clone --depth 1 https://github.com/saaspegasus/django-boilerplateWrote 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/saaspegasus/django-boilerplate/postgres)<a href="https://agentmods.dev/mcp/saaspegasus/django-boilerplate/postgres"><img src="https://agentmods.dev/badge/mcp/saaspegasus/django-boilerplate/postgres.svg" alt="Measured on agentmods" 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 4d 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": "uvx",
"args": [
"--from",
"mcp-alchemy==2025.8.15.91819",
"--with",
"psycopg2-binary",
"--refresh-package",
"mcp-alchemy",
"mcp-alchemy"
],
"env": {
"DB_URL": "postgresql://postgres:postgres@localhost:5432/project"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 4d ago First seen · 17 lines scan A 7316fc1b16f5
postgres is an MCP server published in the GitHub repository saaspegasus/django-boilerplate (166 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-30.
Other mcp servers, from other repositories
db
Minimal, token-efficient Database MCP Server for PostgreSQL, MySQL, SQL Server, SQLite, MariaDB. Runs locally from the @bytebase/dbhub npm package.
postgresql
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
dryrun
PostgreSQL schema intelligence from a committed snapshot. No connection, no credentials. Runs locally from the @boringsql/dryrun 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.
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.