Plutus
v2.0.0Query cloud, AI and SaaS spend across 25+ providers: costs, budgets, anomalies, unit economics.
Endpoint health
online- Last checked
- 11/20/2026, 7:17:48 AM
- Latency
- 349 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.plutus-cloud%2Fplutus-cost-data
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.plutus-cloud/plutus-cost-data": {
"url": "https://console.plutus-cloud.com/api/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
explain_cost_change
Explain a specific cost change: which timeline events line up with it, how strongly, and how much of the move Plutus could account for. Ask this about any point on a cost chart — it is not limited to anomalies the detector flagged (use list_anomalies for those; each already carries the same explanation). RENDER `explanation.sentences` AS WRITTEN. They are generated under a strict discipline and are the only phrasing this data supports: Plutus reports temporal and dimensional evidence, never causation. Each candidate carries a `claim` of "coincides" (temporal proximity only — the common case), "consistent_with" (proximity plus a confirmed link between that event source and this cost entity) or "accounts_for" (a known dollar amount that matches the move). Do not upgrade one to another, do not say an event "caused" or "led to" the change, and do not merge several candidates into a single narrative. Three separate numbers, never interchangeable: `change_evidence` is how sure we are a real change-point exists at all; `attribution_completeness` is what fraction of the move was localized to a specific part of the bill (a low value means "we do not know what this spend is yet", which is NOT the same as "nothing explains it"); `p_cause` is per candidate, and sums with `p_unknown` to 1. `tier: "unknown"` means we looked and found nothing that lines up — say that, rather than reaching for the top-ranked candidate anyway. Confidence is capped at 0.60 by design; there is no "high" tier today. Body: `dimension` + `value` name the slice (e.g. service=AmazonEC2), optional `cost_source_id` narrows it, and exactly one of `day` or `range` says when. A range is narrowed to the single biggest-moving day inside it, reported as `explained_day`. Mirrors POST /api/accounts/:accountId/cost-changes/explain. In apps that show MCP Apps (Claude on the web, desktop and mobile), this result is also drawn as a card under the tool call showing the move and its candidates. Still give `explanation.sentences` as written, but do not rebuild the candidates as a table or draw another chart of them.
Schema valid · SHA-256 3be70a0d525b…
View input schema
Connections
streamable-http
https://console.plutus-cloud.com/api/mcp