Billtrim: AWS bill savings
com.grain64.billtrim/billtrimVersion 1.0.0Ranked AWS bill savings from a Cost Explorer or CUR export, with dollar impact and CLI steps.
Status
Responds275 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:00 UTC
- Latency
- 275 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://billtrim.grain64.com/mcpResponds275 msNo sign-in
Claude Code
claude mcp add --transport http billtrim https://billtrim.grain64.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: billtrim
Remote MCP server URL: https://billtrim.grain64.com/mcpCursor
{
"mcpServers": {
"billtrim": {
"url": "https://billtrim.grain64.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"billtrim","type":"http","url":"https://billtrim.grain64.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
2 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
analyze_aws_billFind savings in an AWS bill export. Give it the text of a Cost Explorer CSV or an AWS Cost and Usage Report CSV and it returns a ranked list of likely waste (NAT gateway traffic, idle resources, oversized or old-generation volumes and instances, cross-AZ and internet data transfer, Savings Plan sizing), each with a monthly dollar range, the arithmetic, the console and CLI steps, how to verify first, the risk and how to roll back. Deterministic rules, no account access, nothing stored. Findings are suggestions: verify before deleting anything. | No | Yes | Yes | No |
explain_aws_usage_typeExplain one AWS usage-type string from a bill (for example `USE1-NatGateway-Bytes` or `DataTransfer-Regional-Bytes`): what the charge is, the unit price and where it was verified, the usual cause, the cheaper alternative, and the verify-first steps. Use it when you already have a line item and do not need to analyze a whole file. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Nov 11, 2026
- Updated
- Nov 11, 2026
- Repository
- Not given
- Categories (suggested)
- Cloud and infrastructureSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared