# Usefulapi Amberflo MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.usefulapi%2Famberflo
Registry id: `mcp-registry/io.usefulapi/amberflo`
Status: auth-required (checked 2026-10-27T08:32:20.376Z)

## Verdict

Usefulapi Amberflo MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 63 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 14 tools, costing an agent about 3,155 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 63 ms | 88% of MCP servers |
| p95 handshake latency | 365 ms | — |
| Checks in 30 days | 220 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 14 | — |
| Tool-list size for an agent | ~3,155 tokens | 45% of MCP servers |
| Days observed | 28 | — |

## Install

```json
{
  "mcpServers": {
    "usefulapi-amberflo-mcp-server": {
      "type": "http",
      "url": "https://amberflo.usefulapi.io/mcp"
    }
  }
}
```

Claude Code:

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

## Tools (14)

- `amberflo_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.
- `amberflo_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.
- `amberflo_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.
- `amberflo_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.
- `amberflo_get_customer`: Fetch a single customer by its Amberflo customerId. API: GET /customers/?customerId=<id>.
- `amberflo_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 /pay
- `amberflo_get_customer_plan`: Get a customer's LATEST assigned product plan (pricing). API: GET /payments/pricing/amberflo/customer-pricing?CustomerId=<id>.
- `amberflo_get_usage`: Query aggregated usage for a single meter over a time range, optionally grouped/filtered. API: POST /usage/.
- `amberflo_ingest_usage`: 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.
- `amberflo_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.
- `amberflo_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>.
- `amberflo_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_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: 
- `amberflo_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>.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.