io.usefulapi/amberflo

REMOTE · AMBERFLO.USEFULAPI.IO · SCANNED AUG 3

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

Available components

+4 this week 73 73 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security78

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
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. View diagnostics → Pass
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability75

AI-judged instruction clarity (excellent).Pass
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · amberflo.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +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.
2 Aug 26 +44
- Authorization: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
1 Aug 26 −43
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
31 Jul 26 +49
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −48
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +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.
28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +57
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional

Show 5 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://amberflo.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=usefulapi.io	CN=WE1,O=Google Trust Services,C=US	17 Jul 2026	15 Oct 2026	ECDSA 256	ECDSA-SHA256	21da3ed3d8d6cd820e839b2ab904944f
SANs: usefulapi.io, amberflo.usefulapi.io, *.amberflo.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of amberflo.usefulapi.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
usefulapi.io.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://amberflo.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Bearer realm="OAuth", resource_metadata="https://amberflo.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document	https://amberflo.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved	Yes
Resource	https://amberflo.usefulapi.io/mcp
Authorisation server	https://amberflo.usefulapi.io

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://amberflo.usefulapi.io/mcp	Verified	200
http (plaintext)	http://amberflo.usefulapi.io/mcp	Inconclusive	401

MCP tools — 14 exposed · ~1,600 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

amberflo_assign_customer_plan Assign customer plan ~133

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 Output Examples

Name	Type	Req	Description
customer_id	string	yes	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	yes	The productPlanId of the plan to assign.
start_time_in_seconds	integer	—	When the plan takes effect, unix epoch seconds.

No output schema declared.

No examples provided.

amberflo_create_customer Create customer ~148

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 Output Examples

Name	Type	Req	Description
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	yes	Unique customerId to assign (your identifier for the customer).
customer_name	string	yes	Human-readable customer name.
enabled	boolean	—	Whether the customer is enabled.
traits	object	—	Arbitrary string traits (key/value metadata).

No output schema declared.

No examples provided.

amberflo_explain_usage Explain usage ~178

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 Output Examples

Name	Type	Req	Description
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	yes	The meterApiName to explain (from amberflo_list_meters).
start_time_in_seconds	integer	yes	Range start, unix epoch seconds (inclusive).
take_limit	integer	—	Return only the top N records.

No output schema declared.

No examples provided.

amberflo_get_all_usage Get all usage ~143

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

Input Output Examples

Name	Type	Req	Description
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	yes	Range start, unix epoch seconds (inclusive).
time_grouping_interval	string	yes	Bucket size: HOUR \| DAY \| WEEK \| MONTH.

No output schema declared.

No examples provided.

amberflo_get_customer Get a customer ~47

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

Input Output Examples

Name	Type	Req	Description
customer_id	string	yes	The Amberflo customerId to fetch.

No output schema declared.

No examples provided.

amberflo_get_customer_invoice Get customer invoice ~207

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 Output Examples

Name	Type	Req	Description
customer_id	string	yes	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.

No output schema declared.

No examples provided.

amberflo_get_customer_plan Get customer plan ~54

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

Input Output Examples

Name	Type	Req	Description
customer_id	string	yes	The Amberflo customerId.

No output schema declared.

No examples provided.

amberflo_get_usage Query usage for a meter ~208

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

Input Output Examples

Name	Type	Req	Description
aggregation	string	yes	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	yes	The meterApiName to query (from amberflo_list_meters).
start_time_in_seconds	integer	yes	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	yes	Bucket size: HOUR \| DAY \| WEEK \| MONTH.

No output schema declared.

No examples provided.

amberflo_ingest_usage Ingest usage event ~149

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 Output Examples

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

No output schema declared.

No examples provided.

amberflo_list_customer_invoices List customer invoices ~102

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

Input Output Examples

Name	Type	Req	Description
customer_id	string	yes	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.

No output schema declared.

No examples provided.

amberflo_list_customer_plan_history List customer plan history ~59

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

Input Output Examples

Name	Type	Req	Description
customer_id	string	yes	The Amberflo customerId.

No output schema declared.

No examples provided.

amberflo_list_customers List customers ~45

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

amberflo_list_meters List meters ~52

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.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

amberflo_list_prepaid_orders List prepaid orders ~75

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

Input Output Examples

Name	Type	Req	Description
customer_id	string	yes	The Amberflo customerId.
product_id	string	—	Product id. Default "1".

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	69
28 Jul	69
29 Jul	70
30 Jul	22
31 Jul	71
1 Aug	28
2 Aug	72
3 Aug	73