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/alexpota/cloudscope-mcpWrote 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/alexpota/cloudscope-mcp/cloudscope)<a href="https://agentmods.dev/mcp/alexpota/cloudscope-mcp/cloudscope"><img src="https://agentmods.dev/badge/mcp/alexpota/cloudscope-mcp/cloudscope/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/alexpota/cloudscope-mcp/cloudscope"><img src="https://agentmods.dev/badge/mcp/alexpota/cloudscope-mcp/cloudscope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cloudscope 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
{
"cloudscope": {
"command": "npx",
"args": [
"-y",
"cloudscope-mcp"
],
"env": {
"AZURE_SUBSCRIPTION_ID": "",
"AZURE_TENANT_ID": "",
"AZURE_CLIENT_ID": "",
"AZURE_CLIENT_SECRET": "",
"GOOGLE_CLOUD_PROJECT": "",
"GCP_BILLING_TABLE": "",
"GCP_PROJECT_ID": "",
"GCP_BILLING_ACCOUNT_ID": "",
"GOOGLE_APPLICATION_CREDENTIALS": ""
}
}
}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 · 20 lines scan A 8ebf20404b82
cloudscope is an MCP server published in the GitHub repository alexpota/cloudscope-mcp (1 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
cloudprice
MCP server "cloudprice" as configured in Albaker-Group/cloudprice-mcp. Launched with cloudprice-mcp.
azure-finops-mcp
MCP server exposing Azure FinOps capabilities to LLM clients. Runs locally from the azure-finops-mcp Python package. Needs 3 environment variables to run.
azure-resource-manager-mcp
MCP server "azure-resource-manager-mcp", hosted remotely at mcp.management.azure.com, as configured in microsoft/skills.
cloud-finops
MCP server exposing the OptimNow Cloud FinOps skill (reference library + named-pattern playbooks) as queryable tools. Runs locally from the cloud-finops-mcp Python package.
cloudcostsmcp
MCP server for cloud pricing (AWS, GCP, Azure). Runs locally from the opencloudcosts Python package. Needs 5 environment variables to run.
azure-resource-manager-mcp
MCP server "azure-resource-manager-mcp", hosted remotely at mcp.management.azure.com, as configured in jonathan-vella/apex-accelerator.