# io.usefulapi/amberflo (remote · amberflo.usefulapi.io)

Query and manage Amberflo metering & billing: customers, meters, usage, plans, invoices, prepaid.

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `amberflo.usefulapi.io`: 73/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-amberflo/amberflo.md), [page](https://verifymcp.io/servers/io-usefulapi-amberflo/amberflo)

## Channel facts

- Endpoint: `https://amberflo.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-08-03.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1600 tokens (~114/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-usefulapi-amberflo https://amberflo.usefulapi.io/mcp
```

### Codex

```toml
[mcp_servers.io-usefulapi-amberflo]
url = "https://amberflo.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-amberflo": {
      "type": "remote",
      "url": "https://amberflo.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-amberflo --url https://amberflo.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-amberflo:
    url: "https://amberflo.usefulapi.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-amberflo": {
      "type": "http",
      "url": "https://amberflo.usefulapi.io/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-08-03 (score 73, +1)

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

### 2026-08-02 (score 72, +44)

- [security improvement] Authorization: unverified → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20

### 2026-08-01 (score 28, −43)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: fail → unverified

### 2026-07-31 (score 71, +49)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 22, −48)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 70, +1)

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

### 2026-07-28 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 69, +57)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (14)

### `amberflo_list_customers` (~45 tokens)

List customers

List all customers registered in your Amberflo account (id, name, email, traits, enabled). Good first call to discover customer ids. API: GET /customers/.

### `amberflo_get_customer` (~47 tokens)

Get a customer

Fetch a single customer by its Amberflo customerId. API: GET /customers/?customerId=<id>.

Input parameters:

- `customer_id` (string, required): The Amberflo customerId to fetch.

### `amberflo_list_meters` (~52 tokens)

List meters

List all meter definitions in your account (id, meterApiName, label, meterType, aggregation, etc.). Use meterApiName values here as inputs to usage tools. API: GET /meters.

### `amberflo_get_usage` (~208 tokens)

Query usage for a meter

Query aggregated usage for a single meter over a time range, optionally grouped/filtered. API: POST /usage/.

Input parameters:

- `aggregation` (string, required): Aggregation function: SUM | COUNT | MIN | MAX.
- `end_time_in_seconds` (integer): Range end, unix epoch seconds. Defaults to now if omitted.
- `filter` (object): Dimension filter: map of dimension name -> allowed values.
- `group_by` (array): Dimension names to group results by, e.g. ["customerId"].
- `meter_api_name` (string, required): The meterApiName to query (from amberflo_list_meters).
- `start_time_in_seconds` (integer, required): Range start, unix epoch seconds (inclusive).
- `take_is_ascending` (boolean): Sort order for `take` (default false = descending).
- `take_limit` (integer): Return only the top N groups.
- `time_grouping_interval` (string, required): Bucket size: HOUR | DAY | WEEK | MONTH.

### `amberflo_get_all_usage` (~143 tokens)

Get all usage

Get total usage across all meters over a time range, optionally grouped by customer or filtered to one customer. API: GET /usage/all.

Input parameters:

- `end_time_in_seconds` (integer): Range end, unix epoch seconds. Defaults to now if omitted.
- `filter_by_customer_id` (string): Restrict results to a single customerId.
- `group_by_customer_id` (boolean): When true, group results by customer (sends groupBy=customerId).
- `start_time_in_seconds` (integer, required): Range start, unix epoch seconds (inclusive).
- `time_grouping_interval` (string, required): Bucket size: HOUR | DAY | WEEK | MONTH.

### `amberflo_explain_usage` (~178 tokens)

Explain usage

Explain/drill into the raw meter events behind a meter's usage over a time range — useful to debug why a number looks off. API: POST /usage/explain.

Input parameters:

- `aggregation` (string): Aggregation function: SUM | COUNT | MIN | MAX.
- `end_time_in_seconds` (integer): Range end, unix epoch seconds. Defaults to now if omitted.
- `filter` (object): Dimension filter: map of dimension name -> allowed values.
- `group_by` (array): Dimension names to group by, e.g. ["customerId"].
- `meter_api_name` (string, required): The meterApiName to explain (from amberflo_list_meters).
- `start_time_in_seconds` (integer, required): Range start, unix epoch seconds (inclusive).
- `take_limit` (integer): Return only the top N records.

### `amberflo_get_customer_plan` (~54 tokens)

Get customer plan

Get a customer's LATEST assigned product plan (pricing). API: GET /payments/pricing/amberflo/customer-pricing?CustomerId=<id>.

Input parameters:

- `customer_id` (string, required): The Amberflo customerId.

### `amberflo_list_customer_plan_history` (~59 tokens)

List customer plan history

List the full history of product plans assigned to a customer over time. API: GET /payments/pricing/amberflo/customer-pricing/list?CustomerId=<id>.

Input parameters:

- `customer_id` (string, required): The Amberflo customerId.

### `amberflo_list_customer_invoices` (~102 tokens)

List customer invoices

List all invoices for a customer (optionally for a specific product), with payment status. API: GET /payments/billing/customer-product-invoice/all.

Input parameters:

- `customer_id` (string, required): The Amberflo customerId.
- `from_cache` (boolean): Use cached invoices (faster). Default true.
- `product_id` (string): Product id. Default "1".
- `with_payment_status` (boolean): Include payment status. Default true.

### `amberflo_get_customer_invoice` (~207 tokens)

Get customer invoice

Get a single customer invoice: the CURRENT open invoice (latest=true, default) or a SPECIFIC past invoice by product_plan_id + year + month + day. API: GET /payments/billing/customer-product-invoice.

Input parameters:

- `customer_id` (string, required): The Amberflo customerId.
- `day` (integer): Day of month of a specific past invoice.
- `from_cache` (boolean): Use cached invoice (faster). Default true.
- `latest` (boolean): Fetch the current open invoice. Default true. Ignored when a specific invoice is addressed.
- `month` (integer): Month (1-12) of a specific past invoice.
- `product_id` (string): Product id. Default "1".
- `product_plan_id` (string): Product plan id of a specific past invoice (with year/month/day).
- `with_payment_status` (boolean): Include payment status. Default true.
- `year` (integer): Year of a specific past invoice.

### `amberflo_list_prepaid_orders` (~75 tokens)

List prepaid orders

List a customer's active prepaid credit orders for a product. API: GET /payments/pricing/amberflo/customer-prepaid/list?CustomerId=<id>&ProductId=<pid>.

Input parameters:

- `customer_id` (string, required): The Amberflo customerId.
- `product_id` (string): Product id. Default "1".

### `amberflo_create_customer` (~148 tokens)

Create customer

WRITE: create/register a new customer in Amberflo (id + name required; optional email, enabled flag, and traits). Optionally auto-create the customer in Stripe. API: POST /customers/.

Input parameters:

- `create_in_stripe` (boolean): When true, also auto-create this customer in Stripe (adds ?autoCreateCustomerInStripe=true).
- `customer_email` (string): Customer email address.
- `customer_id` (string, required): Unique customerId to assign (your identifier for the customer).
- `customer_name` (string, required): Human-readable customer name.
- `enabled` (boolean): Whether the customer is enabled.
- `traits` (object): Arbitrary string traits (key/value metadata).

### `amberflo_assign_customer_plan` (~133 tokens)

Assign customer plan

WRITE: assign/attach a pricing product plan to a customer — this changes what the customer is billed. API: POST /payments/pricing/amberflo/customer-pricing.

Input parameters:

- `customer_id` (string, required): The Amberflo customerId to assign the plan to.
- `end_time_in_seconds` (integer): When the plan ends, unix epoch seconds.
- `product_id` (string): Product id the plan belongs to.
- `product_plan_id` (string, required): The productPlanId of the plan to assign.
- `start_time_in_seconds` (integer): When the plan takes effect, unix epoch seconds.

### `amberflo_ingest_usage` (~149 tokens)

Ingest usage event

WRITE: record/ingest a single usage meter event (writes billable usage data) to the Amberflo ingestion host. API: POST /ingest/ on the ingest base URL.

Input parameters:

- `customer_id` (string, required): The customerId this usage belongs to.
- `dimensions` (object): Optional dimensions (key/value string metadata) for the event.
- `meter_api_name` (string, required): The meterApiName this event is for.
- `meter_time_in_millis` (integer, required): Event timestamp, unix epoch milliseconds.
- `meter_value` (number, required): The numeric value of the usage event.
- `unique_id` (string): Optional idempotency/unique id for the event.

## Diagnostics

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

## Score history

- 2026-08-03: 73
- 2026-08-02: 72
- 2026-08-01: 28
- 2026-07-31: 71
- 2026-07-30: 22
- 2026-07-29: 70
- 2026-07-28: 69
- 2026-07-27: 69
- 2026-07-26: 12

## Links

- Remote endpoint: https://amberflo.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-amberflo/amberflo/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-amberflo/amberflo/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-amberflo/amberflo