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/jayanthlocam/agentic-rag-postgres-mcp/agentic-rag-postgres-mcpgit clone --depth 1 https://github.com/jayanthlocam/agentic-rag-postgres-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/jayanthlocam/agentic-rag-postgres-mcp/agentic-rag-postgres-mcp)<a href="https://agentmods.dev/mcp/jayanthlocam/agentic-rag-postgres-mcp/agentic-rag-postgres-mcp"><img src="https://agentmods.dev/badge/mcp/jayanthlocam/agentic-rag-postgres-mcp/agentic-rag-postgres-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agentic-rag-postgres-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 3d 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
{ "agentic-rag-postgres-mcp": { "command": "uvx", "args": [ "agentic-rag-postgres-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.
- 3d ago First seen · 8 lines scan A 217126d10883
agentic-rag-postgres-mcp is an MCP server published in the GitHub repository jayanthlocam/agentic-rag-postgres-mcp (0 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-31.
Other mcp servers, from other repositories
local-knowledge-rag
MCP server "local-knowledge-rag" as configured in patakuti/local-knowledge-rag-mcp. Runs /path/to/local-knowledge-rag-mcp/dist/mcp-server.js with node. Needs 3 environment variables to run.
notes-rag-pg
MCP server "notes-rag-pg" as configured in 00aimlds00/notes-rag-pg. Runs locally from the notes-rag-pg Python package.
haiku-rag
Local-first agentic RAG with citations - hybrid search, reranking and multimodal retrieval over your own documents, no database server required. Runs locally from the haiku-rag Python package.
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.
pg-context-mcp
MCP server "pg-context-mcp" as configured in mewsyy/pg-context. Runs locally from the pg-context-mcp npm package.