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/raviteja-pegata/Azure-FinOps-MCP-ServerWrote 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/raviteja-pegata/azure-finops-mcp-server/azure-finops-mcp)<a href="https://agentmods.dev/mcp/raviteja-pegata/azure-finops-mcp-server/azure-finops-mcp"><img src="https://agentmods.dev/badge/mcp/raviteja-pegata/azure-finops-mcp-server/azure-finops-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/raviteja-pegata/azure-finops-mcp-server/azure-finops-mcp"><img src="https://agentmods.dev/badge/mcp/raviteja-pegata/azure-finops-mcp-server/azure-finops-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
azure-finops-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 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
{
"azure-finops-mcp": {
"command": "uvx",
"args": [
"azure-finops-mcp"
],
"env": {
"AZURE_ALLOWED_SUBSCRIPTIONS": "",
"AZURE_DEFAULT_SUBSCRIPTION": "",
"FINOPS_CACHE_TTL_SECONDS": ""
}
}
}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 · 13 lines scan A c2caf383f24b
azure-finops-mcp is an MCP server published in the GitHub repository raviteja-pegata/Azure-FinOps-MCP-Server (0 stars, last pushed 3mo 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
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.
cloudcostsmcp
MCP server for cloud pricing (AWS, GCP, Azure). Runs locally from the opencloudcosts Python package. Needs 5 environment variables to run.
azure-finops-elite
MCP server "azure-finops-elite" as configured in mazhar480/Azure-FinOps-Optimizer-MCP. Runs locally from the azure-finops-elite Python package.
azure-resource-manager-mcp
MCP server "azure-resource-manager-mcp", hosted remotely at mcp.management.azure.com, as configured in jonathan-vella/apex-accelerator.
terraform
MCP server "terraform" as configured in iloveitaly/llm-ide-rules. Runs in Docker (hashicorp/terraform-mcp-server).
stripe
Stripe's hosted MCP server: lets the agent work with customers, products, prices and payment links. Remote server at mcp.stripe.com.