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/gprot42/grok-mcp-cloudrun/cloud-rungit clone --depth 1 https://github.com/gprot42/grok-mcp-cloudrunWrote 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/gprot42/grok-mcp-cloudrun/cloud-run)<a href="https://agentmods.dev/mcp/gprot42/grok-mcp-cloudrun/cloud-run"><img src="https://agentmods.dev/badge/mcp/gprot42/grok-mcp-cloudrun/cloud-run.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cloud-run 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
{
"cloud-run": {
"command": "npx",
"args": [
"-y",
"@google-cloud/[email protected]"
],
"startup_timeout_sec": 60,
"tool_timeouts": {
"deploy-local-folder": 600
},
"env": {
"GOOGLE_CLOUD_PROJECT": "${GOOGLE_CLOUD_PROJECT}",
"GOOGLE_CLOUD_REGION": "${GOOGLE_CLOUD_REGION:-us-central1}",
"DEFAULT_SERVICE_NAME": "${DEFAULT_SERVICE_NAME:-}"
}
}
}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 · 18 lines scan A 0fccac316349
cloud-run is an MCP server published in the GitHub repository gprot42/grok-mcp-cloudrun (0 stars, last pushed 2mo ago), 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-08-31.
Other mcp servers, from other repositories
ssh-licco
SSH Model Context Protocol Server - Enable SSH functionality for AI models. Runs locally from the ssh-licco Python package. Needs 4 environment variables to run.
tailscale-compute
Run builds, tests, and benchmarks on your own Tailscale compute node. Runs locally from the @dylantirandaz/tailscale-compute-mcp npm package. Needs 6 environment variables to run.
project-bourne
Run reproducible scientific workloads on GPUs, local compute, Slurm, and PBS with provenance. Runs locally from the @project-bourne/mcp npm package.
playwright
MCP server "playwright" as configured in jtylek/EpesiCRM. Runs C:\Users\jasiek\AppData\Roaming\npm\node_modules\@playwright\mcp\cli.js with node.
vllm-ops-mcp
Read-only ops/health MCP server for a local vLLM server (WSL2/systemd-managed): liveness vs real-completion health tiers, GPU/VRAM status, systemd service status, and live serve-flag introspection. No lifecycle-control tools in this release. Runs locally from the vllm-ops-mcp Python package.
terraform-docs-mcp
MCP server "terraform-docs-mcp" as configured in brightredchilli/terraform-docs. Runs locally from the terraform-docs-mcp Python package.