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/mattma87/agenticmcp/agenticmcp-postgresgit clone --depth 1 https://github.com/mattma87/AgenticMCPWrote 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/mattma87/agenticmcp/agenticmcp-postgres)<a href="https://agentmods.dev/mcp/mattma87/agenticmcp/agenticmcp-postgres"><img src="https://agentmods.dev/badge/mcp/mattma87/agenticmcp/agenticmcp-postgres.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agenticmcp-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 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.
What it actually says
{
"agenticmcp-postgres": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--name",
"agenticmcp-client",
"-e",
"MCP_DB_HOST=host.docker.internal",
"-e",
"MCP_DB_PORT=5432",
"-e",
"MCP_DB_NAME=app_db",
"-e",
"MCP_DB_USER=app_user",
"-e",
"MCP_DB_PASSWORD=app_password_change_me",
"-e",
"MCP_ROLE=reader",
"-v",
"${HOME}/.agenticmcp:/app/config:ro",
"ghcr.io/YOUR_USERNAME/agenticmcp:latest"
]
}
}What else claude_desktop_config.json configures
This page is one entry in a file that holds 3. 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.
- 2d ago First seen · 27 lines scan A fcaa01cd535a
agenticmcp-postgres is an MCP server published in the GitHub repository mattma87/AgenticMCP (0 stars, last pushed 6mo 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
db
Minimal, token-efficient Database MCP Server for PostgreSQL, MySQL, SQL Server, SQLite, MariaDB. Runs locally from the @bytebase/dbhub npm package.
cloud-sql-postgresql
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package. Needs 7 environment variables to run.
cloud-sql-postgresql-admin
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
alloydb-postgres-admin
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
postgresql
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
postgres
A MCP server that connects to your database. Runs locally from the mcp-alchemy Python package. Needs 1 environment variable to run.