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-postgres-localgit 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-local)<a href="https://agentmods.dev/mcp/mattma87/agenticmcp/agenticmcp-postgres-local"><img src="https://agentmods.dev/badge/mcp/mattma87/agenticmcp/agenticmcp-postgres-local.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agenticmcp-postgres-local 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
{
"agenticmcp-postgres-local": {
"command": "python",
"args": [
"-m",
"agenticmcp.server"
],
"env": {
"MCP_DB_HOST": "localhost",
"MCP_DB_PORT": "5432",
"MCP_DB_NAME": "app_db",
"MCP_DB_USER": "app_user",
"MCP_DB_PASSWORD": "app_password_change_me",
"MCP_ROLE": "reader",
"MCP_PERMISSIONS_FILE": "${HOME}/.agenticmcp/permissions.yaml"
}
}
}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.
- 4d ago First seen · 18 lines scan A 7037b9496b5b
agenticmcp-postgres-local 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
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.
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.
dbeast
MCP server "dbeast" as configured in snss10/DBeast. Runs ${workspaceFolder}/dbeast/src/server.py with python. Needs 9 environment variables to run.
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.
pg-context-mcp
MCP server "pg-context-mcp" as configured in mewsyy/pg-context. Runs locally from the pg-context-mcp npm package.