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/devopam/MCPgWrote 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/plugins/devopam/mcpg/mcpg)<a href="https://agentmods.dev/plugins/devopam/mcpg/mcpg"><img src="https://agentmods.dev/badge/plugins/devopam/mcpg/mcpg/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/plugins/devopam/mcpg/mcpg"><img src="https://agentmods.dev/badge/plugins/devopam/mcpg/mcpg.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcpg 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 today.
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
{
"name": "mcpg",
"version": "0.8.3",
"description": "Production-grade PostgreSQL MCP server: query, tune, and operate Postgres — read-only by default.",
"author": {
"name": "Devopam Mittra",
"email": "[email protected]"
},
"homepage": "https://github.com/devopam/MCPg",
"repository": "https://github.com/devopam/MCPg",
"license": "MIT",
"keywords": [
"postgresql",
"postgres",
"database",
"sql",
"mcp",
"pgvector"
],
"logo": "docs/assets/logo-400.png",
"mcpServers": "packaging/cursor/mcp.json",
"variables": {
"type": "object",
"properties": {
"MCPG_DATABASE_URL": {
"type": "string",
"title": "PostgreSQL connection URL",
"description": "e.g. postgresql://user:password@localhost:5432/mydb — remote hosts need ?sslmode=require."
},
"MCPG_ACCESS_MODE": {
"type": "string",
"title": "Access mode",
"description": "read-only (default, safe) | restricted (allows write tools) | unrestricted (DBA surface; pair with MCPG_ALLOW_DDL etc.).",
"default": "read-only",
"enum": ["read-only", "restricted", "unrestricted"]
}
},
"required": ["MCPG_DATABASE_URL"]
}
}
What it installs
The manifest is a name and a version. 1 MCP server travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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.
- today First seen · 41 lines scan A 782dfc8f24c1
mcpg is a plugin published in the GitHub repository devopam/MCPg (14 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-29.
Other plugins, from other repositories
neon-branch-per-session
A Neon database branch for each Claude Code session: created from your default (or chosen) branch when the session starts, handed to every command Claude runs as DATABASEURL, and set to expire on its own (or deleted when the session ends). Claude can migrate, seed and break the branch without touching production data.
database-design
Database architecture, schema design, and SQL optimization for production systems.
database-migrations
Database migration automation, observability, and cross-database migration strategies.
skillry-database-and-data
Prisma, Postgres/Supabase, migrations, seeds/fixtures, query performance, and RLS/edge functions.
database-performance-optimizer
Use this agent when you need to optimize database performance for B2B applications at enterprise scale. This agent specializes in multi-tenant database optimization, query performance tuning, indexing strategies, connection pooling, and database scaling for SaaS platforms. Handles PostgreSQL, MySQL, MongoDB, and cloud.
LUXOR Database Pro
Professional database engineering skills covering PostgreSQL, SQLAlchemy, Alembic, pandas, Redis, vector databases, and database patterns.