com.grain64.billtrim/billtrim
Billtrim: AWS bill savings
Is the Billtrim MCP server down? It gave no valid answer in the probe of 2026-11-15: not MCP (HTTP 200). One failed probe is not an outage.
Ranked AWS bill savings from a Cost Explorer or CUR export, with dollar impact and CLI steps.
not MCP no valid answer since 2026-11-15 · probed 2026-11-15 · HTTP 200
Streamable HTTP error: Unexpected content type: text/html; charset=utf-8
- Endpoint
- https://billtrim.grain64.com/mcp (streamable-http)
- Host
- billtrim.grain64.com
- Website
- https://billtrim.grain64.com/docs#mcp
- Registry
- active, updated 2026-11-11 · registry entry
- Changes
- 2 recorded, reachable in 1 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention savings or bill.
- AgenticBooks ai.agenticbooks/books · needs auth
- Bankrolled.ai Agent Hub ai.bankrolled/agent-hub · alive
- DeepLedger: QuickBooks, Xero & Bill.com MCP for ChatGPT & Claude ai.deepledger/mcp · needs auth
- ai.diezx/diezx · no DNS
- Dynt ai.dynt.api/dynt · needs auth
- Gavelin ai.gavelin/mcp · needs auth
- Gov Relations ai.govrelations/govrelations · alive
- ModelRunner ai.modelrunner/mcp · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-15 11:09 | not MCP | ||||
| 2026-11-12 11:29 | alive | 661 ms | 2 | 856 | 494 |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-15. One failed probe is not an outage: the board calls a server down after two days without a valid answer. The next probe runs within a day.
- The endpoint answers HTTP 200, but not with a valid MCP initialize result. Common causes: the URL is a web page or a REST API and not the MCP endpoint, the server answers a JSON-RPC error on initialize, or the response is HTML.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.