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/gemini-cli-extensions/alloydb/alloydb-postgresgit clone --depth 1 https://github.com/gemini-cli-extensions/alloydbWrote 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/gemini-cli-extensions/alloydb/alloydb-postgres)<a href="https://agentmods.dev/mcp/gemini-cli-extensions/alloydb/alloydb-postgres"><img src="https://agentmods.dev/badge/mcp/gemini-cli-extensions/alloydb/alloydb-postgres.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
alloydb-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 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
{
"alloydb-postgres": {
"command": "npx",
"args": [
"-y",
"@toolbox-sdk/[email protected]",
"--prebuilt",
"alloydb-postgres",
"--stdio"
],
"env_vars": [
"ALLOYDB_POSTGRES_PROJECT",
"ALLOYDB_POSTGRES_REGION",
"ALLOYDB_POSTGRES_CLUSTER",
"ALLOYDB_POSTGRES_INSTANCE",
"ALLOYDB_POSTGRES_DATABASE",
"ALLOYDB_POSTGRES_USER",
"ALLOYDB_POSTGRES_PASSWORD",
"ALLOYDB_POSTGRES_IP_TYPE"
]
}
}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 · 22 lines scan A c64724ea6523
alloydb-postgres is an MCP server published in the GitHub repository gemini-cli-extensions/alloydb (23 stars, last pushed today), licensed Apache-2.0. 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-09-05.
Other mcp servers, from other repositories
cloud-sql-postgres
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
firestore
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
spanner
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
cloud-sql-mysql
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
oracledb
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
cloud-sql-mssql
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.