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/Albaker-Group/cloudprice-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/albaker-group/cloudprice-mcp/cloudprice)<a href="https://agentmods.dev/mcp/albaker-group/cloudprice-mcp/cloudprice"><img src="https://agentmods.dev/badge/mcp/albaker-group/cloudprice-mcp/cloudprice.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cloudprice 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 7d 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
{
"cloudprice": {
"command": "cloudprice-mcp"
}
}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.
- 7d ago First seen · 5 lines scan A 44daae1e8887
cloudprice is an MCP server published in the GitHub repository Albaker-Group/cloudprice-mcp (1 stars, last pushed yesterday), 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
cloudscope
Azure + GCP cost management: spending, forecasts, anomalies, budgets, idle resources, and tags. Runs locally from the cloudscope-mcp npm package. Needs 9 environment variables to run.
cloudcost-mcp
MCP server for multi-cloud cost analysis of Terraform, CloudFormation, Pulumi, and Bicep/ARM codebases. Runs locally from the @jadenrazo/cloudcost-mcp npm package.
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.
aws-readonly-mcp
MCP server "aws-readonly-mcp" as configured in ziyuyu23/aws-readonly-mcp. Runs locally from the aws-readonly-mcp Python package.
cloud-regions
Cloud region data for AWS, Azure, GCP, OCI & more. Query by location, compliance, GPU. Runs locally from the mcp-server-cloud-regions npm package.