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/jpantsjoha/googlecloud-pluginWrote 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/jpantsjoha/googlecloud-plugin/gcloud)<a href="https://agentmods.dev/mcp/jpantsjoha/googlecloud-plugin/gcloud"><img src="https://agentmods.dev/badge/mcp/jpantsjoha/googlecloud-plugin/gcloud/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/mcp/jpantsjoha/googlecloud-plugin/gcloud"><img src="https://agentmods.dev/badge/mcp/jpantsjoha/googlecloud-plugin/gcloud.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gcloud 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 1mo 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
{
"gcloud": {
"command": "npx",
"args": [
"-y",
"@google-cloud/gcloud-mcp"
],
"env": {
"CLOUDSDK_CORE_PROJECT": "${GCP_PROJECT_ID}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. 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.
- 1mo ago First seen · 12 lines scan A c27681bc75bb
gcloud is an MCP server published in the GitHub repository jpantsjoha/googlecloud-plugin (4 stars, last pushed 2mo 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
proximo-proxmox
The Proxmox MCP you can hand the keys: VE/PBS/PMG/PDM. Plan, prove, undo, diagnose. MCP/A2A/API. Runs locally from the proximo-proxmox Python package.
terraform
MCP server "terraform" as configured in aws-samples/sample-agentic-chatbot-accelerator. Runs in Docker (hashicorp/terraform-mcp-server:0.5.2).
foreman
Python library to manipulate The Foreman through the API. Runs locally from the foreman Python package.
sec
AWS Well-Architected Security Assessment Tool MCP Server. Runs locally from the awslabs.well-architected-security-mcp-server Python package.
azure-resource-manager-mcp
MCP server "azure-resource-manager-mcp", hosted remotely at mcp.management.azure.com, as configured in jonathan-vella/apex-accelerator.
mcp-s3-server
An implementation of a Model Context Protocol (MCP) server for AWS S3, enabling AI models, particularly Large Language Models (LLMs), to securely interact with S3 buckets. Runs locally from the mcp-s3-server Python package.