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/globodai-group/mcp-gcloud-dnsWrote 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/globodai-group/mcp-gcloud-dns/globodai-mcp-gcloud-dns)<a href="https://agentmods.dev/mcp/globodai-group/mcp-gcloud-dns/globodai-mcp-gcloud-dns"><img src="https://agentmods.dev/badge/mcp/globodai-group/mcp-gcloud-dns/globodai-mcp-gcloud-dns/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/globodai-group/mcp-gcloud-dns/globodai-mcp-gcloud-dns"><img src="https://agentmods.dev/badge/mcp/globodai-group/mcp-gcloud-dns/globodai-mcp-gcloud-dns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
globodai-mcp-gcloud-dns 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 11d 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
{ "globodai-mcp-gcloud-dns": { "command": "npx", "args": [ "-y", "globodai-mcp-gcloud-dns" ] } }
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.
- 11d ago First seen · 9 lines scan A c8d9f706fd3a
globodai-mcp-gcloud-dns is an MCP server published in the GitHub repository globodai-group/mcp-gcloud-dns (0 stars, last pushed 7mo 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
platform-mcp
Read-only GCP platform-engineer MCP server for debugging and cost optimization. Runs locally from the platform-mcp Python package. Needs 4 environment variables to run.
hostinger-mcp-server
The most complete MCP server for Hostinger — 280+ tools, OAuth, HTTP transport, retry/cache, batch operations, deploy automation. Runs locally from the hostinger-mcp-server npm package.
globodai-mcp-gandi
MCP server "globodai-mcp-gandi" as configured in globodai-group/mcp-gandi. Runs locally from the globodai-mcp-gandi npm package.
globodai-mcp-cloudflare-dns
MCP server "globodai-mcp-cloudflare-dns" as configured in globodai-group/mcp-cloudflare-dns. Runs locally from the globodai-mcp-cloudflare-dns npm package.
gcp-mcp-server
An MCP server providing tools for GCP Cloud Functions logs. Runs locally from the gcp-mcp-server Python package.
gcp-cost
MCP server "gcp-cost" as configured in nozomi-koborinai/terradart. Launched with bash tool/gcp-cost-mcp-wrapper.sh.