# Billtrim: AWS bill savings (remote · billtrim.grain64.com)

Ranked AWS bill savings from a Cost Explorer or CUR export, with dollar impact and CLI steps.

- Trust score: 23/100 (low)
- Change this week: −51
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `billtrim.grain64.com`: 23/100 (this document), [markdown](https://verifymcp.io/servers/com-grain64-billtrim-billtrim/billtrim.md), [page](https://verifymcp.io/servers/com-grain64-billtrim-billtrim/billtrim)

## Channel facts

- Endpoint: `https://billtrim.grain64.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Billtrim: AWS bill savings MCP server?

Billtrim: AWS bill savings is a hosted endpoint at https://billtrim.grain64.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-grain64-billtrim-billtrim 'https://billtrim.grain64.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-grain64-billtrim-billtrim": {
      "url": "https://billtrim.grain64.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-grain64-billtrim-billtrim": {
      "type": "http",
      "url": "https://billtrim.grain64.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-grain64-billtrim-billtrim]
url = "https://billtrim.grain64.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-grain64-billtrim-billtrim": {
      "type": "remote",
      "url": "https://billtrim.grain64.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-grain64-billtrim-billtrim --url 'https://billtrim.grain64.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-grain64-billtrim-billtrim:
    url: "https://billtrim.grain64.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-grain64-billtrim-billtrim": {
      "Transport": "http",
      "Url": "https://billtrim.grain64.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-grain64-billtrim-billtrim -t streamable-http -u 'https://billtrim.grain64.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-grain64-billtrim-billtrim": {
      "type": "http",
      "url": "https://billtrim.grain64.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-16 (score 23, −51)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security regression] HSTS header: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-14 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 72)

First indexed and scored.

## MCP tools (2)

### `analyze_aws_bill` (~233 tokens)

Find savings in an AWS bill

Find 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.

Input parameters:

- `csv` (string, required): The text of the CSV file, header row included, up to 2 MB. For a bigger file, group by Service, Usage Type and Region in Cost Explorer first.
- `format` (string): ce-csv (Cost Explorer), cur-csv (Cost and Usage Report) or auto to detect it.
- `max_findings` (integer): How many ranked findings to return.
- `min_monthly_savings_usd` (number): Drop findings whose top-end monthly saving is below this many US dollars.

Output parameters:

- `engine_version` (string)
- `finding_count` (integer)
- `findings` (array)
- `format` (string)
- `granularity` (string)
- `notes` (array)
- `period_end` (string)
- `period_start` (string)
- `returned` (integer)
- `savings_high` (number)
- `savings_low` (number)
- `source` (string)
- `total_cost` (number)
- `web_url` (string)

### `explain_aws_usage_type` (~152 tokens)

Explain an AWS usage type

Explain 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.

Input parameters:

- `service` (string): Optional service name from the bill, e.g. "EC2 - Other", to tell apart usage types shared by services.
- `usage_type` (string, required): The usage type as it appears on the bill, region prefix allowed, e.g. USE1-NatGateway-Bytes.

Output parameters:

- `closest_rule_ids` (array)
- `decoder_url` (string)
- `engine_version` (string)
- `fixes` (array)
- `matched` (boolean)
- `message` (string)
- `price` (object|null)
- `risk` (string)
- `rollback` (string)
- `rule_id` (string)
- `steps` (object)
- `title` (string)
- `usage_type` (string)
- `usual_causes` (array)
- `verify` (array)
- `what_it_is` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-grain64-billtrim-billtrim/billtrim#diagnostics

## Score history

- 2026-11-21: 23
- 2026-11-20: 23
- 2026-11-19: 23
- 2026-11-18: 23
- 2026-11-17: 23
- 2026-11-16: 23
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 73
- 2026-11-12: 73
- 2026-11-11: 72

## Common questions

### What is the Billtrim: AWS bill savings MCP server?

Billtrim: AWS bill savings is an MCP server listed in the public MCP registry as com.grain64.billtrim/billtrim. Ranked AWS bill savings from a Cost Explorer or CUR export, with dollar impact and CLI steps. This page covers its hosted endpoint (https://billtrim.grain64.com/mcp).

### Is the Billtrim: AWS bill savings MCP server safe to use?

Billtrim: AWS bill savings scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Billtrim: AWS bill savings MCP server expose?

Billtrim: AWS bill savings exposes 2 tools: analyze_aws_bill, explain_aws_usage_type. Their descriptions and schemas cost roughly 385 tokens of context every time the server is loaded.

### Does the Billtrim: AWS bill savings MCP server require authentication?

Its publisher declares no required credentials for Billtrim: AWS bill savings. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Billtrim: AWS bill savings MCP server still maintained?

Billtrim: AWS bill savings is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Billtrim: AWS bill savings MCP server?

VerifyMCP ran 5 checks on Billtrim: AWS bill savings, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Billtrim: AWS bill savings: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://billtrim.grain64.com/mcp
- Website: https://billtrim.grain64.com/docs#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-grain64-billtrim-billtrim/billtrim.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-grain64-billtrim-billtrim/billtrim/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-grain64-billtrim-billtrim/billtrim.json
- HTML version of this page: https://verifymcp.io/servers/com-grain64-billtrim-billtrim/billtrim
