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/toolbox)<a href="https://agentmods.dev/mcp/jpantsjoha/googlecloud-plugin/toolbox"><img src="https://agentmods.dev/badge/mcp/jpantsjoha/googlecloud-plugin/toolbox/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/toolbox"><img src="https://agentmods.dev/badge/mcp/jpantsjoha/googlecloud-plugin/toolbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
toolbox 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
{
"toolbox": {
"command": "npx",
"args": [
"-y",
"@toolbox-sdk/server",
"--stdio",
"--config",
"${TOOLBOX_TOOLS_FILE}"
],
"env": {
"GCP_PROJECT_ID": "${GCP_PROJECT_ID}",
"GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}",
"TOOLBOX_TOOLS_FILE": "${TOOLBOX_TOOLS_FILE}"
}
}
}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 · 17 lines scan A f682727a940f
toolbox 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
crm-mcp
MCP server "crm-mcp", hosted remotely at crm-mcp, as configured in adithyan-ak/AgentHound.
moragent
MCP server "moragent" as configured in EduardoMoraga/moragent. Runs locally from the moragent npm package.
open-agent-polity
Open governance for AI agents: join, create topics, debate, amend, vote, follow, and invite. Remote server at open-agent-polity.politeia-agents.workers.dev.
intentfence
Signed U.S. CPI data, Base wallet risk, x402 quote checks, and payment preflights for AI agents. Remote server at agentpass-protocol.rmalka06.chatgpt.site.
multi-agent-orchestration-with-mcp-and-a2a
MCP server "multi-agent-orchestration-with-mcp-and-a2a" as configured in Saad-Dev13/MultiAgentOrchestrationwithMCPandA2A. Runs locally from the multi-agent-orchestration-with-mcp-and-a2a Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.