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/JadenRazo/CloudCostMCPWrote 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/jadenrazo/cloudcostmcp/cloudcost-mcp)<a href="https://agentmods.dev/mcp/jadenrazo/cloudcostmcp/cloudcost-mcp"><img src="https://agentmods.dev/badge/mcp/jadenrazo/cloudcostmcp/cloudcost-mcp/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/jadenrazo/cloudcostmcp/cloudcost-mcp"><img src="https://agentmods.dev/badge/mcp/jadenrazo/cloudcostmcp/cloudcost-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cloudcost-mcp 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.
This is a copy
72% identical to playwright-mcp — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "cloudcost-mcp": { "command": "npx", "args": [ "-y", "@jadenrazo/cloudcost-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.
- 1mo ago First seen · 9 lines scan A 0da0ca6218f5
cloudcost-mcp is an MCP server published in the GitHub repository JadenRazo/CloudCostMCP (0 stars, last pushed 3d 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. It is 72% identical to playwright-mcp, differing in 7 lines, and is treated as a copy.
Other mcp servers, from other repositories
cloudprice
MCP server "cloudprice" as configured in Albaker-Group/cloudprice-mcp. Launched with cloudprice-mcp.
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.
clawops
Deploy self-hosted OpenClaw to AWS, GCP, Azure or a local VM — a CLI and an MCP server in one. Runs locally from the @clawops/cli 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.
costory
MCP server "costory", hosted remotely at app-api.costory.io, as configured in costory-io/costory-finops-mcp-skills.
finops
FinOps MCP: query allocated, correlated cloud and AI cost across AWS, GCP, Azure and Snowflake. Remote server at app-api.costory.io.