Azure + GCP cost management: spending, forecasts, anomalies, budgets, idle resources, and tags.
Ask your AI about your cloud bill. Ask once: "Give me this month's cost review" — and CloudScope runs the full workflow (spend, deltas, anomalies, idle resources, budgets, forecast) and hands back a decision-ready report, not raw numbers to interpret yourself: Month-to-date Azure spend is $4,312 (May 1–29), tracking +11% vs April. The mover is App Service (+$280) — a new staging slot left…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
get_cost_summaryNo description publishedThis tool published no description. Forge does not invent one.
detect_anomaliesNo description publishedThis tool published no description. Forge does not invent one.
list_recommendationsNo description publishedThis tool published no description. Forge does not invent one.
get_cost_forecastNo description publishedThis tool published no description. Forge does not invent one.
check_budgetsNo description publishedThis tool published no description. Forge does not invent one.
compare_periodsNo description publishedThis tool published no description. Forge does not invent one.
top_spending_resourcesNo description publishedThis tool published no description. Forge does not invent one.
get_cost_by_tagNo description publishedThis tool published no description. Forge does not invent one.
find_idle_resourcesNo description publishedThis tool published no description. Forge does not invent one.
find_untagged_resourcesNo description publishedThis tool published no description. Forge does not invent one.
get_current_dateNo description publishedThis tool published no description. Forge does not invent one.
get_cross_subscription_costsNo description publishedThis tool published no description. Forge does not invent one.
list_subscriptionsNo description publishedThis tool published no description. Forge does not invent one.
list_projectsNo description publishedThis tool published no description. Forge does not invent one.
get_cross_project_costsNo description publishedThis tool published no description. Forge does not invent one.
0 of 15 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Ask your AI about your cloud bill. Ask once: "Give me this month's cost review" — and CloudScope runs the full workflow (spend, deltas, anomalies, idle resources, budgets, forecast) and hands back a decision-ready report, not raw numbers to interpret yourself: Month-to-date Azure spend is $4,312 (May 1–29), tracking +11% vs April. The mover is App Service (+$280) — a new staging slot left running. 2 idle resources cost $94/month; is at 78% with 2 days left. Top action: delete the orphaned…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.